Use cases
A local authority maintains resident records. A procurement service checks a supplier. These illustrative examples show how Registry Stack can support the work and what remains under the organization’s control.
Two ways to start
Base Registry Engine
Store and manage records about people, households, organizations, or assets. Your applications can create, find, and update them under shared rules, with a history of changes.
Explore Base Registry Engine →Evidence Gateway
An approved service checks a fact held in an existing source. The gateway returns the agreed answer with a signature the service can verify.
Explore Evidence Gateway →These products can be used independently. When a service needs selected fields, Registry Relay provides another option.
Illustration: a civil register
A pension service checks whether a person is alive. A licensing service checks whether they are 18 or older. The registry owner defines the permitted questions and access rules; Evidence Gateway applies those rules to each request.
Kept by the civil registry
Maya Okafor
The registry owner maintains the record. The full record stays here.
Evidence Gateway
The registry owner defines which questions each service may ask.
Derive and sign only the agreed answer.
Data broker asks
Request not permitted
No source information returned.
Returned separately to each service
Is this person alive?
Pension service receives
Is this person 18 or older?
Licensing service receives
Where is this person registered?
Local office receives
Kept at source Date of birth, street address, marital status, and the rest of the record.
Audit Each request and its outcome are recorded.
Illustrative public-service scenarios
Each scenario shows a possible configuration. Your organization defines the records, permissions, and service rules for its own use.
People and households
Base Registry Engine
The result
Store person and household records, link them, and let authorized staff find and update the information through their application, with a history of changes.
What stays with the institution
The authority defines the records, runs the registry, and controls which details each role can access.
Businesses and establishments
Base Registry Engine
The result
Store and connect business and establishment records. Create registrations, look up existing entries, and keep addresses and status current under the registry’s rules.
What stays with the institution
The authority owns the register and sets the access, validation, and review rules used by its applications.
Civil registration
Evidence Gateway
The result
Return an age band such as “18–64”, calculated from the civil register.
What stays with the institution
Date of birth and the rest of the civil-registration record stay with the authority.
Social protection
Evidence Gateway
The result
Return the current enrollment status agreed by the social registry owner.
What stays with the institution
The household case file, income details, and payment history are not returned.
Business registration
Evidence Gateway
The result
Return a signed active or inactive answer for the supplier being checked.
What stays with the institution
Filing history, addresses, and ownership records stay in the business register.
Farmer support
Registry Relay
The result
Return the agreed fields, such as registered status and 2.5 hectares.
What stays with the institution
Plot coordinates, household members, crop history, and financial records are not returned.
Residence verification
Evidence Gateway
The result
Return a signed region value defined by the registry owner for the approved purpose.
What stays with the institution
The street address, household members, and rest of the source record stay with the authority.
A registry in a spreadsheet
Registry Relay
The result
The registry team prepares and maintains a reviewed extract. Registry Relay gives the partner access to the agreed fields.
What stays with the institution
The source file, database credentials, and unrelated rows are not distributed to the partner.
AI-assisted services
A service that uses AI to guide a person or caseworker can call the same configured Registry Stack interface as other services. Registry Stack checks the service’s permission for each request and returns only the information its rules allow.
The choice is the same as for any other service: copy the records, or ask the question. A housing benefit service could receive a copy of each applicant’s income records and let its application work them out. Or the registry owner defines one question, such as whether annual net income is below the benefit threshold, and the registry returns that answer. The registry may hold gross monthly income while the rule needs net annual income; the definition of the question carries that translation, and the AI-assisted service never holds the record.
The service owner remains responsible for how the application uses that information, including decisions about eligibility, approvals, and the people it makes requests about.
For developers
The tutorials introduce each product through the exercises below. The scenarios above are illustrations for discussing your own use case.
Create a sample business record, change its label, and try requests the server refuses.
Base Registry Engine introductory tutorial →Ask whether a synthetic person is an adult and verify the signed answer.
Evidence Gateway introductory tutorial →Publish a sample business register that returns legal name and legal form, and refuses a request for the address.
Registry Relay introductory tutorial →Take the next step
Evaluate the open-source software with your team, or get paid implementation help and ongoing support.