For governments, funders, and implementing partners
Registry Stack’s open-source products are digital public infrastructure: shared rails that let the registries a government already holds answer questions safely. A pilot does not begin with a replatforming program. It begins with one registry, one question a service keeps asking, and safeguards enforced from the first request.
What a pilot buys
The once-only principle, made operational: a fact the government already holds is answered by the registry that holds it, instead of being re-documented at every counter. Fewer certified copies, fewer queues, fewer reasons to drop out of a service.
A zero-trust posture for registry data: no caller is trusted by default, and purpose, scope, and disclosure limits are checked on every request, not promised in a signed agreement nobody can verify. Every trust-critical request leaves an audit record a reviewer, an inspector, or a court can actually read.
A one-off integration project leaves behind code two people understand. A pilot on shared rails leaves behind a described, governed registry surface that the next program reuses, which is the difference between an IT project and digital public infrastructure.
Registry Stack runs alongside the platforms governments already choose, including OpenCRVS, OpenSPP, DHIS2, and MOSIP, and behind X-Road-style exchange layers. Nothing is replaced and nothing migrates.
The shape of a pilot
Three phases, each with something concrete to show. The scope is set by the registry owner and the asking service, not by a product roadmap. Your team can evaluate every product free before any paid support starts. A supported pilot is the published First registry package, with scope confirmed against the registry, service question, deployment path, and governance owner.
A civil register, a household register in a spreadsheet, a farmer registry export: any source counts. Pair it with one question a service keeps asking of it, with a yes-or-no or bounded answer.
Stand up the same flow the hosted lab runs, on synthetic records shaped like yours. Stakeholders watch a signed answer land in a wallet before any real record is touched.
Connect the real source read-only, scope the route to its stated purpose, and let the audit trail run from day one. The registry keeps its records; the service gets its answer.
The division of work
Who is behind this
Registry Stack is built in the open by maintainers who work in social protection, DCI standards, and GovStack specifications. The code, the documentation, and the hosted lab are public: what this site claims, you can check.
Paid pilot support starts when there is a concrete registry, a concrete service question, and an institutional owner who can approve purpose, access, and safeguards. For earlier exploration, start with the docs and hosted lab.
Request pilot scope →For your technical team