FAQ

What would Registry Stack mean for your team?

Product fit, control of your records, and the choice between self-service evaluation and paid implementation or support.

Choose what fits

What does Registry Stack help us do?

Base Registry Engine stores and manages records about people, households, organizations, assets, and more. Your applications can create, find, and update those records under your rules. Evidence Gateway lets approved services receive signed facts from a source your organization controls, without receiving its full records.

See illustrative use cases →
Do we need both main products?

No. Base Registry Engine stores and maintains your organization's records. Evidence Gateway can answer questions using an existing source. Each can be used independently. If you choose to combine them, your technical team configures their connection.

Explore the product choices →
Can we keep our existing registry?

Yes. Evidence Gateway can use an existing source to answer configured questions, such as whether a supplier is actively registered. When a service needs selected fields instead, Registry Relay can provide access to data your team prepares from that source.

Explore Evidence Gateway →
What is Registry Stack not?

It is not a central data store, a data exchange platform, or a replacement for the applications your staff use. It does not copy your registries into one place, and it does not decide eligibility for you. Each product does one job beside the systems you already run: hold records, answer a defined question, publish selected fields, or coordinate the officers who review changes.

Read how it sits beside existing systems →

Your records and your applications

Who owns and controls the records?

Your organization does. You decide who may create or change a record, which services can ask for information, and what they may receive. The software applies the rules your team configures. You host the deployment; the software does not send your records or audit logs to Aubex.

Understand the security responsibilities →
What does our team supply?

Your organization defines the records and access rules, provides the application people use, and operates the service. Base Registry Engine handles record storage, relationships, and controlled access and updates. Evidence Gateway connects to a source your team makes available and returns the answers you have defined.

See how Base Registry Engine supports your application →
Can we start from a spreadsheet or legacy database?

Yes, with preparation by your technical team. To share selected information with Registry Relay, your team prepares and maintains a reviewed extract. To move records into Base Registry Engine, your team defines the record structure and plans the migration.

Explore Registry Relay →
Does every new question mean a new integration project?

No. The registry is connected once. Each further question a service asks is a configuration change: your team defines the answer, its source, and who may receive it, and reviews that definition before it goes live. The first connection carries the integration cost; later questions reuse it.

Read how to define the question first →

Evaluation and paid support

Is there a software license fee?

No. Registry Stack is Apache-2.0 open-source software. Your team provides the hosting, implementation, and operation. Self-service use is separate from paid delivery and private support.

Read the documentation →
What can our developers try?

The Base Registry Engine tutorial creates and updates a sample business record. The Evidence Gateway tutorial checks a synthetic person's adult status and verifies the signed answer. The Registry Relay tutorial publishes a sample business register with two permitted fields. Each tutorial explains its prerequisites and steps.

Choose an introductory tutorial →
What implementation and support services are available?

We can help deliver a scoped implementation pilot. If your team handles implementation itself, you can choose an ongoing support contract. Both are paid services, with the scope and fee agreed before work begins. You can discuss your needs before installing the software.

See implementation and support pricing →

Take the next step

Explore it with your team.

Evaluate the open-source software with your team, or get paid implementation help and ongoing support.