Model the information you need
Define record types, required fields, valid values, and relationships. Your registry can hold several kinds of records together, such as people, households, and memberships.
Base Registry Engine
Build and run the base registry others rely on.
A base registry is the register one organization is responsible for and other services use instead of asking people for the same information again: residents, businesses, addresses, licences, assets. Base Registry Engine stores those records with your rules for access, data quality, and change, and gives your applications one consistent way to create, find, and update them.
From the first record to years of changes
Create, connect, and maintain your records.
A local authority could use the engine for a registry of residents and households. Staff register people, find existing records, and update details as circumstances change. The engine stores the information and its history; your application provides the screens.
Stored in Base Registry Engine
Person record P-1042
Amara Mensah
- Date of birth
- 16 March 1992
Member of household
Household record H-208
- District
- Northfield
Two linked records, each with its own fields and change history.
Register and connect
Create a person’s record and link it to a household. The engine checks required information, permitted values, and references before saving it.
Find and use
Look up a resident or retrieve the people linked to a household. Each application can access the records and fields its permissions allow.
Keep up with changes
Correct a detail or update a household relationship. The engine stores the current information and preserves earlier revisions so authorized users can follow what changed.
Your records, your rules
A shared foundation for your applications.
Define the registry once, then use it across the applications that maintain and consult it. The engine applies the same configured rules to each request.
Control access and changes
Decide which records and fields each role can read or change. Allow routine updates directly and require review where needed, including a set number of approvals before a change takes effect. Related changes can be applied together so they stay consistent.
Keep continuity over time
Inspect earlier revisions and prevent an older edit from overwriting a newer change. As your needs evolve, update the record definitions through versioned configuration and planned data migrations.
One solution, several products
What a base registry owes the services around it.
The term comes from public-sector interoperability: the Dutch basisregistratie, the Belgian authentic source, the foundational registries of identification programmes. Whatever the name, a base registry carries the same duties, and Registry Stack has a product for each. Start with the engine and add the others when a duty becomes real.
- Hold the authoritative records
- Base Registry Engine stores the records and their history and applies your rules for who may read or change what.
- Let other services rely on the register without copying it
- Evidence Gateway answers a defined question, such as an age check, with a signed fact and no full record. Registry Relay publishes the fields each service is allowed to receive.
- Take back corrections and decide on them
- A service that spots a wrong record has to report it, and someone has to review it. Casework gives the officers who do that one accountable inbox, and the registry keeps its own rules about who may change a record.
- Answer for it afterwards
- Every change and refused request is journaled with who asked and who decided, so a reviewer can reconstruct what happened without asking the people involved.
How it fits your organization
Build your services around a registry you control.
Your organization owns the records and runs the engine and its database on infrastructure you control. Connect staff applications, public services, and other systems through the registry’s interface.
Use it to build a new registry or move an existing register into a defined structure, with a planned migration of its records.
- Your team defines the registry
- Agree what the records mean, how they relate, and who may use them. Your technical team translates those decisions into the configuration that defines storage, validation, and access.
- Your applications serve the people using it
- Your team or delivery partner provides the screens, sign-in, and wider service workflows. The engine handles record storage and operations behind those applications.
- Add the other products when a duty becomes real
- Each product runs on its own. Connect Evidence Gateway, Registry Relay, or Casework to the registry when another service needs a fact, a data feed, or a person’s decision, and not before.
For developers and implementers
Create your first registry and work with its records.
The introductory tutorial uses a sample business register. Create and update a record, try a request that should be refused, and inspect the generated interface description.
Run the first registry tutorial →
To explore optional review, a second tutorial uses an asset-location correction: propose a different site, collect two approvals, and apply the change.
- Database and application interface
- A versioned model defines the PostgreSQL structure, validation, REST API, and OpenAPI description. Existing records require an explicit migration into the registry.
- Changes that belong together
- Configured actions can create or update several records in one transaction. Changes to the model are reviewed and tested, with a database migration where the structure changes.
- Continue in the documentation
- Read how a configuration-defined registry works for the model, permissions, and application boundary. The tutorials provide their prerequisites and executable steps.
Work with us
Get help when you need it.
Get hands-on help through a paid implementation pilot, or ongoing support while your team builds and runs the solution.
Implementation and support