What’s Plumbed In, and What Isn’t: Reading Tunduk’s 2024 Monitoring Data

In 2016 and 2017, sitting first as a public adviser in the Presidential Administration and then in the Office of the Prime Minister, I spent a meaningful share of my advocacy capital on a single technical proposition: that Kyrgyzstan should import the architecture behind Estonia’s X-Road. The argument was not glamorous. X-Road is not a citizen-facing app. It does not produce photogenic launches. It is the data-exchange backbone that lets one part of a digital state ask another part of the same state for a piece of information about a citizen, in milliseconds, without paper, without queues, and without the citizen having to carry a bundle of documents from one window to the next.

The advocacy worked, and the architecture was eventually adopted, reframed, and branded locally as Tunduk. Of all the things that have happened to Kyrgyz digital governance in the last decade, this is the one I would still defend first if asked which single decision mattered most for the country’s digital sovereignty and resilience. Tunduk is a success. It is also, six years into operation, a long way from finished. The most useful way to look at it now is not in terms of whether it works — it does — but in terms of what is plumbed in, and what isn’t yet.

The State Institution «Tunduk» under the Ministry of Digital Development publishes monthly exchange reports — the equivalent, for an X-Road-class system, of a control-room read-out. They list, in plain table form, which agency requested what data from which other agency, how often, and how often the request succeeded. This piece is built on six of those reports, covering January through June 2024. It treats the data the way I would treat a network capture: as the operational truth of an architecture, regardless of what was promised about it earlier or planned for later.

What X-Road actually is, and why Tunduk matters

X-Road, the Estonian original, solved a specific problem. In any country with a working bureaucracy, citizen data lives in many separate registries: civil status, taxation, vehicles, property, health, social benefits, court records, business registration. Each registry has a legitimate owner and its own access rules. When a citizen interacts with the state — applying for a benefit, registering a car, paying a fine, attending a clinic — the response usually requires several of these registries to confirm something to each other. The traditional answer was paper: the citizen carries the documents between windows. The modern answer was supposed to be data-sharing. The intermediate, common, and unhelpful answer was each ministry building its own siloed digital system that did not speak to anybody else’s.

X-Road’s contribution was a federated message-bus pattern that is, in retrospect, almost obvious: every registry stays where it is, every ministry retains ownership, and a layer of standardised, signed, mutually authenticated services lets one part of the state ask another part for a defined piece of information, with audit, with revocation, and with no central database that anyone has to trust. Estonia ran on this. Finland adopted it. Several other countries have built local variants. Kyrgyzstan is the Central Asian member of this family, branded as Tunduk. The brand is local; the engineering pattern is the imported one.

The reason the advocacy in 2016–2017 mattered is that the alternative — and the path several other countries in the region took — was building a series of bilateral integrations between ministries, each negotiated separately, each dependent on the political relationship of the day, and each producing a fragile, unaudited, gradually obsolete piece of bespoke wiring. The Tunduk model, by contrast, scales because every additional consumer or producer plugs into the same bus. The system gets stronger with every ministry that joins. And every additional connection reduces the number of times a Kyrgyz citizen has to physically carry a piece of paper from one window to another.

Reading the 2024 monitoring data: who is on the bus

The first useful read of the 2024 reports is the participant list. Across the six monthly windows, the producer-and-consumer columns name the institutions that are actually exchanging data over Tunduk in production. The picture is broader than is usually credited.

The list is striking on its own. Almost every line ministry of the executive branch is on the bus. The full court system — prosecutor, courts, court department, probation, penal service, legal aid — is on the bus. The financial sovereignty stack — National Bank, MoF, Tax, Customs, Financial Intelligence, Statistical Committee — is on the bus. The two main social-welfare entitlements — pension and mandatory medical insurance — are on the bus. The cadastral and intellectual-property registries are on the bus. The MVD’s own e-services portal is on the bus. The sanctions list is on the bus. By any honest read of the participant column, Tunduk has reached operational scale across the executive and judicial branches of the Kyrgyz state.

The shape of the queries: what the state actually asks itself

The second useful read is the service column. What gets asked across this bus, in production, in 2024? The answer falls into a small number of recurring patterns, all keyed off the citizen’s PIN (Personal Identification Number) — the Kyrgyz analogue of an SSN or a national ID number.

• Identity verification. Address registration by PIN, citizen photo by PIN, passport details by PIN, family-member counts and children-of-citizen lookups, foreign-citizen lookups by document number, foreigner status verifications.
• Civil status. Birth records, marriage records, death records — pulled from the ZAGS (civil registry) and made queryable by other ministries that need them as input to a benefit or service.
• Vehicles and licences. Vehicle ownership by PIN, vehicle technical parameters, the most recent driver’s licence by PIN, vehicle search registries.
• Justice and enforcement. Outstanding fines by PIN (multiple variants — Tunduk-aware, plate-aware, civil-tolom-bound), judge-assignment data, debtor data with case-detail context, suspect-arrest lookups, prisoner-status checks under the Penal Service.
• Property. Movable property checks, immovable property checks, owners by property code, property information for sale, beneficial-ownership lookups.
• Tax and finance. Income data aggregated at four different category levels, insurance data, payment-document confirmation, tax-payment dates by INN, patent-policy payment status, e-payment information.
• Health. Vaccination records routed both to the GPEU portal and to the Tunduk mobile app, patient lookups, vaccine reference data, mandatory medical insurance status.
• Apostille and external recognition. Document-data verification, payment confirmation for apostille, both production and test-environment endpoints visible in the public reports.

The composite picture, read service by service, is a digital state whose interoperability layer has matured to the point where a Kyrgyz citizen’s interaction with one part of the state can, in principle, draw on every other part of the state’s record on them, in real time. The kind of cross-ministry workflow that ten years ago required a stack of stamped paper now requires a single PIN-keyed message on Tunduk. That is precisely the outcome the X-Road argument was made for.

The most-queried families of services

The reports also publish per-service Failed / Succeeded / Total counts. Without disclosing protected per-citizen detail, the operational read across the six 2024 windows lands as follows: identity-verification queries (address by PIN, passport details by PIN, family composition) are the highest-volume category. Justice-side fines and debtor lookups are the second highest-volume category, with multiple variants of fine-search keyed off PIN and licence plate. Civil-status records — birth, marriage, death — sit close behind, queried as input into services across the social and migration domains. Vehicle and licence lookups form a sustained background load. Health-side vaccination and insurance flows grew across the window, consistent with the public expansion of the GPEU vaccination service and the Tunduk mobile app.

Service family	Anchored on	Operational role
Identity verification	PIN	Backbone for almost every other workflow
Justice / fines / debtor data	PIN, plate, INN	Used by enforcement and citizen-facing payment flows
Civil-status records	PIN, ZAGS	Birth / marriage / death, fed into social, migration, education
Vehicles and licences	PIN, plate	Used by traffic, customs, social services
Tax and income	INN, PIN	Aggregated at four category levels for cross-checks
Health and insurance	PIN	Vaccination records, MMIF status, patient lookups
Property and ownership	Property code, PIN	Cadastral and beneficial-ownership checks
Apostille and external recognition	Document number	Document verification + payment confirmation

What is not yet plumbed in

The honest part of any account of Tunduk in 2024 is the part that names the gaps. The participant list reads broad because it is the executive and the judicial branches; it is much narrower as soon as one looks below ministry level, sideways to private institutions, or outward to the layers of the state where most citizens actually meet government.

• Local self-government. The Aiyl Okmotu — the rural municipal-level administration that for most Kyrgyz citizens is the first and most frequent face of the state — does not appear as a Tunduk participant. The internal digitisation of an Aiyl Okmotu typically means a 1C accounting installation and the SPM (Social Passport of Poor Families) form-filling system, neither of which sits on the country’s interoperability backbone. The street-level integration is missing.
• Schools and clinics as endpoints. The Ministries of Education and of Health are on the bus. The institutions they oversee — schools, clinics, hospitals, vocational colleges — are not Tunduk participants in their own right in the 2024 reports. Where Tunduk reaches into health, it does so at the platform layer (vaccination data routed through the GPEU and the Tunduk mobile app), not at the level of the individual clinic. Where it reaches into education, the integration is similarly thin.
• Private-sector consumers. Banks, insurers, fintech platforms, telecoms, e-commerce operators, and licensed professional bodies are the classes of consumer for which X-Road-class systems eventually deliver the most economic value. They are not visible as Tunduk consumers in the 2024 monitoring window. The interoperability stays inside the state’s perimeter.
• Educational outcomes and credentials. The Digital Mektep Information System exists at MES level. Diploma verification, credential checks, professional-licence lookups — the parts of education and employment most useful to integrate with everything else — do not appear as services on the bus.
• Cross-border interoperability. Several of the country’s neighbours run their own X-Road or X-Road-adjacent systems. Cross-border interoperability — the bilateral message-bus pattern that has, for example, started to connect Estonia and Finland — is not visible in the Kyrgyz reports. The country’s data-exchange backbone is, for now, a domestic backbone.

None of these gaps is a failure of Tunduk. They are the next phase of the same project. The platform has reached the point where the missing layers are not technical questions about the bus itself; they are organisational and policy questions about who is allowed to plug in, on what terms, and to do what.

What the architecture has and has not yet produced

Read against the 2016–2017 advocacy, three things have happened, two as predicted and one as a surprise.

• The federated pattern held. Tunduk did not become a centralised mega-database. Each ministry kept ownership of its data; the bus did the message-bus work. Six years on, the architecture’s first promise — that scale would not require central control — is intact.
• The participant list did broaden. The 2024 monitoring data shows a participant set that, in scope, looks more like the mid-period Estonian X-Road than like the early Kyrgyz pilot. The executive and judicial branches are largely on the bus.
• The benefit ledger lags the connectivity ledger. What the platform does not yet show is a clear public read on the citizen-time and citizen-money saved by the integrations. Estonia produces those numbers as a matter of routine. Kyrgyzstan does not. The economic case for further integration is being made, but it is being made without the operational instrumentation that would allow it to be made well.

Tunduk is the part of Kyrgyzstan’s digital decade that I would still defend first. The work that follows it is the work of pushing the bus into the parts of the country where most citizens actually meet the state.

The next pieces in the wider series move from the interoperability backbone to the layers it now needs to reach: local self-government, schools, clinics, and the private-sector consumers that turn a state-internal bus into a national digital fabric. None of those steps require building a new platform. They require taking the platform that has been built and wiring the next layer in.