Token-OPEX: Inference Controls, Not the Seat Budget
Angelika Beierlein
9 Min. read time Token costs aren’t a line item in SaaS contracts. They’re variable OPEX per workflow-and ...
More and more CIOs in Western Europe want to expand their local cloud usage. At first glance, this seems like a clear direction. But in the investment round, it becomes an uncomfortable question: What exactly is a company paying for when it pays for sovereignty? And what risks does this premium actually insure against? Microsoft, AWS, and StackIT all use the same buzzword, yet they mean very different things.
Key Takeaways
Related:Cloud and AI Development Act: Sovereignty Becomes a Tender Requirement / VMware Under Broadcom: The Exit Plan as a Lever
Sovereignty is plastered across almost every sales brochure these days. For an investment decision, that’s a problem because the word describes a spectrum, not a fixed state. At one end sits the data boundary, where data and processing stay inside the EU. Microsoft has declared its EU Data Boundary “complete” by early 2025, operated through European legal entities, yet the U.S. parent company remains outside that boundary. At the other extreme is a platform that is legally, operationally, and technically severed from any U.S. corporation.
In between lies the expensive part. AWS is building its European Sovereign Cloud with an announced investment of €7.8 billion; the first region will go live in Brandenburg. StackIT, an arm of the Schwarz Group, positions itself without any U.S. business at all, while T-Systems operates entirely on German soil. Each option solves a slice of the puzzle. None solves all of it.
An investment committee tallies line items, not worldviews. For vendor selection, four variables can be cleanly weighed against one another.
A single example makes the gap tangible. Delos Cloud, a German offering for the public sector, operates its platform on Microsoft Azure technology. That is understandable and pragmatic. It also shows that the “sovereign” label does not automatically dissolve technical dependency.
Sovereignty that runs on the very technology it is meant to free you from remains a negotiating position.
For the investment appraisal this means digging one layer deeper. Who operates the hardware? Whose software runs on it? Who holds the keys in a crisis? StackIT has drawn a clear line for precisely this reason and, by its own account, deliberately avoids U.S. investments to credibly maintain distance from the CLOUD Act. Whether a company needs this level of stringency is a business decision, one that should be made deliberately, not casually via a vendor data sheet.
The counter-calculation is sobering. Waiting for the sovereign option forgoes the fastest AI services and the largest provider ecosystem. In the race for AI products, that forfeiture can cost more than any compliance risk. The argument collapses only when a business runs on data whose leakage would be existential. For most applications the cooler question is which data are actually affected. IT Budget 2026: The End of the 70/30 Rule illustrates how narrow this margin has become.
Before vendor selection comes data classification. Which data sets would truly pose a problem under foreign access, and which would not. This list is uncomfortable because it must be brutally honest. Yet it is the only foundation on which a surcharge can be justified. Only then does vendor comparison pay off. Only then can the investment be weighed against actual protection needs rather than gut feeling. Keeping an eye on the cost side? In The Billion-Euro Bet of the Hyperscalers, and Your Cloud Bill you’ll find the counter-calculation to the sovereignty premium.
An EU region stores data in Europe but is operated by a global provider. A sovereign cloud goes further by placing operations, personnel, and legal control under European sovereignty to prevent access by foreign authorities.
Generally, yes. Separate operations, dedicated personnel, and reduced economies of scale drive up costs. The premium should be clearly disclosed and weighed against specific compliance benefits.
Key players include Microsoft with its EU Data Boundary, AWS with the European Sovereign Cloud, T-Systems, StackIT (part of the Schwarz Group), and Delos Cloud for the public sector. Their offerings vary significantly in terms of sovereignty.
Not necessarily. Some platforms may still tie you to a new provider or rely technically on a hyperscaler stack. Portability should be evaluated just as rigorously as with any other cloud decision.
With data classification. Only once you know which data truly requires protection can you determine whether, and to what extent, a sovereign offering justifies the added cost.
Read more on Digital Chiefs
Digital ChiefsIT Budget 2026: The End of the 70/30 RuleDigital ChiefsThe AI writes the code. Who is liable for it?Digital ChiefsVMware under Broadcom: The Exit Plan as a LeverMore from the MBF Media Network
Succession Without a Successor: Making the Business Transition Fit
Image source: AI-generated (June 2026)