Few terms in public sector technology are used as loosely as sovereign cloud. It is applied to a national data centre, a hyperscaler region with a local billing address, a private tenancy, and occasionally to a contract clause that says nothing enforceable at all.
For a ministry deciding where citizen records live, the distinction matters. Sovereignty is not a location on a map. It is a set of answers to questions that must survive scrutiny from an auditor, a regulator and a parliamentary committee.
The four questions that define sovereignty
Where does the data reside, and does it stay there? Not just at rest in a primary region, but in backups, replicas, disaster recovery copies, logs, support bundles and the metadata that describes them. A sovereign arrangement that forgets recovery copies is a partial arrangement.
Who can access it? Named individuals, not job titles. Which provider personnel, under which jurisdiction, with which approval path, and what record exists afterwards. Support models that grant remote administrative access across borders are the most common sovereignty gap in public sector cloud.
Who holds the encryption keys? If the provider holds the keys, the provider can be compelled to disclose. Key custody — including who can revoke access and what happens when a key is lost — is the difference between control and a promise.
What evidence exists that controls were applied? Policies are not evidence. Access reviews, change records, restore tests, incident logs and configuration baselines are. A sovereign operating model produces them continuously rather than assembling them for an audit.
Sovereignty is not a statement about intent. It is the ability to prove, after the fact, who did what and where the data was.
Sovereignty is a spectrum, not a binary
Governments rarely need the same position across every system. A practical arrangement classifies workloads, then places each against its obligation:
- In-country infrastructure for registers, identity systems and citizen records where the law requires storage inside national borders.
- Sovereign regions operated by a provider under the national legal framework, suitable where the obligation is about jurisdiction and access rather than physical location.
- Hybrid arrangements keeping sensitive systems in-country while non-sensitive analytics run on commercial cloud.
- National or community cloud for shared services across agencies, reducing duplicated cost.
The classification exercise is where most programmes either succeed or create years of remediation. It is a legal, security and operational decision made together, not a platform choice made by a technology team alone.
What procurement should test
A sovereign cloud proposal is only as strong as the answers it puts in writing. Six questions expose most of the weakness in a bid:
- Can you name every location where our data, logs and backups may exist? Including sub-processors and support tooling.
- Which personnel can access our environment without our approval, and under which legal jurisdiction?
- Who holds the encryption keys, and can you demonstrate that you cannot access data without them?
- What happens if you receive a disclosure request that conflicts with our law?
- What is the exit path, in what format, and how long would it take?
- Which audit artefacts will we receive, how often, and in what form?
An answer of "we comply with all applicable laws" is not an answer to any of them.
The operating model is the hard part
Most sovereign cloud discussions end at architecture. The recurring failures happen afterwards: patch windows nobody owns, access reviews skipped, recovery never tested, a change made by a contractor that no one recorded.
Sovereign managed operations therefore need three things beyond infrastructure:
- Documented procedures agreed with the institution, including change control, incident response and maintenance windows around service hours.
- Local accountability — named engineers, in the institution's time zone, with an escalation path that answers out of hours.
- Standing evidence — monthly reporting on availability, security patching, access changes and recovery testing, produced as a matter of routine.
A realistic starting point
Institutions do not need a national cloud programme to make progress. The first step is a sovereignty assessment: inventory what holds citizen data, classify it against the obligations that apply, identify where the current arrangement cannot be evidenced, and sequence remediation by risk.
That assessment usually produces a small number of high-value moves — an in-country backup copy, a key custody change, a documented access path — long before any platform migration is required. Sovereignty improves in steps, and the first steps are often contractual and operational rather than technical.
Addicnet operates sovereign cloud environments for public sector institutions across Africa, delivered with in-country and sovereign-region infrastructure partners and governed by a single managed agreement.