Skip to content
You can now search across every topic, entity and event.What's new
Iran Conflict 2026
28APR

Commission awards sovereign cloud slot to Google joint venture

5 min read
09:13UTC

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.

← Back to Iran writes Phase 1; Washington still has no penJump to analysis ↓
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.

Sources:The Register·European Commission·Data Center Dynamics
Mentions:European Commission →S3NS →Proximus →Thales →Google Cloud →Post Telecom →CleverCloud →OVHcloud →STACKIT →Schwarz Group →Clarence →Mistral AI →Francisco Mingorance →CISPE →Microsoft →CLOUD Act →DG DIGIT →The Register →GAIA-X →Azure →Google →France →Germany →Prima Mente →Scaleway →
First Reported In

Update #3 · Sovereignty summit, minus the sovereigns

The Register· 23 Apr 2026
Read original →
Causes and effects
Caused by
EU awards first sovereign cloud deal
The naming of four provider groupings including S3NS directly advanced from the initial framework award in ID:2617; the S3NS inclusion and CISPE criticism emerged as the names became public.
Occurred 17 Apr 2026
Read story →
EC opens DMA cloud probes against AWS and Azure
The DMA cloud gatekeeper probes against AWS and Azure that prompted the US Section 301 response created the political context in which the Commission built a sovereign cloud framework including a US-linked provider.
Occurred 1 Oct 2025
Read story →
This Event
Commission awards sovereign cloud slot to Google joint venture
The first pan-EU institutional sovereign cloud contract now carries a US-anchored joint venture inside its reference provider set. Because member-state tenders will cite this framework as a procurement benchmark over the next six years, the Commission's definition of "sovereign" for a €180m pilot will shape considerably larger downstream contracts.
Led to
CISPE ships rival sovereign cloud badge
CISPE's sovereignty framework launched directly in response to its criticism of the S3NS SEAL-2 award as 'sovereignty washing', operationalising Mingorance's Making Sovereignty Verifiable keynote.
Occurred 24 Apr 2026
Read story →
Different Perspectives
Oil markets and Lloyd's of London
Oil markets and Lloyd's of London
Brent fell to $89.25 on ceasefire probability, not new barrels, with traders voting for Trump's deed over Tehran's denial. Lloyd's has not repriced Hormuz war-risk cover because its trigger requires a UN Security Council resolution or government certification, so tanker insurance costs remain elevated regardless of the spot move.
Pakistan and Qatar mediators
Pakistan and Qatar mediators
Pakistan's Mohsin Naqvi was in Tehran for his second visit in under a week, using the Pakistan-Qatar channel that delivered April's ceasefire after an identical public-denial cycle. The channel carries both civilian and military buy-in from Islamabad, the only configuration Iran's split command cannot dismiss as a partial signal.
India
India
India summoned the US Deputy Chief of Mission after three Indian sailors were killed aboard MT Settebello, the first formal grievance from a major non-belligerent directed at US enforcement. Indian seafarers supply roughly 12 per cent of the global maritime workforce; their presence on third-flag Gulf tankers is structurally inevitable regardless of bilateral diplomacy.
Islamic Revolutionary Guard Corps (IRGC)
Islamic Revolutionary Guard Corps (IRGC)
The IRGC declared Hormuz closed on 11 June while civilian negotiators were on the same mediation channel, then issued no public comment on the MoU framework. Its silence on the framework, rather than any foreign ministry statement, is the operative approval signal; the corps' unilateral Hormuz closure shows it did not treat the diplomatic track as binding on its operations.
Iran foreign ministry (Baghaei)
Iran foreign ministry (Baghaei)
Esmail Baghaei told IRNA that reports of a finalised deal were 'merely speculation' and that Iran had 'not yet made a final decision'. The denial is structurally identical to Iranian foreign ministry statements during the April ceasefire talks, which produced a binding text within 48 hours of the same language.
Trump administration / CENTCOM
Trump administration / CENTCOM
Trump cancelled the third strike day and called the MoU 'very strong' and almost ready to sign, while CENTCOM kept tanker enforcement running in the same 24-hour window. The administration is simultaneously withdrawing the military pressure it claims drove the deal and sustaining the enforcement campaign it is trying to trade away.