What is Sovereign deployment?
Running the system where the data is legally required to stay. A constraint set by a regulator or a board, not an engineer.
Three shapes cover almost every requirement: on-premises, a sovereign cloud region, or the client's own cloud tenancy. Which one applies is usually decided by a regulator or a board rather than by an engineer, and the practical question is not whether it is possible but what it costs in capability.
One delivered system was built where nothing could leave the building at all, and that constraint shaped the whole architecture rather than being a deployment option chosen at the end.
| On this | Sovereign deployment | A regional cloud region |
|---|---|---|
| Who controls the keys | You, in the on-premises and own-tenancy shapes | The provider, under their jurisdiction |
| What it costs you | Some model choice, and you own the operating burden | Less operationally, more in what a regulator will accept |
| When it has to be decided | Before the architecture, because it constrains it | Often treated as a deployment detail, which is the mistake |
- When it is the right answer
- State the requirement in the first conversation. It is cheap to design for and expensive to retrofit.
Start here
If a term here is the one your board paper turns on, ask us about it.
We will send the entry, the evidence behind it, and the note about where it does not apply.
You get a reply within one working day, from the engineer who would do the work.