Each nation's registry is its own — on its own domain
Every tenant is white-labelled as a sovereign national system. The platform gives each a default subdomain; the State maps its own government domain on top — that is the public, production face.
Platform default and sovereign public face
| Platform subdomain | Government domain | Instance |
|---|---|---|
zlits.lits.africa | zlits.gov.<cc> | ZLITS (example) |
mlits.lits.africa | mlits.gov.<cc> | MLITS (example) |
my.zlits.lits.africa | my.zlits.gov.<cc> | Keeper self-service |
Owned by the State
The government owns the mandate and the national herd data. Dzinza operates the platform — with full data export and in-house handover available at any time.
Residency you choose
Pooled, dedicated, in-country silo, or fully State self-hosted / air-gapped — selected per nation, with in-region operations for sovereign data.
Traceable across borders
Sovereign registries federate over the open contract — exchanging signed attestations for cross-border movement and export, never sharing storage.
The residency rungs
A nation chooses how much isolation it needs — and can move up the rungs over time.
- Pool
- Shared multi-tenant platform with strict per-tenant isolation. Fastest to launch.
- Dedicated
- A dedicated database and runtime for the nation, still operated by the platform.
- In-country silo
- Hosting inside the nation's borders for data-residency requirements.
- State self-host
- The government runs the software itself — up to fully air-gapped. The standard is the same.
Data protection and exit
- The government owns the data. Personal and herd data are held under the nation's data-protection law, with the government as the data owner.
- Your data, exportable. The full dataset can be exported in the open format at any time — there is no hostage data.
- Take it in-house any time. The State can run the software itself or move operators without losing the registry.
- An open standard. The contract is public, so a nation is never locked to one operator — see the standard.