Foreign tech companies entering Kazakhstan face layered licensing and permit obligations under Kazakhstani law. Understand the framework. Make an enquiry.
Foreign technology and software companies entering the Kazakhstani market encounter a regulatory environment that is more layered than its reputation as a business-friendly destination might suggest. Kazakhstan's licensing and permit framework applies selectively to the technology sector — certain activities require a formal licence from a designated state authority, others require notifications, registrations, or approvals that fall short of full licensing but carry equivalent compliance weight. For in-house counsel assessing market entry, understanding which obligations attach to which activities — and in which order — is the first substantive question the regulatory analysis must answer. The distinction matters: missing a licensing obligation before commencing operations carries administrative and, in some cases, criminal exposure under Kazakhstani law, and the regulator's enforcement posture has tightened in recent years.
Kazakhstan's primary instrument governing licensing and permit requirements across all sectors is the Law on Permits and Notifications, which establishes a unified classification framework distinguishing between licences, subsidiary licences, notifications, and permits. The Law was introduced to consolidate what had been a fragmented set of sector-specific instruments and to create a single procedural channel — the Government for Citizens portal — through which the majority of applications and notifications are submitted electronically. For the technology and software sector, however, the unified framework interacts with a set of sector-specific regimes, including those governing cryptography, electronic signatures, personal data processing, financial technology, and telecommunications infrastructure. Each of those sector-specific regimes carries its own competent authority and its own documentation standard.
The central regulatory authority for digital and technology activities is the Ministry of Digital Development, Innovation and Aerospace Industry (MDDIAI). It administers licensing for a range of activities touching on information security, certified encryption tools, and electronic document circulation systems. The Ministry of Trade and Integration handles certain distribution and import-related approvals relevant to foreign software vendors supplying products classified as dual-use technology. The Agency for Regulation and Development of the Financial Market (ARDFM) is the competent authority for fintech activities and payment system operators — a category that increasingly overlaps with software companies offering embedded finance or payment infrastructure. The National Bank of Kazakhstan retains a parallel oversight role in respect of payment systems and electronic money.
For a foreign company assessing its obligations, the first analytical step is to identify which of these regulatory authorities has competence over its specific activity — because the licensing obligations, timelines, and substantive requirements differ materially between them.
The licensing obligation in the technology sector is activity-specific rather than sector-wide. Not every foreign technology company entering Kazakhstan needs a licence. The obligation attaches to defined categories of activity, and the characterisation of a company's actual operations against those categories is the core of the compliance exercise.
The principal licensed activities in the technology and software domain include: the provision of services involving cryptographic information protection tools; the development, production, or distribution of electronic digital signature tools and associated infrastructure; the operation of certification centres under the electronic signature framework; the provision of certain types of information security services, including penetration testing services when offered commercially; and the operation of networks or platforms classified as telecommunications networks under the Law on Communications. Additionally, any company intending to process personal data on behalf of Kazakhstani residents in a commercial context is subject to registration obligations under the Law on Personal Data and Its Protection, though this is a registration rather than a licence in the strict sense.
Fintech is a separately regulated zone. Software companies that embed payment processing, e-money issuance, or banking functionality into their products are assessed by the ARDFM and the National Bank against the criteria applicable to payment service providers and electronic money operators — a licensing regime substantially more demanding than the general technology licence framework, with capital adequacy requirements and ongoing supervisory reporting.
For companies whose technology activities do not fall within any of these categories — for example, a pure SaaS provider offering business productivity tools with no cryptographic, financial, or telecommunications-classified components — the general position is that no technology-specific licence is required. However, such a company will still need to comply with registration requirements for its legal entity in Kazakhstan, may need to register as a data operator, and must ensure its imported software products comply with applicable technical regulations of the EAEU.
Kazakhstan is a founding member of the Eurasian Economic Union alongside Russia, Belarus, Armenia, and Kyrgyzstan. EAEU membership has direct consequences for the licensing and permit analysis that foreign technology companies need to understand at the outset.
The EAEU has adopted harmonised technical regulations that apply across all member states, including in respect of certain categories of electronic products and telecommunications equipment. Where a product falls within the scope of an EAEU technical regulation, conformity assessment in any one member state in principle provides access to the entire union market — but Kazakhstan maintains certain national licensing requirements that operate in parallel with EAEU conformity procedures. The critical point for foreign technology companies is that EAEU conformity does not substitute for a Kazakhstani licence where a Kazakhstani licence is required; the two obligations coexist.
For Russian technology companies entering Kazakhstan specifically, the EAEU framework provides procedural advantages in customs and product movement, and the mutual recognition of certain conformity assessments reduces duplication. However, both countries maintain national licensing regimes for information security tools and cryptographic products, and mutual recognition does not extend to those regimes. A Russian company licensed by the FSB for cryptographic tools in Russia does not hold an equivalent Kazakhstani licence and must apply separately in Kazakhstan through the MDDIAI process. This is a frequently misunderstood point among Russian technology companies that assume their domestic authorisations carry across the border.
The EAEU customs union also affects the import of software delivered on physical media or embedded in hardware. Technical regulation TP EAEU 004/2011 (low-voltage equipment) and related instruments may require EAC marking for hardware components. For in-house counsel with cross-border Russia-Kazakhstan mandates, the EAEU layer is therefore both an opportunity — in terms of streamlined customs procedures — and a source of additional compliance obligations that are easily overlooked.
For in-house counsel assessing market entry across the EAEU, early-stage regulatory mapping is considerably more efficient than retrospective compliance remediation. The Regulatory & Licensing practice at Vetrov & Partners has advised on cross-border entry structures in Kazakhstan and the wider EAEU region — contact the team at info@vetrovpartners.com or via for an initial conversation.
"The EAEU framework creates a deceptive familiarity for Russian technology companies entering Kazakhstan — the administrative architecture looks similar, but the licensing obligations are national, not union-wide, and that distinction carries real compliance risk." — Aigerim Serikbayeva, Contributing Regional Analyst — Kazakhstan · EAEU trade, customs and market entry
Foreign companies applying for technology-related licences in Kazakhstan navigate a process administered primarily through the Government for Citizens state services portal (egov.kz). The stated statutory timeline for most first-tier technology licences is fifteen working days from submission of a complete application. In practice, timelines extend considerably beyond this figure when documentation is incomplete, when translation and apostille requirements have not been satisfied, or when the competent authority requires clarification of the nature of the activity. Applicants should plan for a realistic timeline of six to twelve weeks for a straightforward first licence, and longer for applications involving cryptographic tools or telecommunications infrastructure, which involve additional inter-agency consultation steps.
The documentation required typically includes: the applicant's corporate formation documents (translated into Kazakhstani and notarised); confirmation of the technical qualifications of key personnel; a technical description of the relevant software or system; and, for cryptographic and information security licences, technical expert assessments conducted by accredited laboratories. Foreign companies frequently encounter delays at the expert assessment stage because MDDIAI-accredited laboratories are limited in number and the queue for assessments can extend several weeks beyond the formal statutory timeline.
A persistent source of difficulty for foreign technology companies is the localisation requirement. Certain licensing categories require that the applicant maintain a physical presence and technical infrastructure in Kazakhstan, not merely a legal registration. For a company structured to deliver its technology services entirely from abroad or via cloud infrastructure located outside Kazakhstan, the localisation question requires careful analysis before the application is submitted. In some cases, a subsidiary or branch is required; in others, a commercial representation structure may be sufficient. The answer depends on the specific licence category and the regulatory interpretation current at the time of application.
A further practical consideration is the interaction between the licensing timeline and the commencement of commercial operations. Kazakhstani law is explicit that licensed activities may not commence before the licence is issued. Companies that begin delivering services in anticipation of a forthcoming licence — a pattern more common than compliance practitioners would prefer — expose themselves to administrative liability under the Code of Administrative Offences. The quantum of sanctions is not trivial, and for companies in regulated sectors such as fintech or information security, the reputational consequences of an enforcement action can exceed the immediate financial penalty.
For foreign creditors, investors, and general counsel assessing a prospective acquisition or partnership with a Kazakhstani technology company, licensing status is accordingly a material due diligence item. The acquiring party should verify not only that the target holds the applicable licences but that those licences have been maintained in good standing — fee payments, renewal filings, and condition compliance are all separately auditable — and that no suspension or enforcement action is open or pending. Verification of licensing status can be performed through the official state database and, where necessary, through a formal regulatory enquiry directed to the competent authority.
The practical guidance that follows from the analysis above can be distilled into a structured sequence of steps that foreign technology companies should complete before commencing regulated activities in Kazakhstan.
The first step is an activity characterisation exercise: mapping each planned activity in Kazakhstan against the categories of licensed and notifiable activity under the Law on Permits and Notifications and the relevant sector-specific rules. This exercise determines whether any licence is required at all, and if so, which authority has competence and which documentation pathway applies.
The second step is an EAEU conformity assessment review: determining whether the products or services involve components subject to EAEU technical regulations and whether conformity assessments already held in another EAEU member state require supplementation or re-registration for the Kazakhstani market.
The third step is a localisation analysis: establishing whether the applicable licence category requires physical infrastructure or personnel in Kazakhstan and, if so, what corporate structure is required to satisfy that requirement. This analysis directly informs the company formation and corporate structuring decisions that must precede the licence application.
The fourth step is a personal data compliance mapping exercise: identifying whether the company's activities involve the collection, storage, or processing of personal data of Kazakhstani residents and, if so, registering as a data operator and ensuring that data processing arrangements comply with Kazakhstani personal data law. Where data is processed outside Kazakhstan or involves cross-border transfers, additional restrictions apply.
The fifth step — and one frequently deferred until too late — is establishing a relationship with qualified local counsel in Kazakhstan before the licensing application is submitted, not after the first request for information is received from the regulatory authority. The licensing process in Kazakhstan is administratively intensive, and competent preparation at the outset materially reduces the risk of delays and substantive objections during review.
Q: Does a foreign software company always need a licence to operate in Kazakhstan?
A: No. The licensing obligation applies to specific categories of activity — not to the technology sector as a whole. A SaaS company delivering general business productivity tools with no cryptographic, financial technology, or telecommunications-classified components will typically not require a technology-specific licence, though it will need to register its legal entity and may need to comply with data operator registration requirements. The threshold question is always whether the company's specific activities fall within one of the defined licensed categories under the Law on Permits and Notifications and the relevant sector-specific rules. An activity characterisation exercise conducted before operations commence is the most reliable way to determine this.
Q: Does a Russian technology company's domestic licence carry over into Kazakhstan under the EAEU framework?
A: No. EAEU membership provides harmonised customs and conformity assessment procedures for certain product categories, but national licensing regimes — including those for cryptographic tools, information security services, and electronic signature infrastructure — are maintained separately by each EAEU member state. A Russian company licensed by its domestic competent authority for cryptographic or information security activities does not hold an equivalent Kazakhstani licence and must apply separately through the Ministry of Digital Development, Innovation and Aerospace Industry. This is one of the more common misapprehensions among Russian technology companies expanding into Kazakhstan, and it can cause significant operational delays if not addressed at the planning stage.
Q: How long does it take to obtain a technology sector licence in Kazakhstan?
A: The statutory timeline for most first-tier technology licences is fifteen working days from submission of a complete application through the egov.kz portal. In practice, the realistic timeline for a straightforward licence — assuming documentation is complete and translations and apostilles are in order — is six to twelve weeks. Applications involving cryptographic tools or telecommunications infrastructure require inter-agency consultation steps and typically take longer. Expert assessments by accredited laboratories, which are mandatory for certain information security licence categories, add to the timeline and should be commissioned before or in parallel with the licence application rather than after.
Q: What happens if a company begins technology operations in Kazakhstan before obtaining the required licence?
A: Commencing licensed activities before the licence is issued is a violation of Kazakhstani administrative law. The Code of Administrative Offences provides for sanctions in such cases, and for companies in regulated sectors — fintech, information security, telecommunications — enforcement action can have consequences beyond the immediate financial penalty, including reputational damage and complications with future licensing or regulatory interaction. The risk is not hypothetical; the regulatory posture has tightened in recent years. Companies should not commence regulated activities in anticipation of a forthcoming licence.
Q: Is personal data compliance a licensing issue or a separate obligation?
A: It is a separate but related obligation. The processing of personal data of Kazakhstani residents triggers registration requirements under the Law on Personal Data and Its Protection, administered by a designated competent authority. This is a registration obligation rather than a licence in the formal classification, but it carries equivalent compliance weight: processing personal data without completing the registration, or processing data in a manner inconsistent with the registration, exposes the company to administrative liability. For technology companies whose products involve user data — which is the majority of consumer-facing and many B2B software products — the personal data compliance analysis runs in parallel with the licensing analysis and should be completed at the same stage of the market entry assessment.
This briefing is general information and does not constitute legal advice. For advice on a specific matter, write in confidence to info@vetrovpartners.com.
Our team advises foreign clients on exactly these questions across Russia and the EAEU region. Initial 30-minute consultation — complimentary.
Make an enquiry