Services ask for the fact they need
Evidence Gateway lets an approved service ask one predefined question and receive a signed answer instead of collecting the source facts again.
Open-source infrastructure for government registries and their partners
Answer the question. Keep the records.
Registry Stack helps the registries a government already runs provide what another service needs: one signed answer or selected data. The records stay with the authority that holds them.
The demo uses synthetic data only. No sign-up required.
Works alongside the platforms governments already run
How it works
How Registry Stack handles a request to an existing registry.
The registry owner defines who may request an answer or selected data, for what purpose, and what may be returned. Registry Stack applies those rules and records each request.
- 01
Connect the registry you already have.
Start with the system of record already in use. Prepare the reviewed view, extract, or fixed source connection required by the chosen product without replacing the registry.
- 02
Agree what can be asked and returned.
Define who may ask, for what purpose, and whether the service should receive one signed answer or selected fields.
- 03
Return only what was agreed.
Check each request against the reviewed definition, read the source, and return the agreed answer or selected data.
- 04
Keep a record of what happened.
The registry owner can see who asked, the purpose they gave, and whether evidence was provided or the request was refused.
What this changes
Services can use registry information without copying the full record.
A service can receive a signed answer or selected data directly. The source record remains with the registry owner.
Registries disclose less data
A clear answer or a few agreed fields can replace a database login, a full export, or another copy of the registry.
New service connections can reuse existing definitions
Once an authority has reviewed its Evidence requirements or Relay resources, another connection can start from those definitions instead of reopening every source decision.
In practice
Start with questions services already ask.
A pension program may need an age band. A payment system may need a supplier’s registration status. Neither needs the complete record behind the answer.
Civil registration
“Which age band applies to this person?”
Age band · 18-64 Social protection
“Is this household enrolled?”
Enrolled household Business registry
“Is this supplier actively registered?”
Active Farmer registry
“Send the full list of registered farmers.”
Refused · outside the agreed scopeTwo ways to start
Sometimes a service needs an answer. Sometimes it needs a few fields.
Registry Stack supports both through separate products. Evidence Gateway returns a signed minimum-disclosure assertion. Registry Relay exposes protected, selected data.
When a service needs proof
Evidence Gateway
Answer one predefined question against an authoritative source and return a signed, minimum-disclosure assertion.
- Answer defined questions such as “is this business actively registered?”
- The requesting service receives the answer, not the source record behind it.
When a service needs registry data
Protected Registry APIs
Provide read-only access to defined registry fields without giving out a database login or distributing copies of the source.
- Return agreed fields, metadata, or allowed counts through a protected API.
- Keep the existing registry as the official record and record each read.
Who it is for
For teams that need registries to work together.
Registry Stack is government-first. It helps registry owners, public-service teams, and their implementation partners agree what can be asked, then make that agreement work in practice.
Registry authorities
Provide signed answers or selected data while keeping the source records and deciding what each service may receive.
Public-service teams
Confirm facts such as enrollment, registration, or status without collecting more information than the service needs.
Digital delivery partners
Connect existing systems without creating another central database, and leave infrastructure the government can inspect and operate.
The same infrastructure can support regulated private-sector networks where one organization needs evidence held by another, but should not receive the source records.
Evaluate Registry Stack
Try the demo, review the software, and plan a pilot.
Current releases are for evaluation, integration pilots, and public review. The public roadmap records the work toward stable deployment and compatibility commitments.
Try the synthetic demo
The hosted lab illustrates registry-backed requests and protected reads with synthetic data. It is a demonstration, not a production integration reference.
No install or sign-up
Inspect and deploy the software
The products and documentation are Apache-2.0. Run them on infrastructure controlled by the government or its chosen operator.
Open source and self-hosted
Get help with the first registry
Aubex provides pilot design, source integration, deployment, training, and ongoing engineering support.
Delivery and support available
Built and supported by Aubex
Registry Stack is built by Aubex. Founder Jeremi Joslin brings experience from OpenSPP. Aubex also participates in Digital Convergence Initiative standards work and has contributed to the GovStack registry building block. Our engineers work directly with pilot teams and publish the code, documentation, releases, and security material for review.
Plan a pilot
Start with one registry and one service need.
We can help determine whether the service should receive one signed answer through Evidence Gateway or selected data through Registry Relay. We then define a pilot around that decision.