Digital systems for the public and quasi-public sector
We build and evolve systems for quasi-public companies, state enterprises and government bodies: portals and customer accounts, CRM and ERP, document workflows, integrations with digital signature and government systems. Kazakhstan's requirements are built in from day one: data on servers in Kazakhstan, Kazakh and Russian interfaces, source code and rights stay with the client.
- Data in Kazakhstan
- Kazakh & Russian
- Digital signature
What does a system for a government client in Kazakhstan need?
A system for a government body, state enterprise or quasi-public company must keep data on servers in Kazakhstan, work in Kazakh and Russian, sign documents with the NCA RK digital signature, exchange data with government systems through the digital government gateway, and pass cybersecurity compliance testing. These requirements come from the Digital Code of Kazakhstan (in force since 12 July 2026), the Law on Cybersecurity and the Unified Requirements (Government Decree No. 832). A contractor builds them into the architecture, documentation and plan before development starts — otherwise the system gets reworked after review or testing.
Who we work with in the public sector
Quasi-public companies and their subsidiaries
National companies, holdings and their group organisations: internal CRM and ERP, portals for clients and partners, document workflows and reporting. They buy under their own procurement rules — we work in their format.
State enterprises and institutions
Automation of internal processes, customer accounts, request handling and reporting to higher authorities — with data stored in Kazakhstan and a bilingual interface.
General contractors and system integrators
You need a technical partner for one part of the project: a module, an integration, a mobile app or a web account. We work as a subcontractor — the team has this experience.
Companies working with the state
Private systems that need to exchange data with government systems: digital signature, connection through the external digital government gateway, eGov services.
Problems we solve
Data must be stored in Kazakhstan
We host the system and databases on servers in Kazakhstan data centres. Cloud is acceptable only if servers and control centres are physically in Kazakhstan — the Unified Requirements demand this for government systems and systems integrated with them, and the personal data law for databases with personal data.
Documents must be signed with a digital signature
We connect signing through NCALayer and eGov QR, check certificate status, store the document with all signatures and timestamps, and support export and import of signed documents.
The system must exchange data with government systems
We build an integration module to the digital government gateway requirements (formerly the e-government gateway): signed requests, reuse of existing gateway services. The operator connects the system on the owner's application — we plan for its timelines.
The interface and documentation are needed in two languages
We build Kazakh and Russian interfaces with a language switch, and technical and user documentation in both languages. Kazakh texts are proofread before delivery.
The system must be prepared for testing
We build in event logging, log export and a document package for cybersecurity compliance testing, and fix the findings. The testing itself is done by the State Technical Service or an accredited laboratory.
What the work includes
items
- Review of the task, the client and the engagement format: direct contract, subcontract or pre-project work
- Requirements analysis: Unified Requirements, data residency, languages, integrations, accessibility
- Architecture and technical documentation in the scope needed for expert review
- Prototype of key screens in Kazakh and Russian
- Development in sprints with working demos
- Digital signature module: NCALayer, eGov QR, certificate checks, signature storage
- Integrations with government systems through the gateway, with 1C, EDMS and internal systems
- Event logging and a document package for testing
- Hosting on servers in Kazakhstan, backups
- Handover of source code, build and deployment instructions
- Pilot operation, a 12-month warranty and support
Ways to work with government clients
The format determines how the contract is concluded and what is required of the contractor. We choose it together with the client or the general contractor.
| Format | When it fits | How it works |
|---|---|---|
| Direct contract under a procurement | A procurement by a government or quasi-public client: request for price quotations, single-source procurement, a quasi-public tender | Contract and payment follow the procurement rules and the client's contract terms |
| Subcontract to a general contractor | An integrator leads a large project, and a partner is needed for one part: a module, an integration, a mobile app | A contract with the general contractor; under the public procurement law up to 30% of the volume can be subcontracted |
| Pre-project work | A process survey, terms of reference or a prototype is needed before the procurement | A separate contract. We do not take part in the procurement based on those terms — the law requires this |
The public procurement law bars anyone who provided services to prepare a procurement from taking part in it. So we never combine writing the terms of reference with bidding in the same procurement.
How we design to Kazakhstan's requirements
Public sector requirements go into the architecture before development — rework after expert review or testing costs more.
| Requirement | What we do |
|---|---|
| Data residency in Kazakhstan | Servers and databases in Kazakhstan data centres; cloud only with servers in Kazakhstan |
| Kazakh and Russian | Bilingual interface with a language switch, documentation in both languages |
| NCA RK digital signature | Signing via NCALayer and eGov QR, certificate status checks, signatures stored with the document |
| Integration with government systems | A module for the digital government gateway; the operator connects it on the owner's application |
| Logging | Event log and log export for monitoring and testing |
| Open-source software | A widely used open stack: PostgreSQL, Node.js, React |
| Source code | Handover of source code, build and deployment instructions, a reproducible build |
| Accessibility | Interfaces designed with accessibility requirements for people with disabilities (ST RK 2191-2023) |
| Testing | A document package for cybersecurity compliance testing, fixing the findings |
The regulations we rely on
The list was checked on 23.10.2026. Regulations change: since 12 July 2026 the Digital Code is in force, "e-government" became "digital government", and the Law on Informatization became the Law on Cybersecurity.
| Document | What it means for the project |
|---|---|
| Digital Code of Kazakhstan No. 255-VIII | Life cycle of digital objects, integration through the gateway, digital signature, a warranty of at least one year |
| Law on Cybersecurity No. 418-V | Cybersecurity requirements, mandatory testing, bilingual information in government systems |
| Unified Requirements (Government Decree No. 832) | Hosting in Kazakhstan, interface languages, digital signature, source code handover, accessibility |
| Law on Personal Data and Its Protection No. 94-V | Databases with personal data stored in Kazakhstan |
| Law on Public Procurement No. 106-VIII and Rules No. 687 | Procurement methods, supplier requirements, subcontracting up to 30% of the volume |
| Law on Procurement by Certain Quasi-Public Sector Entities No. 47-VII | Procurement rules of national companies, holdings and their groups |
This is a planning reference, not legal advice: the requirements of a specific procurement are set by its documentation.
Contract, warranty and code
For government and quasi-public clients the procurement sets the payment terms, while the warranty and the rights to the result are the same in every project.
| Term | How we work |
|---|---|
| Payment and security | Under the procurement rules and the client's contract terms |
| Warranty | 12 months after going into production: we fix defects in our code free of charge |
| Testing findings | Fixed within the contract |
| Code and rights | Source code, documentation and rights to the result stay with the client |
| Confidentiality | NDA on your template or ours |
We follow procurement rules
A government client needs procurement and acceptance results that cannot be challenged. So we keep to a few rules.
Terms of reference and bidding kept apart
If we prepared the terms of reference for a client, we don't bid in the procurement based on them: the public procurement law requires this, and it protects the procurement results from challenges.
Testing by authorised organisations
Cybersecurity compliance testing is done by the State Technical Service or an accredited laboratory. We prepare the system and documents and fix the findings.
A realistic offer
The timeline and scope in our offer are what we will deliver under the contract — including approvals, testing and gateway connection.
How a project runs
- 01
Task and format
We review the task, the client and the engagement format: direct contract, subcontract or pre-project work. We estimate procurement and approval timelines.
- 02
Requirements and architecture
We consolidate requirements: data residency, languages, digital signature, integrations, accessibility. We design the architecture and the documentation scope.
- 03
Prototype
We show key screens in Kazakh and Russian before development — the client's users see the system early.
- 04
Development
We work in sprints with demos. Integrations and the signature module are verified in test environments.
- 05
Pilot and testing
We launch for a limited group of users, prepare documents for testing and fix the findings.
- 06
Launch and warranty
We hand over source code and documentation and support the move to production. Warranty: 12 months.
Get your project assessed before development starts
Describe the task in the form below — we reply within a business hour and suggest the next step: a call, a review or an estimate.
Technology
We use a widely adopted open stack: plenty of engineers on the market, no dependency on one contractor or rare licences. Hosted in Kazakhstan data centres.
- TypeScript
- Node.js
- PostgreSQL
- React
- Next.js
- Docker
- Event log
- Servers in Kazakhstan
Integrations
A public sector system rarely works alone: documents are signed digitally, data is checked against government databases, accounting runs in 1C. We design exchanges so data is entered once.
NCA RK digital signature, NCALayer, eGov QR, Digital government gateway, eGov services, 1C, EDMS
FAQ about working with the public sector
Yes. Under the law, a supplier in public procurement can be an individual entrepreneur or a legal entity. We work through direct contracts under a procurement (request for price quotations, single-source procurement, quasi-public tenders) and as a subcontractor to a general contractor.
Yes. We take on separate parts of a project: modules, integrations, mobile apps, web accounts. The public procurement law allows subcontracting up to 30% of the contract volume. The team has subcontracting experience.
On servers in Kazakhstan data centres. The Unified Requirements demand this for government systems and systems integrated with them, and the personal data law for databases with personal data.
Yes. We build Kazakh and Russian interfaces with a language switch and documentation in both languages. Kazakh texts are proofread before delivery.
The State Technical Service for government objects, accredited laboratories for the rest. We prepare the system and documentation for testing and fix the findings.
12 months after going into production: we fix defects in our code free of charge. For digital government objects the Digital Code requires a warranty of at least one year.
Yes, under a separate contract. But then we don't take part in the procurement based on those terms: the public procurement law bars anyone who helped prepare a procurement from bidding in it.
Since 2026, new systems implementing government functions are built on the QazTech digital government platform. In such projects we join through integrators and the platform operator. Quasi-public companies and state enterprises commission systems directly.
Related services
Let's discuss the project and the engagement format
Describe the task, the client and the procurement timeline — without personal data or restricted documents.
- The first short conversation is free — we choose the format
- NDA — yours or ours
- Pricing after a brief and an agreed scope