How it fits
Registry Stack is not a replacement for registry software, exchange networks, identity systems, or catalogs. It runs next to the registry and applies the registry owner’s rules when another service requests an answer or selected data.
Existing systems and standards
Some connections are implemented and demonstrated today. Others describe where Registry Stack can sit but still require integration work. Each entry states the current level of support.
Works alongside
OpenCRVS, OpenSPP, DHIS2, and custom systems
The existing system keeps its records, write workflows, and user interface. Registry Stack adds a read-only interface for agreed questions or fields. The hosted lab demonstrates connections to OpenCRVS and DHIS2, but that is not a promise of automatic integration with every version or deployment.
Connects to supported sources
CSV, XLSX, and selected PostgreSQL tables
Registry Relay can place a protected, read-only API over these sources. The registry owner still maintains the source and decides which fields a public or partner service may read.
Connects after Registry Stack
X-Road, WSO2, and OpenFn
Registry Stack is deployed next to the source registry, before any exchange layer. It applies the registry owner’s rules first. An exchange layer can then transport requests and responses between institutions. Registry Stack does not replace that layer, and no X-Road, WSO2, or OpenFn integration is shipped today.
Relies on an identity provider
MOSIP eSignet and other identity providers
Identity systems establish who a person or service is. Registry Stack uses that identity when checking a request; it does not enroll people, issue national identifiers, or replace identity and access management. An eSignet-backed flow is demonstrated in the lab.
Returns one assertion in two encodings
Signed JWS and SD-JWT VC
Evidence Gateway returns a stateless signed assertion. Signed JWS is the default; SD-JWT VC is an optional serialization of the same assertion. It does not add a credential lifecycle, wallet flow, or presentation service.
Publishes supported formats
DCAT, BRegDCAT-AP, CPSV-AP, JSON Schema, and OpenAPI
Registry Manifest and Registry Relay can publish machine-readable descriptions in these formats. Support and conformance evidence differ by standard, so Registry Stack does not make one blanket statement of standards conformance.
Follows the same broad evidence journey
Discover evidence, request it from an authority, return it to a service
Registry Stack describes available evidence and handles defined requests between authorities and services. An EU OOTS deployment would add its network, eDelivery, AS4 transport, and conformance requirements through the surrounding integration layer.
A direct service request
The components below are ordered from the source registry outward. A request travels inward in the opposite direction, and the response returns through the same components.
Stores the source records. The registry owner remains responsible for updates and corrections.
Runs next to the registry, checks each request, reads the source, returns the agreed answer or fields, and records the event.
Transports requests and responses between institutions after Registry Stack has applied the registry owner’s rules.
Sends the permitted request and uses the answer or selected fields it receives.
Evidence Gateway returns one signed fact. Registry Relay returns protected, selected data. Evidence Gateway may use a Relay-protected API as one fixed source, but each product keeps its own authorization and configuration boundary.
Technical details