Ecosystem fit
Registry Stack assumes a wider ecosystem and is designed to fit into it, not replicate it. It does not replace exchange layers, workflow engines, wallets, public-service platforms, or domain registry systems. It gives them safer registry-facing services to call.
In plain terms
Categories matter when budgets are assigned and architecture diagrams are drawn. If you are mapping Registry Stack to a program line, start from what it does not do.
Neighbor systems
Each neighbor keeps what it owns. Registry Stack adds the narrow registry surface that was missing: described, scoped, evidence-shaped, and auditable.
OpenCRVS, OpenSPP, DHIS2, OpenIMIS
The neighbor owns
Storage, business rules, correction workflows, user interfaces, and a domain runtime API.
Registry Stack adds
Standards-shaped metadata, scoped read-only routes, configured evidence responses, and tamper-evident audit.
OpenFn, Camunda, Flowable
The neighbor owns
Process state, task assignment, timers, branching, retries, escalation, and history.
Registry Stack adds
A stable registry contract a workflow step can call without learning source tables, raw SQL, or full records.
X-Road, GovStack-style reference exchanges
The neighbor owns
Participant onboarding, message transport, mutual trust, routing, addressing, and cross-institution policy.
Registry Stack adds
The registry-facing surface behind the exchange: route-level scopes, field projection, and source access controls.
SD-JWT VC and OpenID4VCI-compatible wallets
The neighbor owns
Key management, credential storage, holder consent, and presentation to relying parties.
Registry Stack adds
The server-side issuance path: claim evaluation against registry data, and discoverable evidence offerings.
Citizen portals, casework systems, service catalogs
The neighbor owns
The user journey: forms, case queues, notifications, payments, and channels.
Registry Stack adds
The narrow registry-facing surface those journeys call: entity routes, evidence responses, and audit records.
MOSIP, eSignet
The neighbor owns
Identity enrollment, deduplication, authentication, e-KYC, and assurance levels for who a person is.
Registry Stack adds
The registry-facing side of that question: signed answers about what is true of that person in a specific registry (alive, eligible, registered), issued after the identity layer has done its job.
Demonstrated, not promised
The homepage names five platforms. This list states what exists today for each: four run in the hosted lab, where you can check them yourself, and one is in progress.
A layered example
An exchange layer such as X-Road handles network trust between institutions. The registry surface behind it assumes zero trust anyway: a request arriving through a trusted channel is still checked for route-level scope, field projection, and source access. The two layers do different jobs.
X-Road or a GovStack-style exchange handles trust, transport, routing, and addressing between participants.
The legacy database, extract, or domain platform stays where it is, under institutional control.
A request forwarded by the exchange layer arrives at a registry surface that can return a configured evidence response instead of a copied record, and log who asked and why.
Standards we adopt
Registry Stack adopts standards rather than inventing them. Claim levels vary by standard; the docs carry the full register before assuming conformance. No universal registry ontology is claimed.