The state runs on AWS. The military uses Microsoft. Sovereignty has been outsourced.
Literal meaning: Sovereignty as a Service describes the condition in which a state’s exercise of sovereign functions — communications, tax collection, benefits administration, border control, defence logistics — is dependent on private technology infrastructure that the state does not own and cannot fully control.
Origin: The term adapts the cloud computing “as a service” model (Software as a Service, Infrastructure as a Service) to describe a political condition: sovereignty that is rented rather than owned. It describes a pattern documented across multiple governments that have outsourced critical administrative and intelligence functions to private vendors — most prominently Palantir, Microsoft, and Amazon — without retaining the capacity to perform those functions independently.
A condition in which state sovereignty is operationally dependent on private infrastructure — where the government cannot function without a vendor it cannot fire.
The Appeal: Outsourcing state functions to private technology providers offers real capabilities at lower cost than in-house development. The expertise, scale, and investment capacity of major technology companies genuinely exceeds what most governments can develop internally. The efficiency argument is real.
The Friction: Vendor Lock-in is the structural mechanism: once state functions are built on private infrastructure, exit costs are prohibitive. CLOUD Act is the legal dimension: US cloud providers must comply with US government data requests, meaning that states using US cloud infrastructure have in effect made their data subject to US jurisdiction. Technofeudalism is the broader category: Sovereignty as a Service is what feudal dependency looks like when the lords are technology companies and the serfs are governments. Muskism is the most acute form: a private individual with control over communications infrastructure, satellite internet, and space launch capacity who simultaneously advises government departments.
Why This Matters: Sovereignty as a Service names the political condition produced when efficiency arguments consistently win procurement decisions. Once you see the dependency accumulating, “the vendor has access to the data” is not a data security problem — it is a sovereignty problem.
Related terms: Vendor Lock-in · CLOUD Act · Technofeudalism · Muskism · Brussels Effect · Cybernetic Governance · Situated Knowledge
Read more:
- The Palantir Problem — Brayne, S. (2021). SSRN
- Crack-Up Capitalism — Slobodian, Q. (2023). Metropolitan Books