Sovereignty is not a server location

The comforting half-truth

In-region hosting is necessary and reassuring, but it addresses where data rests, not who governs how it is used. If every decision is still made by a foreign model under foreign terms, the sovereignty is cosmetic.

Buyers should look past the data-centre map to the control plane.

What real control requires

You control the model and its updates, you hold the keys, and the decision logic runs under your governance. When those are true, location becomes one honest detail among several rather than a stand-in for the whole claim.

How to test the claim

Ask whether you could keep operating, and keep making the same decisions, if the vendor disappeared tomorrow. If the answer is no, the sovereignty was never yours.

The question that cuts through

One question separates real sovereignty from the cosmetic kind: if the vendor disappeared tomorrow, could you keep operating and keep making the same decisions? If the answer is no, then whatever the data-centre map shows, the sovereignty was never yours.

Asking it early, before a contract, saves the far more painful discovery of the answer during an incident, when the cost of a dependency you did not know you had is at its highest.