Lexicon
Data sovereignty
Data sovereignty is about whose laws govern your data and who can compel access to it. How it differs from residency, and what real guarantees look like.
Definition
Data sovereignty is the question of whose laws govern your data and who can be compelled to grant access to it. It goes beyond data residency: residency asks where the bytes sit, sovereignty asks which jurisdictions and third parties have reach over them.
What it means in observability
The distinction became concrete when regulators and courts noticed that data stored in Europe by a foreign owned provider may still be reachable under that provider's home jurisdiction. For governments, regulated industries, and companies with hard contractual commitments, this is not abstract: it shapes which vendors are eligible at all. Observability raises the stakes quietly, since telemetry describes systems, users, and business activity in exactly the detail that makes jurisdiction over it matter. The sovereign cloud movement, and sovereign observability with it, is the market's response.
How it works in practice
Sovereignty is built from custody and control: who holds the storage account, who holds the encryption keys, who can access data operationally, and which legal entities sit in the chain between you and your bytes. Architectures where the platform runs inside your own cloud account move custody decisively to you. The vendor operates software, but the data, the keys, and the access controls live under your account and your jurisdiction's law, and audit trails plus scoped vendor permissions make the boundary inspectable rather than asserted.
Where it gets hard
Marketing outruns architecture here more than anywhere in the category. A regional logo on a datacenter does not settle whose subpoena reaches the data, and sovereignty claims deserve the boring questions: who owns the account, who holds the keys, what can vendor staff see, and under which law does each party sit. Conflicts of law are real and unresolved in places, so the practical goal is minimizing exposure, keeping data and custody where your obligations are, rather than waiting for treaties to tidy up.
Where Tsuga fits
Tsuga's BYOC architecture makes sovereignty structural: telemetry lives in your cloud account, under your keys and access controls, in your jurisdiction. The vendor operates the software without taking custody of the data.
Related terms
- BYOCBYOC, Bring Your Own Cloud, is a deployment model where a vendor's software runs inside the customer's own cloud account, operated by the vendor but living on infrastructure the customer owns.
- Data residencyData residency is the question of where data physically lives: which country or region stores it, and where it is processed along the way.
- ObservabilityObservability is the ability to understand what is happening inside a system from the data it emits: its logs, metrics, and traces.
- Vendor lock-inVendor lock-in is the accumulation of switching costs that makes leaving a platform impractical regardless of how the relationship is going: proprietary instrumentation, captive data, workflows that exist in only one tool, and contracts priced to reward staying.