How we build

Open standards. Sovereign by design. Operated, not just sold.

The principles every Dzinza product shares — the reason a government can adopt our infrastructure as a national utility rather than a vendor's lock-in.

Open standard

Published contracts (Apache-2.0) any vendor can build against — no private agreement, no lock-in. The spec is the agreement.

Sovereign by design

The State owns the data and the mandate as controller. Dzinza operates as a processor, with escrow, export-on-exit and a standing right-to-in-house.

Vendor-neutral

Competitors integrate on identical terms through the same public API. Even our own FuroTrack is just a client, never privileged.

Publicly verifiable

Anyone can verify a certificate with no login — the trust anchor that makes a national record impossible to fake or quietly alter.

Built in & for Africa

A SADC-based team building for African veterinary authorities, producers and export markets first — not a port of someone else's system.

Operated, not just sold

We run the platform under a concession — uptime, data residency, in-region operations — and hand stewardship to the State on designation.

FuroTrackherd appAbattoirintakeAuctionsaleyardINDUSTRY · ANY VENDORNationalRegistry*.gov.zwidentity · movementhealth · certificatesSTATE-OWNEDVerifyANYONE · NO LOGIN
The sovereignty model

The State holds the data and the mandate. We hold the implementation.

Sovereignty isn't a slogan in our contracts — it's the operating model. The registry is the single source of truth, owned by the State; Dzinza runs it as a processor under a concession with explicit exits.

  • State = data controller. Dzinza = processor. The herd data is never a vendor asset.
  • Source-available implementation + escrow — auditable, with no hidden behaviour.
  • Export-on-exit and right-to-in-house: the nation can always take it over.
How a national instance is delivered

From standard to sovereign system — and then handed over.

Each rollout follows the same path, so a government always knows what it is adopting and how it can take control.

01

Standardise

Ratify the open contract and the national profile — acronym, ID scheme, veterinary zones — with the authority.

02

Build

Stand up the sovereign registry on the government domain, integrate the first vendors against the open API.

03

Operate

Run it to an SLA — uptime, residency, support — while industry adopts it and the record fills with real data.

04

Hand over

Transfer stewardship of the standard to the State or a neutral national body on official designation.

Adopt infrastructure you can own.

See how the open standard, the sovereign model and the conformance mark fit together in our flagship.