Business Mission Control · Episode 7
What Does A Sovereign Cloud Offer Actually Buy You?
Sovereign is on every cloud offer now, and the label does not say which of three things you buy.
Estera Kot and Sebastian Selman break down what a sovereign cloud offer actually buys, in francs and in failure modes.
We cover:
- Legal control, operational control and exit cost, with a test for each
- The Swiss Government Cloud plan: 68% on foreign hyperscalers by 2032
- Why renting is fine and renaming it sovereign is not
- A three-question test for any sovereign offer
Chapters
- 00:00Intro: a breach mid sovereignty debate
- 00:56One word, three things
- 02:58Legal control: the subpoena test
- 03:27Operational control: the 2 a.m. test
- 03:42Exit cost: the gravity test
- 03:59Scoring a hyperscaler sovereign region
- 04:52The 68% ledger of the Swiss Government Cloud
- 05:40Renting is fine, renaming it is not
- 06:05Pricing sovereignty like insurance
- 07:40Full chain, per workload: the Infomaniak line
- 08:41Apertus and what real sovereignty costs
- 09:06Per workload: patient records vs marketing site
- 10:50The three-question test: whose law
- 11:35Question 2: who holds the patch
- 12:00Question 3: what leaving costs
- 12:24What a good answer sounds like
- 13:17The middle-tier debate on sovereign regions
- 14:13Mission debrief
Sources
- Federal Administration notice on the SharePoint attack (about 200 accounts, detected Jul 28, 2026): admin.ch/de/newnsb/1CjmpBBHQaMV82PjKEpcL
- Inside IT on the SharePoint attack: inside-it.ch/bundesamt-fuer-informatik-sperrt-server-zugr…
- Netzwoche on the SharePoint attack: netzwoche.ch/news/2026-08-05/cyberangriff-auf-sharepoint…
- EFK (Swiss Federal Audit Office), Swiss Government Cloud audit (economic benefit not yet demonstrated): efk.admin.ch/en/audit/swiss-government-cloud-key-project…
- Netzwoche, EFK review and the 68% projection: netzwoche.ch/news/2025-12-08/efk-nimmt-swiss-government-c…
- BIT, Swiss Government Cloud programme: bit.admin.ch/en/sgc-en
- Netzwoche, Thomas Jacobsen (Infomaniak) on sovereignty: netzwoche.ch/news/2026-06-10/die-schweiz-hat-einen-trumpf
- Microsoft and ELCA, sovereign cloud options in Switzerland (Azure Local, Microsoft 365 Local): news.microsoft.com/source/emea/2026/06/elca-collaborates…
- Netzwoche, open source as the middle way: netzwoche.ch/news/2026-07-30/digitale-souveraenitaet-mit…
- ICTjournal, Geneva digital sovereignty strategy: ictjournal.ch/news/2026-07-08/geneve-se-dote-dune-strateg…
- ICTjournal, Swiss Center for Digital Sovereignty (31 partners): ictjournal.ch/news/2026-04-29/lancement-officiel-du-centr…
- ETH Zurich, Apertus launch: ethz.ch/en/news-and-events/eth-news/news/2025/09/press-re…
- swissinfo, Apertus one year on (4M+ downloads): swissinfo.ch/eng/swiss-ai/one-year-on-has-swiss-ai-model…
- Inside IT, CSCS power consumption (Alps, 10 MW at full load): inside-it.ch/so-viel-strom-verbraucht-das-supercomputing…
Further reading:
- Geneva's digital sovereignty strategy, the document itself: ge.ch/document/strategie-souverainete-numerique-etat-geneve
- ICTjournal, Jan Kerschgens named co-director of the Swiss Center for Digital Sovereignty: ictjournal.ch/news/2026-08-10/jan-kerschgens-nomme-codire…
Notes
- Clouds on Mars is a Microsoft Fabric Featured Partner. This episode was not commissioned or sponsored by Microsoft.
Transcript
This transcript is provisional. It was made from YouTube's automatic captions and will be replaced by the editor's corrected version.
Transcript of the published episode, lightly edited for readability. Timestamps match the video.
Business Mission Control, Mission 007. Systems check.
All consoles go. And today we check whose consoles they are.
So here's a timeline. This July, Switzerland was mid-debate about digital sovereignty. Geneva published a cantonal sovereignty strategy. A national center for digital sovereignty was staffing up. And in the same weeks, the federal government got breached through its SharePoint servers. Around 200 accounts compromised, internet access to the servers cut.
The country got hacked through the exact dependency it was holding a conference about. And a canton reported a similar incident one day later.
So everyone will now say the answer is sovereignty. Buy sovereign.
Except nobody selling sovereign will tell you what the word means. And a word that means everything prices at whatever the vendor wants.
Today's mission, for the record.
Define what sovereignty actually buys, in francs and in failure modes. And bring back a three-question test you can run on any sovereign offer that lands on your desk.
I am Sebastian. And if the word sovereign appears anywhere in your current RFP, this transmission is for you. So let's start with the market, because sovereign is on everything now. Integrators sell sovereign Microsoft clouds. Open source gets pitched as the sovereign middle way. Every canton wants a strategy.
Yeah. And as an architect, I have a problem, because those offers cover three different things, and the label does not say it. So thing one is legal control: whose law can reach your data, whose courts, and whose subpoenas. Thing two, operational control: who can actually run the system when the vendor is breached, sanctioned or gone. Thing number three, exit cost: what leaving takes, in francs and months.
Okay. So you mentioned three things: the legal control, the operational control and the exit cost. Can you make each of them concrete, because in an RFP they might blur.
Oh, very true. So legal control is the subpoena test. A foreign parent company can be compelled by its home jurisdiction, regardless of where the data center stands. Swiss soil does not stop a foreign statute reaching a foreign company. It means "your data stays in Switzerland" answers a real-estate question, not a jurisdiction question. Operational control is the two-in-the-morning test. So who rotates the keys? Who reads the logs in depth? Who can patch without a ticket to another continent, or another country? And exit cost is the gravity test. Here: data egress, rebuilt integrations, retrained people. All three are measurable. Almost no offer measures them for you. Now let's score a sovereign region from a hyperscaler against that. It buys you thing one, partially: Swiss jurisdiction, with caveats that live in the fine print. It buys you almost none of thing two. The people who can operate the platform at depth are the vendor's people, on the vendor's escalation chain.
Which the July breach made concrete. When the SharePoint vulnerabilities hit, the Bund did not patch its way out on its own schedule. It waited, like every other customer on the planet, for the vendor.
Yeah. And this is the honest definition of a dependency. Not who hosts your data, but who you wait for when it burns. And now the ledger nobody reads aloud. The federal audit office looked at the planned Swiss Government Cloud and projected it would run roughly 68% on foreign hyperscalers by 2032, and said the economic benefit was unproven.
And I will defend that, because, I mean, the alternative is worse. Switzerland is not going to rebuild a hyperscaler. The talent does not exist here at that scale. The capex does not exist, and the services gap would cost more than the dependency does. So renting the best infrastructure on the market is not a weakness. It's arithmetic.
Yeah, renting is fine. I rent. Clouds on Mars builds on rented infrastructure every day, and I will say that on any stage. What is not fine is renting and calling it sovereign. This mislabel is the problem, because it makes the board believe a risk is closed when it's merely rebranded.
Okay, so we agree on the split. Pragmatism, yes. But imprecise vocabulary, no.
Yeah.
But then price the vocabulary for me. If honest labels existed, what would the sovereign premium be worth paying?
Price it like insurance, because this is what it is. You pay a premium against a failure mode. For a marketing site, the failure mode of foreign jurisdiction is an inconvenience, premium worth roughly zero. For court records, the health data, for the systems a canton governs with, the failure mode is existential, and the premium is worth real money. And the ledger problem with the Government Cloud is not the 68%. It's that nobody published which workloads sit in the protected 32, and why. The percentage is the headline, but the allocation is the strategy.
And the audit office said exactly that, in its own language: benefit unproven. Not wrong. Unproven.
And a dependency you name honestly is a decision. A dependency you rename is a surprise with a delivery date.
Yeah. I think the sharpest counter-voice in the Swiss market right now comes from Infomaniak. Thomas Jacobsen's line: digital sovereignty is no longer theoretical but a concrete operational risk. And their definition is maximalist. Real sovereignty means controlling the whole chain: headquarters, voting rights, infrastructure, staff, reversibility.
On the definition, Jacobsen is right. That is what the word means. Full-chain control. Anything less is partial sovereignty and should be sold as such.
But.
But the conclusion does not follow that everyone should buy the full chain, meaning that full-chain control is expensive, and most workloads do not earn it. Switzerland built Apertus, a sovereign language model, on national supercomputing power. And this is what real sovereignty costs: years, institutions and the power bill. Worth it for the workloads that are existential, and absurd for your marketing websites.
So sovereignty is not a tier you buy. It's a decision you make per workload. Walk one example through Jacobsen's five links, so listeners can copy the move.
Yeah. Take patient records versus the hospital's marketing site. Same organization, opposite answers. Headquarters and voting rights: for the records, you want the operator to answer to Swiss law first, because this is who the court will actually reach. For the website, it's irrelevant. Infrastructure and staff: the records need people with Swiss clearance who can act without a foreign escalation chain. The two-in-the-morning test again. The website needs, for example, a CDN, very lovely ones. And reversibility: the records need a tested exit, rehearsed like a fire drill, because you will only ever need it on the worst day of your tenure. The website needs a backup.
Okay. So full chain for one workload, probably one workload in 50, and rented convenience for the other 49.
Per workload, I would say, with open eyes. The scandal is not that Switzerland rents cloud. The scandal would be not knowing which workloads must never be rented.
So, the test then. An offer lands on my desk. The word sovereign is in the title. Three questions.
Okay. Question one would be legal. Whose law can reach this data, and who enforces the answer? Not the marketing page, but the contract. If a foreign statute can compel disclosure, you have partial legal control, and the offer should be priced accordingly.
So most buyers would stop there, right? That is the whole sovereignty conversation in most RFPs I see.
Yeah. Which is why breaches keep surprising people. Question two: operational, and July wrote it for us. When this system is compromised, who holds the patch? Who holds the logs? And on whose clock do we recover? If the answer to all three is the vendor, you are a spectator with a contract. The Bund spent early August finding that out in public.
And question three is the one that finance will love.
Exit. What does leaving cost, in francs and in months, measured now and not in the crisis? Reversibility is the only sovereignty you can bank. If you cannot state your exit cost, your exit cost is whatever the vendor decides on the day you need it.
And what does a good answer sound like, so the listener recognizes one? Because every vendor will claim all three questions are covered.
A good answer is specific and dated. On legal: a contract clause naming the governing law and what happens on a foreign disclosure order, not a compliance badge. On operational: named roles on your side with real privileges, who holds keys, who reads the logs, and an incident drill you have actually run. On exit: a number, in francs, refreshed on a cadence, yearly, with the last export test dated. If any answer is an adjective instead of a noun, then score it zero and move on.
One thing we might read differently, and it goes to the audience. I think the sovereign-region offers from hyperscalers are a legitimate middle tier: partial sovereignty, honestly useful for most regulated workloads. Estera, do you think the naming does more damage than the tier does good?
So, a middle tier sold with a precise label, I would endorse tomorrow. Sold as sovereign, full stop, it teaches boards to stop asking the three questions, and this is the damage.
So, YouTube comments: is a sovereign hyperscaler region real sovereignty, useful middle ground, or a contradiction in terms? Best argument gets read in the next mission briefing.
Yeah, time for the mission debrief.
Yep. The mission was: define what sovereignty buys, and bring back the test. The definition: legal control, operational control, exit cost. Three different purchases, one misused word. The test: whose law, who recovers, and what does leaving cost.
And run it per workload, not per vendor. Show notes carry every source, including the breach coverage and the EFK numbers. The middle-tier question is live in the comments. You can follow us on Spotify or Apple Podcasts; that will bring you the next transmission.
Next mission: the cost floor. Why your data platform bill is rising, even if you bought nothing new.
And this is Business Mission Control, somewhere between the flag and the fine print. Keep your trajectory honest.
Signing off.
Signing off.