Why Digital Public Goods matter for national technology sovereignty

A government that adopts a proprietary platform for a core public service has made a decision that outlasts the contract that created it. Digital Public Goods exist to make that decision reversible.

"Technology sovereignty" gets used loosely, but the underlying concern is specific and legitimate: can a government change course — switch vendors, bring maintenance in-house, adapt the system to a new law or a new administration's priorities — without starting from zero? With a closed, proprietary system, often not. The code is not available to inspect or modify. The data formats are not open. The institution that built it is the only one who can change it, and every change goes through that institution's pricing and priorities.

What a Digital Public Good actually guarantees

Digital Public Goods Alliance certification is not a marketing label; it is a specific, independently verified set of requirements: open-source licensing, adherence to open standards, documentation sufficient for another team to actually maintain the system, and design that respects privacy and do-no-harm principles. OpenCHS, the case-management and helpline platform BITZ has built and maintained, holds this certification (DPGA GID0092407) — verified against the DPG Standard, not self-declared.

In practice, this changes what a government is actually buying. It is not just software; it is the right to keep, modify, and extend that software regardless of who built it originally. A ministry that adopts OpenCHS can, in principle, hand maintenance to a different technical team without renegotiating a license. That possibility — even if a government never exercises it — changes the negotiating position of everyone involved, including the original vendor.

Sovereignty is a design decision, not a procurement clause

It is tempting to think ownership is something you write into a contract after the fact. In practice, it has to be designed in from the start:

• Open standards for data exchange, so the system can talk to national registries and other platforms without a bespoke integration every time.
• Documentation written for a stranger, not just for the team that built the system — because eventually, someone else will have to maintain it.
• No proprietary dependencies buried in the stack that quietly reintroduce vendor lock-in even when the top-level license is open.
• A genuine handover plan, with capacity building built into the engagement rather than treated as a training afterthought in the final week.

This is also why we build OpenCHS on the principle that no single vendor — including BITZ — should become a point of lock-in. It is a constraint we put on our own work deliberately, because the alternative is building exactly the kind of dependency DPG status is meant to prevent.

Why this matters beyond any one platform

Africa's national digital infrastructure is being built right now, across dozens of services and countries, largely through vendor-funded or donor-funded platforms. The systems chosen today will be expensive and disruptive to replace for a decade or more. Digital Public Goods are one of the few mechanisms that let a government make that long-term bet without permanently ceding control of the outcome. That is the sovereignty argument, stripped of the buzzword: not that a government builds everything itself, but that it retains the right to.