Skip to content
Briefings are running a touch slower this week while we rebuild the foundations.See roadmap
Iran Conflict 2026
4JUN

Commission awards sovereign cloud slot to Google joint venture

5 min read
11:25UTC

The European Commission's €180m six-year sovereign cloud framework, named between 17 and 20 April, handed one of four provider slots to S3NS, a Thales-Google joint venture that cleared only the minimum SEAL-2 threshold.

ConflictDeveloping
Key takeaway

A sovereignty framework that treats SEAL-2 and SEAL-3 as interchangeable has collapsed its own distinction.

Between 17 and 20 April 2026 the European Commission named the four provider groupings selected for its €180m, six-year sovereign cloud framework . Post Telecom leads a Luxembourg consortium with CleverCloud and OVHcloud at SEAL-3; STACKIT, owned by the Schwarz Group, represents Germany at SEAL-3; Scaleway represents France at SEAL-3; and Proximus leads a Belgian consortium that includes S3NS, Clarence and Mistral AI, with S3NS rated at SEAL-2. the Commission's Sovereignty European Assurance Level framework grades contracts from SEAL-1 to SEAL-3, and SEAL-3 requires the operator to run the service without foreign technical dependencies. SEAL-2 requires only data-sovereignty minima. Three awardees cleared the higher bar; one did not.

CISPE's Francisco Mingorance told The Register the award was "clearly an own goal" and called the S3NS inclusion "sovereignty washing" . The objection is specific: S3NS is a joint venture between French defence group Thales and Google Cloud, and workloads running on Google infrastructure sit within reach of the US CLOUD Act, the 2018 law that lets American authorities compel disclosure of cloud data held anywhere in the world. Microsoft told the French Senate last year that it could not guarantee French customer data would never be disclosed under US legal orders; the same exposure attaches structurally to any Google-hosted workload regardless of where the data physically sits.

EU-native providers hold roughly 15 per cent of the European cloud market against around 70 per cent for the three US hyperscalers combined , and the Commission's counter-case rests on that arithmetic. Excluding every provider with any US linkage would have narrowed the tender to a field too small to be competitive, and the sovereign cloud market is forecast to triple to $23bn by 2027; a procurement logic that restricts the supplier base risks producing either no viable bidder or a single one. Hedged inclusion of S3NS at SEAL-2, alongside three SEAL-3 awardees, reads on that defence as a deliberate widening of the competitive field rather than a concession on sovereignty.

A €180m framework becomes the citation benchmark for every national cloud tender that follows, and member-state procurement Teams tend to cite the Commission's own designation as prima facie evidence of sovereignty compliance. Over six years the downstream contracts will be valued well above €180m, and a SEAL-2 provider sitting inside the same slot as a SEAL-3 one collapses two categories the framework was designed to separate. CISPE has the foundation for a legal challenge; Mingorance's keynote in Brussels this week on "Making Sovereignty Verifiable" suggests the challenge will come through an auditability argument rather than a tender-rules one.

Deep Analysis

In plain English

The EU runs its own computer systems on rented cloud infrastructure. This contract decides which companies can bid to provide that infrastructure for the next six years, with rules about how 'European' those providers must be. The controversy is that one of the four winners, S3NS, is a joint venture between French defence company Thales and Google. Critics say that because Google is an American company, EU data running on S3NS infrastructure could legally be accessed by US courts under a 2018 US law called the CLOUD Act. The Commission's response is that S3NS met the minimum sovereignty standard, and excluding it would have left too few suppliers in the competition.

Deep Analysis
Root Causes

Three structural factors make hyperscaler dependency difficult to escape. The managed services gap is the first: EU-native providers can match hyperscalers on raw compute and storage pricing but cannot yet replicate the depth of managed database, machine learning, networking and observability services that enterprise workloads depend on.

Migrating from Azure to OVHcloud or Scaleway requires rebuilding application dependencies against a shallower service catalogue, and the engineering cost is a real barrier for large organisations.

Network effects in procurement compound the problem: once a ministry or large enterprise runs on a hyperscaler, its staff develop platform-specific skills, its vendors integrate through that platform's APIs, and switching costs compound over time. Third, hyperscalers can cross-subsidise European market share from US revenue bases at a scale no European provider can match.

What could happen next?
  • Meaning

    The first consequence is precedential: member-state procurement agencies will cite the Commission's own SEAL-2 award as justification for purchasing from S3NS and structurally similar Thales-Microsoft or Thales-Amazon joint ventures. If those downstream contracts follow, the practical effect of the EU's sovereign cloud framework over six years will be to channel public money toward hybrid US-European structures rather than toward EU-native providers. The second consequence is political: CISPE's public challenge delegitimises the framework before it has generated a single call-off contract. If the Commission does not respond with a published SEAL audit methodology, the 'sovereignty washing' framing will become the dominant description of the award in procurement guidance discussions across Europe.

First Reported In

Update #3 · Sovereignty summit, minus the sovereigns

The Register· 23 Apr 2026
Read original
Different Perspectives
China
China
Beijing's MOFCOM Blocking Rules constrain OFAC enforcement on the mainland; China has not corroborated Trump's verbal account of any bilateral summit, and the rial's failure to hold its Rubio bounce, combined with the IRGC's stablecoin rail closure, increases Chinese yuan-denominated oil-payment exposure through Hormuz.
Israel
Israel
IDF Chief Zamir said on 3 June there is no ceasefire for his forces even as Israel signed the Washington Lebanon framework requiring Hezbollah withdrawal south of the Litani; a UNIFIL peacekeeper was killed by mortar near Marjayoun on the same day, exposing the gap between the diplomatic framework and a ground advance that has not stopped.
Bahrain
Bahrain
The IRGC struck Bahrain on 3 June as its sirens sounded and its PAC-3 magazine neared exhaustion; excluded from Rubio's 2 May emergency resupply, Bahrain received a 50-round Federal Register notice on 1 June on an 18-month delivery timeline, meaning it is defending the US Fifth Fleet headquarters on the last rounds it has.
Qatar
Qatar
Qatar offered $6bn under OFAC Licence L-2 restrictions and sent Ghalibaf's delegation home empty-handed; the $6bn ceiling is a legal constraint, not a negotiating floor, and Rubio's no-sanctions-relief testimony means Qatar cannot revise it without White House action that has not been requested.
Kuwait
Kuwait
Kuwait expelled two Iranian diplomats within 24 hours of the airport strike, the strongest and fastest Kuwaiti diplomatic move of the conflict, while keeping the full mission in place to preserve a communication channel; it has now invoked Article 51 self-defence, filed a formal protest, and expelled diplomats, exhausting its formal toolkit short of full rupture.
United States
United States
Trump narrated a weekend deal while the channel Rubio described under oath, Khamenei's written-only couriers with a 3-to-5-day lag, cannot answer at that speed; CENTCOM called the airport strike deliberate, calculated and unjustified. The House 215-208 vote gave Congress its first on-record war-powers position against the deployment Trump has run without a signed instrument for 96 days.