Kazakhstan has approved binding rules for how the operator of its National AI Platform deals with anyone who wants to build or host an AI model on it

The order is an intake procedure, and it is worth saying so before anything else

Read the operative part and there is not much regulatory reach in it. An initiator, defined to include a state body, a legal entity or an individual, sends the platform operator two documents: a request on the form at Annex 1, and a passport of the platform software product or AI model on the form at Annex 2. Both go through the platform itself or to the operator email address published on the platform.

The operator then has 5 working days to check that the two filings are complete. Where something is missing it sends a notice inside that same window, and the initiator has 3 working days to supply the gap. Miss that and the operator decides to refuse consideration of the request, with reasons.

Once completeness is confirmed, a second 5-working-day clock runs for the substantive review. The outcome is one of two decisions: grant platform resources, or refuse them. The decision goes out as a notice within 2 working days of being taken, through the platform or to the email address given in the request. A refusal notice states the ground and the information it rested on.

So the worst-case published path from a clean filing to a written answer is roughly twelve working days, and a single incompleteness round trip adds to that. Those are the operator's deadlines. No deadline in the order runs against the applicant except the 3-working-day cure period.

If the decision is a grant, the operator concludes a contract with the initiator under Kazakh law, creates user accounts, and gives access to platform resources in the volume the contract fixes. Development, testing and hosting then proceed under the contract and under Kazakh law generally. That is the whole of Chapter 2.

The statute behind it is the actual story

Kazakhstan has a standalone national AI statute. Law No. 230-VIII ZRK On Artificial Intelligence was adopted on 17 November 2025 and, per the Adilet registration card, published on 18 November 2025 in Egemen Qazaqstan and Kazakhstanskaya Pravda. Article 31 brings it into force sixty calendar days after first official publication, which places commencement in mid-January 2026. The Adilet text also carries editor notes recording amendments made by Law No. 326-VIII of 24 June 2026. This is a live statute with an amendment history, not a bill.

It is also not thin. Article 17(3) prohibits creating or operating AI systems with any of seven listed capabilities, including subliminal or manipulative techniques that distort a person's behaviour, exploitation of vulnerability by age or disability, social scoring outside cases set by law, biometric classification aimed at discrimination, and emotion recognition without consent. Article 21(2) permits distribution of synthetic outputs only where they carry machine-readable marking plus a visual or other warning. Article 23(5) allows use of works to train AI models only where the author or rightholder has not objected in machine-readable form.

None of that is what Order 482/NQ does. The order implements one narrow delegation. Article 25(1) describes the platform as providing a controlled environment for development, training and trial operation of platform software products and AI models for a limited period. Article 25(2) says the interaction procedure is to be determined by the authorised body. That is the clause the order recites.

The desk's reading, and it is inference rather than anything the ministry says: the sequencing suggests the platform is being stood up as a supervised environment first, with the substantive conduct rules of the statute sitting above it and applying regardless of whether anyone uses the platform at all.

What an applicant actually has to hand over

The request form at Annex 1 is administrative: status of the initiator, name or full name, business identification number or individual identification number, legal address or place of residence, phone, email, project name, type of work, and planned start and finish dates.

The passport at Annex 2 is where the substance sits. Fifteen numbered fields, including a description of the current process in AS-IS terms, the project purpose and the processes for which AI is to be applied, a description of the proposed solution, the expected economic or social effect, and a compute request broken out into CPU cores, number and type of GPUs, RAM in gigabytes, disk space in gigabytes, and the period of use.

Then the fields that matter legally. Field 9 asks for data sources and the legal grounds for using them. Field 10 asks for the categories of data used, with open data, personal data, restricted-access data and other data given as the examples. Field 11 asks for data protection and cybersecurity requirements. Field 12 asks whether integration with digital systems is needed and lists the expected integrations. Fields 13 to 15 name the planned number of authorised users, the list of users cleared to develop, test and host on the platform, and the persons responsible.

An applicant is therefore declaring its training data provenance and legal basis, on a state form, to a state-appointed operator, before it gets any compute.

Four criteria, four refusal grounds, and no appeal route in the text

Clause 5 lists what the operator reviews: whether the declared purposes of development or hosting comply with the requirements of Kazakh legislation; whether free compute resources exist in the volume and for the period stated in the passport; whether the proposed solution is compatible with the platform's software and technical architecture; and whether the declared data-use arrangements comply with Kazakh legislation on digitalisation, personal data and their protection, and cybersecurity.

Clause 7 mirrors those four as the exhaustive refusal grounds. Two are legal tests, one is a technical compatibility test, and one is simple capacity. A vendor can be turned away because the machines are busy.

Clause 9 says that after the reasons for refusal are removed the initiator resubmits, and the repeat request is considered in the manner and within the periods established by clauses 4 and 8 of the rules. Note what that cross-reference does not include: clauses 5 to 7, which carry the substantive review criteria and the refusal grounds. The desk reads that as a drafting slip rather than an intention to shorten the second-round review, but it is what the text says, and a resubmitting applicant has no clear textual answer on which criteria govern round two.

There is no appeal, no review body, and no complaint channel in the order. The only remedy the text supplies is cure the defect and file again. General Kazakh administrative procedure may supply more; the order does not, and we have not checked whether it does.

What the order does not do, which is most of what people will assume

There is no registration regime. There is no accreditation or licensing of AI developers. There is no conformity assessment, no certification, no notified body. Nothing in the order requires anyone to come to the platform in the first place, and nothing extends the rules to AI developed or deployed off the platform.

There is no data localisation rule in the order either. What clause 5 point 4 does is test the declared data-use arrangements against Kazakh personal data and cybersecurity law. That is a compliance-by-reference test, and its content lives in those other statutes, which we did not open for this piece.

There is no sanction. No fine, no suspension, no enforcement mechanism. Article 30 of the AI Law states in general terms that breach of Kazakh AI legislation entails liability established by the laws of Kazakhstan, which is a signpost rather than a penalty provision.

Anyone tempted to file this next to the EU AI Act should stop at the parent statute. Law 230-VIII does carry recognisably similar furniture, risk tiers, prohibited practices, synthetic content marking. The order under it carries none of that. It is an access-control document for one state facility, and describing it as Kazakhstan regulating AI would misstate what a reader can read in the text.

One thing that differs between the two language versions

The Russian and Kazakh texts were both extracted and compared on the definition of initiator, which is the term that fixes who the rules bind. They do not say quite the same thing.

The Russian definition at clause 2 point 1 identifies the initiator by the act of filing: a state body, legal person or natural person that has sent the operator a request for development or hosting of a platform software product or AI model. The Kazakh definition identifies the initiator by activity instead: a state body, and also an organisation or natural person that develops and hosts platform software products or AI models on the platform. The Kazakh version omits the request-sending element and uses organisation where the Russian uses legal person.

Practically the two probably land in the same place, because clause 3 in both versions makes the filing the trigger. The desk flags it because a definition keyed to activity rather than to filing reads slightly wider, and because anyone advising in Kazakh should not assume the Russian text is the only operative one. Both are published as authentic text on Adilet. We did not check whether Kazakh legislative drafting rules give one language priority in a conflict.

What we did not verify

What we opened and read in full: the Kazakh text of Order No. 482/NQ at adilet.zan.kz/kaz/docs/V2600039591; the Russian text of the same order at adilet.zan.kz/rus/docs/V2600039591; the Adilet registration card for the order; the full Russian text of Law No. 230-VIII ZRK On Artificial Intelligence; and the Adilet registration card for that law. The enacting formula was character-matched against the extracted Kazakh text and matches, including the double quotation marks around the law title and the trailing colon after the imperative verb. The extraction was clean Kazakh Cyrillic and Russian Cyrillic from the HTML text layer, not from a PDF, so no reordering risk applies.

What we did not open: the PDF and DOCX downloads of either instrument; the electronic reference control bank version at law.gov.kz; the English translation of the AI Law, which returned a connection error on the Adilet English path; Presidential Decree No. 997 of 18 September 2025 creating the ministry; Law No. 326-VIII of 24 June 2026 which amends the AI Law; and the Kazakh statutes on personal data protection, informatisation and cybersecurity that clause 5 point 4 cross-refers to. We also did not read any trade-press account of this order, by choice.

What we refuse to claim: we do not name the operator. The order defines it functionally as the legal person charged with ensuring development and functioning of the platform, and article 12(2) of the AI Law assigns the Government the job of designating it, but we did not find the designating act and will not guess an entity. We do not state the exact commencement date. Clause 4 sets ten calendar days from first official publication, the registration card gives 18 August 2026 as the publication date in the electronic reference control bank, and the arithmetic lands at the end of August 2026, but whether the count expires on 28 or 29 August depends on a Kazakh counting convention we did not verify. We do not assert the platform is operational, that any compute exists on it, or that any request has been filed. We take no position on whether refusal decisions are challengeable under general administrative procedure. And we do not claim the AI Law is unamended: the Adilet text carries editor notes on changes already enacted by the June 2026 amending law, several of which had not yet taken effect at the date of extraction.

Related briefings

• Kazakhstan Digital Code 255 on AI risk and human oversight
• Uzbekistan Decree PF-141 on AI and digital strategy
• UK AI Growth Lab regulatory sandbox
• Brazil ANPD AI regulatory sandbox
• AI Regulation News hub