Kazakhstan
Planned
Where data lives in the pilot today, what Planned means for a Kazakhstan cell, the printable statement and tenge invoices, which Kazakh services connect, and the Kazakh and Russian interface. No claim we cannot back.
Qaldy Cloud is built for companies in Kazakhstan and Central Asia first. This page says what is true today for a company there, what is planned, and what we will not claim until it is true.
Where your data is today#
The pilot is one cell:
| Part | Where |
|---|---|
| The console | Cloudflare Pages, served worldwide from the edge |
| The API, the MCP server, the database and the authorization service | AWS, Frankfurt (eu-central-1) |
| The sandbox that runs apps | Cloudflare's network (Workers). The pilot does not pin an app to a region; pinning is Planned |
| The gate that holds your keys | AWS, Frankfurt, with a fixed outbound address |
| Email codes | Resend, from login@mail.qaldy.com |
The honest sentence for your records is: the pilot stores data in the EU (Frankfurt) and on Cloudflare's network; storing personal data of Kazakh residents in Kazakhstan is planned, not live. If your obligations require storage in Kazakhstan today, Qaldy Cloud is not ready for that data yet, and whether they do is a question for your counsel, not for this page.
The statement you can print#
Auditors ask "where is the data, who touches it, and what happens to a backup". Where your data lives answers it for your workspace: the cell that holds it, every company that processes it and what they see, a list of what lives where, the backups and how long they are kept, and, in full, what the statement does not claim. It is made in Russian, Kazakh or English and printed or saved as PDF from the console. See Where your data lives. Preview
Invoices and acts in tenge#
A workspace owner or admin can issue an invoice and, for a finished month, an act of completed work in tenge, with the company's BIN or IIN and a VAT line, mark it paid by hand, and print it. Billing is mock, so until Qaldy's own legal entity is set up each document says not a tax document. See Invoices and acts. Preview
Data and AI policy#
When you create a workspace you choose a data and AI policy. Today only the pilot cell exists, so the choice narrows which connectors and models your apps may use, not where they run:
- Global is the default and the pilot cell.
- Kazakhstan allows frontier models only with personal data removed first and nothing retained, or open models hosted in Kazakhstan.
- Kazakhstan, strict allows only open models hosted in Kazakhstan (there are none yet) and only the connectors that operate in Kazakhstan. No public links.
- A policy is not a promise about where the bytes are: every profile stores in the pilot cell until a Kazakhstan cell exists. The console says so, in the same words, where you choose one.
The Kazakh stack works today#
You do not have to wait for a cell to connect the services a company in Kazakhstan runs on:
ESF and 1C: what we will and will not do#
Kazakhstan's electronic tax invoices (ESF) and the 1C accounting system matter to most companies here. After desk research on 2026-10-18 (nothing was run against the tax system or a 1C server, and it is not legal or tax advice) the position is:
- Qaldy will not issue ESF on your behalf. Signing an ESF needs the signer's own electronic digital signature, handing that to a third party is not allowed as far as the sources we read say, and some taxpayers also have to pass a face check. A service that held your key would be signing as you. 1C already issues ESF itself, with the signing done on your accountant's computer.
- Reading from 1C is the part that fits. 1C can publish a standard HTTP interface. An automation that reads unpaid invoices, stock or sales from it and then sends a Telegram reminder fits the sandbox-and-gate model. A 1C connector is Planned and will be built, if at all, as read-only and in Preview after it is checked with the partners who run 1C for companies here. Until then the HTTP connector can reach a 1C interface that you have published.
- The act of completed work that Qaldy prints is a document in the style of the usual Kazakh form, not an ESF and not filed with the tax system.
In your language#
- The console is in English, Russian and Kazakh. Pick the language in settings, or add
?lang=ruor?lang=kkto the landing page. - Getting started is in Russian and Kazakh.
- Prices can be shown in tenge. The rate card holds a tenge price for every plan.
- The Russian and Kazakh text was written by us and has not had a native read. If a sentence is wrong or awkward, tell us.
What we are working on#
- A decision on the shape and the provider of the Kazakhstan cell.
- Qaldy's own legal entity set up as the seller, and the tenge prices checked by an accountant, so that documents stop saying "not a tax document".
- A 1C connector, read-only.
Nothing on that list is live until this page says so.