Registry infrastructure for institutions that already have the data

Serve the registries you already have. Share only what each request requires.

Registry Stack puts a governed service surface over registry data you already operate: a published metadata contract, protected read-only APIs, and configured evidence answers.

Built to complement the domain platforms you already run (OpenCRVS, OpenSPP, DHIS2, OpenIMIS, and others), and the workflow engines, exchanges, and wallets that consume their answers.

Choose where to start See capabilities Read a worked example

The problem

Data exists. The service contract around it often does not.

No safe service surface Data exists in files, extracts, databases, or legacy systems, but other services cannot depend on a clear, approved interface. Too much disclosure Callers need a status or evidence response, but broad record APIs move more data than the purpose requires. No technical enforcement Data-sharing agreements describe intended access on paper. The API itself has no scopes, no purpose field, no disclosure limits, no audit record.

The operating model

Three steps. In order: describe, expose, certify.

1. Describe the registry

   Registry metadata names the fields, schemas, policies, services, and evidence offerings the registry actually publishes. Other teams can read the contract before integrating.

   Describe registries
2. Expose it safely

   Registry Relay serves protected, read-only, entity-shaped routes over the source data. Callers authorize, scope, and audit at the API layer, not at the source.

   Expose protected APIs
3. Return only the evidence the call needs

   Registry Notary evaluates configured claims and returns the shape the caller is entitled to: a status, predicate, selected value, or signed credential.

   Certify evidence

Start from your situation

Find the path that matches your job.

Decision-maker See project ownership, boundaries, and how the registry services fit together. Registry owner Put a governed API in front of a file, extract, database, or legacy registry. Service integrator Verify a status fact about a registered entity without pulling the full record. Ecosystem partner See where Registry Stack fits alongside the platforms, exchanges, wallets, and standards you already use.

Scope

Focused registry infrastructure, not another whole platform.

Product focus

• Registry Relay for protected read-only registry APIs.
• Registry Notary for configured evidence responses.
• Registry metadata for inspectable contracts and offerings.

Explicit boundaries

• Does not replace exchange layers, workflow engines, wallets, or public-service platforms.
• Does not solve foundational identity, deduplication, or semantic governance on its own.