Europe’s cloud problem is simple in one sentence: the continent needs a credible, large-scale cloud supplier that can match hyperscaler scale while answering Europe’s specific demands for data sovereignty, regulatory compliance, and strategic resilience—and the gap between aspirations and reality is now a policy crisis as well as a market opportunity.
For years European policymakers, enterprise IT teams, and cloud vendors have debated whether Europe can build or nurture its own hyperscale-class cloud industry or whether the continent must accept U.S. and global hyperscalers as permanent infrastructure partners. That debate has accelerated into concrete policy action: the European Commission opened formal market investigations in November 2025 to determine whether Amazon Web Services and Microsoft Azure should be treated as “gatekeepers” under the Digital Markets Act (DMA), and whether the DMA’s framework is fit for policing cloud infrastructure more broadly.
The result is a multi-front realignment of incentives and procurement choices across the EU: governments are demanding more “sovereign” control; regional providers such as OVHcloud are doubling down on certified sovereign offers; analyst firms forecast a rapid rise in sovereign-cloud spending; and legal/commercial disputes—most visibly the CISPE–Microsoft negotiations over an EU‑specific “hoster” variant of Azure—have left open questions about whether Europe can rely on the technical concessions of global suppliers.
This article unpacks why the “missing cloud provider” matters, what Europe has actually done so far, which technical and commercial obstacles remain, and what pragmatic pathways exist for Europe to regain more control over its digital infrastructure without sacrificing performance and innovation.
However, Europe’s incumbent providers generally lack the global scale and breadth of managed services (platforms, advanced AI infrastructure, developer ecosystems) that AWS, Microsoft, and Google supply. That difference is not only technical; it affects partner ecosystems (ISVs, SaaS), training resources, and developer mindshare—factors that shape long‑term platform adoption.
If Brussels and national governments coordinate procurement, fund critical infrastructure, and enforce interoperability while European providers scale through partnerships and targeted investment, Europe can build a durable sovereign cloud ecosystem that serves regulated and strategic workl value‑led grounds. But that outcome requires hard, measurable commitments—capital, contracts, and timelines—not just slogans about sovereignty. The alternative is a patchwork of national champions that soothe political anxieties but leave Europe dependent on external advanced capabilities when it matters most. Recent regulatory moves and vendor negotiations show the problem is being taken seriously at every level, but the most consequential work—the patient engineering, capital deployment, and ecosystem building—happens in data centers, procurement offices, and at the bargaining table, not in policy press releases.
Commercial and market developments (OVHcloud’s sovereign positioning, CISPE–Microsoft negotiations, analyst forecasts about sovereign‑cloud spend) are reported by vendor press releases, specialist outlets, and industry analysts; these form the evidence base for the market dynamics described above. Readers should treat vendor claims about “sovereignty” and “local control” as claims to be independently audited—technical details such as certificate provenance, third‑party attestation, and licensing commitments are where the real differences appear.
Finally, community and industry forums show that these issues are actively discussed among practitioners and that the DMA probes have already shifted procurement conversations—illustrating the practical, not just theoretical, impacts of this policy moment.
Europe’s missing cloud provider is not a single vendor that someone can snap their fingers and create. It is a capability to be assembled—part technical, part commercial, part political. The better question for EU policymakers, CIOs, and industry leaders is not whether Europe can build a “copy” of AWS, but whether it can develop a resilient, interoperable, and trusted cloud backbone that protects sensitive data, supports digital competitiveness, and leaves Europe better off in a world where cloud power equals economic and strategic power.
Source: IEEE Spectrum IEEE Spectrum
Background / Overview
For years European policymakers, enterprise IT teams, and cloud vendors have debated whether Europe can build or nurture its own hyperscale-class cloud industry or whether the continent must accept U.S. and global hyperscalers as permanent infrastructure partners. That debate has accelerated into concrete policy action: the European Commission opened formal market investigations in November 2025 to determine whether Amazon Web Services and Microsoft Azure should be treated as “gatekeepers” under the Digital Markets Act (DMA), and whether the DMA’s framework is fit for policing cloud infrastructure more broadly.The result is a multi-front realignment of incentives and procurement choices across the EU: governments are demanding more “sovereign” control; regional providers such as OVHcloud are doubling down on certified sovereign offers; analyst firms forecast a rapid rise in sovereign-cloud spending; and legal/commercial disputes—most visibly the CISPE–Microsoft negotiations over an EU‑specific “hoster” variant of Azure—have left open questions about whether Europe can rely on the technical concessions of global suppliers.
This article unpacks why the “missing cloud provider” matters, what Europe has actually done so far, which technical and commercial obstacles remain, and what pragmatic pathways exist for Europe to regain more control over its digital infrastructure without sacrificing performance and innovation.
Why a European-scale cloud provider matters
Sovereignty is more than rhetoric
The phrase digital sovereignty has migrated from think‑tank briefs to procurement rules and national security planning. In practice it means three measurable expectations:- Data residency and legal jurisdiction — data processed and stored under EU law, minimizing foreign‑government legal reach.
- Operational control and supply‑chain transparency — the ability to audit, inspect, and limit third‑party or foreign dependencies in critical infrastructure.
- Resilience and strategic continuity — ensuring public services and critical industries can continue to operate during geopolitical or commercial shocks.
Economic and competitive rationales
Beyond sovereignty, the cloud market structure raises classic industrial‑policy concerns. Hyperscalers provide enormous scale and a vast feature set, but that scale gives them strategic leverage: pricing power on software licensing, preferential integration of higher‑margin AI features, and deep entanglement with enterprise application stacks. EU regulators now question whether these dynamics stifle competition, innovation, and European cloud firms’ ability to compete. The DMA probes into AWS and Azure are a direct manifestation of those concerns.The AI inflection point
AI workloads are increasing the stakes exponentially. Training and inference at scale push compute, network, and storage needs toward hyperscaler economics; if European data and models live on non‑European platforms, policy and industrial goals collide with technical realities. Analysts expect sovereign‑cloud spending to grow quickly as a share of overall cloud budgets—but the scale challenge remains: can EU providers reach the performance, network density, and global reach required for advanced AI? Early forecasts show rapid growth in sovereign spend but also underscore that only a fraction of workloads will migrate unless providers broaden their capabilities.Current state of play: what Europe has built so far
OVHcloud and regional champions
Europe is not starting from zero. OVHcloud, T-Systems, and a handful of other providers have steadily grown their footprint, invested in certifications (for example, France’s SecNumCloud qualification), and pitched “sovereign cloud” offerings aimed at government and regulated industries. OVHcloud has publicly positioned itself as a leading candidate to host some EU institutional workloads and has emphasized certified regions and locally operated facilities.However, Europe’s incumbent providers generally lack the global scale and breadth of managed services (platforms, advanced AI infrastructure, developer ecosystems) that AWS, Microsoft, and Google supply. That difference is not only technical; it affects partner ecosystems (ISVs, SaaS), training resources, and developer mindshare—factors that shape long‑term platform adoption.
Industry coordination and funding efforts
Budgets and programs are forming around the idea of a more resilient European cloud stack: targeted public spending, consortium models, and tender programs for “important projects of common European interest” seek to catalyze capacity building. The Commission and member states have floated funding to support secure, sovereign infrastructure, and private partnerships have emerged to bundle technical skills and data‑center capacity. These are meaningful steps, but they are still modest relative to the capital intensity and R&D budgets of the hyperscalers.Regulatory leverage and the DMA
One of the most consequential shifts is regulatory: by interrogating whether cloud services should be designated core platform services under the DMA—bringing hyperscalers under a stricter set of obligations—Brussels signals it will use law, not just procurement, to rebalance power. The DMA probes are an instrument aiming to force interoperability, portability, and non‑discrimination where commercial incentives have historically favored lock‑in.The stubborn technical and commercial gaps
Why building a hyperscaler is brutally hard
Hyperscale clouds are not simply “lots of data centers.” They are global systems of software, networking, hardware procurement, specialized chips, energy logistics, and deeply integrated developer platforms. Replicating:- Compute fleets and specialized accelerators at scale (GPUs, TPUs, custom LPUs).
- High‑capacity low‑latency backbone networks across many regions.
- A rich managed service catalog (databases, analytics, AI services, identity, security).
- Developer ecosystems and global channel partners.
Licensing and platform economics: the Microsoft case
Commercial frictions exacerbate the capacity problem. The Cloud Infrastructure Service Providers in Europe (CISPE) pressed Microsoft over licensing and run‑cost asymmetries, and a negotiated “hoster” product—meant to let European hosters operate Windows Server, SQL Server, and other MS software under Azure‑comparable terms—failed to meet expectations or delivery deadlines in 2025. CISPE and Microsoft restructured the settlement, but the episode underlines a larger point: without software‑stack cooperation from major ISVs, regional cloud providers face cost and integration disadvantages compared with Azure or AWS.Talent, energy, and supply chains
Hyperscale operations rely on deep talent pools for networking software, data‑center engineering, and AI systems. They also depend on predictable electricity pricing, chip supply (NVIDIA/H100s, custom silicon), and international supply chains. Building that capability across disparate EU national markets—each with its own regulation, labor market, and energy profile—adds friction that a single, centrally coordinated hyperscaler avoids.Strategies that could produce a credible European cloud
There is no single silver bullet. Achieving credible scale and capability will likely require a blended approach that mixes market forces, public investment, and regulatory nudges. Below are concrete, pragmatic options—ranked and explained.1. Federated European cloud consortium (practical realism)
Create a federation that combines multiple strong regional providers (OVHcloud, T‑Systems, others) with standardized APIs, federated identity, and orchestrated cross‑region networking. The EU can support this with procurement guarantees, interconnect subsidies, and a single certification framework. A federation leverages existing data‑center footprints while delivering a unified developer experience for key verticals (government, finance, defense).- Pros: Faster to build, lower capital requirement, can lean on existing vendor relationships.
- Cons: Achieves partial consistency; federation overhead complicates unified billing, SLAs, and developer experience.
2. Public–private “EU hyperscaler” seed with industrial partners
Use targeted public capital to seed a new entity—or a joint venture—that pools national investments, strategic industrial partners (telecoms, utilities), and a lead European cloud operator. The EU can condition funding on open standards, exportable IP, and multiyear procurement commitments from member states.- Pros: Centrally coordinated, can target strategic workloads (defense, health, public admin).
- Cons: Political complexity (who controls it?), risk of inefficiency, and long build times.
3. Open‑stack, open‑hardware, and niche specialization
Support open platforms and vertical specialization instead of trying to replicate every hyperscaler service. Some European providers could focus on privacy‑sensitive workloads, regulated industries, or AI inference workloads optimized for local data, offering superior compliance and tailored SLAs while integrating with multinational hyperscalers for capacity bursts.- Pros: Lower technical bar; better fit for regulated workloads; faster commercial adoption.
- Cons: Continues reliance on hyperscalers for frontier services; may not satisfy ambitions for full sovereignty.
4. Regulatory carrots and sticks
Use procurement policies, DMA enforcement, and Data Act incentives (and potential public contracts) to make it commercially viable for enterprises and public agencies to choose European cloud alternatives. At the same time, demand technical interoperability and data portability from global vendors so that migration costs fall.- Pros: Can reshape market incentives without building everything from scratch.
- Cons: Risk of regulatory overreach, trade disputes, and unintended vendor lock‑ins to a different stack.
Strengths and opportunities: why Europe still has a shot
- Trust and compliance as differentiators: For public administration, health, and regulated finance, the combination of EU law, local operations, and clear procurement channels can be a marketable advantage. European providers can charge a premium for demonstrable sovereignty.
- Growing sovereign demand: Analysts forecast a rapid rise in sovereign‑cloud spending; a meaningful minority of workloads will remain local for legal and strategic reasons, creating a base market to iterate from.
- Political will and funding: The Commission and several member states are actively exploring procurement pathways, public tenders, and seed funding, giving the effort policy momentum. Public contracts can anchor commercial viability for nascent capabilities.
- European industrial strengths: Telecom operators, energy firms, and industrial cloud customers offer complementary assets—fiber networks, energy procurement expertise, and committed anchor tenants—that can reduce build‑out risk if coordinated effectively.
Risks and hard limits: what could go wrong
- Underinvestment and time lag: Hyperscalers’ global scale is built on years of continuous investment. European initiatives risk undercapitalization or politicking that slows timelines, allowing hyperscalers to lock in features and customers. This is not merely financial inertia; it is a first‑mover advantage in developer mindshare and partner ecosystems.
- Fragmentation vs. unity: If member states prefer national champions, the market will fragment into small islands of sovereign clouds that cannot match scale—reducing both competitiveness and the EU’s bargaining power.
- False assurance and vendor dependence: Some “sovereign” offers may still rely on non‑EU software or critical components (for instance, certain management planes or chip dependencies), producing a misleading sense of independence. Procurement teams must audit software supply chains and licensing commitments carefully. Independent testing and certifications must be meaningful, not just marketing claims.
- License games and commercial friction: The CISPE–Microsoft episode shows that even when large suppliers appear to make concessions, delivery and licensing semantics can blunt the practical impact. European buyers need enforceable, verifiable commercial commitments, not merely aspirational statements.
A technical checklist for European sovereign cloud projects
Any serious initiative should demonstrate the following, ideally within 12–36 months for initial services:- Regionally operated data centers with verified operator control and clear legal contracts guaranteeing EU jurisdiction for data processing.
- Interoperable APIs and migration tools that make it technically straightforward to export workloads and state from hyperscalers without catastrophic cost.
- Managed AI infrastructure (GPU/accelerator pools, model‑hosting frameworks) with transparent pricing and SLAs supported by long‑term chip procurement strategies.
- Transparent licensing regimes for third‑party software to avoid hidden premium costs for running common enterprise stacks.
- Federated identity and consistent security baselines, including common attestation frameworks so customers can verify integrity and custody across providers.
What the DMA probes change (and what they don’t)
The DMA inquires are not a silver bullet, but they are a structural lever. If the Commission finds that cloud services constitute “core platform services” with gatekeeper obligations, regulators can force changes in how hyperscalers handle interoperability, data portability, and preferential treatment. That could lower migration costs for European alternatives and reduce subtle forms of commercial exclusion. However, legal designation alone won’t create hardware, data centers, or specialized local talent overnight. The DMA is a tool for market conditioning; Europe still needs industrial execution to fill capability gaps.Practical advice for IT decision‑makers in Europe (what to do now)
- Inventory and classify workloads. Not all workloads need sovereign hosting. Classify by sensitivity, regulatory risk, cost of outage, and AI‑dependency.
- Design for exit and portability. Use containerized architectures, standard APIs, and avoid proprietary managed services for critical components unless offset by contractual portability guarantees.
- Negotiate licensing and audit rights. As the CISPE case shows, licensing terms can be decisive—secure Azure‑ or Windows‑compatible terms where needed or insist on clear hoster pricing models.
- Adopt hybrid/federated architectures. Use regional sovereign clouds for sensitive data and hyperscalers for scale bursts; invest in secure data pipelines and robust identity federation.
- Engage in procurement coalitions. Joint procurement across public agencies and large enterprises can create scale that improves bargaining power and reduces unit costs.
Conclusion — a realistic roadmap, not a manifesto
Europe is not helpless; it has capable providers, a credible political voice, and growing public funds to invest in sovereign capabilities. But the continent is also confronting a technical reality: building a full hyperscale competitor from scratch would be enormously costly and slow. The pragmatic route lies in a hybrid of federation, targeted public investment, regulatory leverage, and transparent commercial agreements—with realistic expectations about what each track can deliver and when.If Brussels and national governments coordinate procurement, fund critical infrastructure, and enforce interoperability while European providers scale through partnerships and targeted investment, Europe can build a durable sovereign cloud ecosystem that serves regulated and strategic workl value‑led grounds. But that outcome requires hard, measurable commitments—capital, contracts, and timelines—not just slogans about sovereignty. The alternative is a patchwork of national champions that soothe political anxieties but leave Europe dependent on external advanced capabilities when it matters most. Recent regulatory moves and vendor negotiations show the problem is being taken seriously at every level, but the most consequential work—the patient engineering, capital deployment, and ecosystem building—happens in data centers, procurement offices, and at the bargaining table, not in policy press releases.
Notes on sources and verifiability
Key regulatory facts referenced here—most importantly the European Commission’s market investigations into cloud computing services under the DMA—are publicly reported by the Commission and major news outlets.Commercial and market developments (OVHcloud’s sovereign positioning, CISPE–Microsoft negotiations, analyst forecasts about sovereign‑cloud spend) are reported by vendor press releases, specialist outlets, and industry analysts; these form the evidence base for the market dynamics described above. Readers should treat vendor claims about “sovereignty” and “local control” as claims to be independently audited—technical details such as certificate provenance, third‑party attestation, and licensing commitments are where the real differences appear.
Finally, community and industry forums show that these issues are actively discussed among practitioners and that the DMA probes have already shifted procurement conversations—illustrating the practical, not just theoretical, impacts of this policy moment.
Europe’s missing cloud provider is not a single vendor that someone can snap their fingers and create. It is a capability to be assembled—part technical, part commercial, part political. The better question for EU policymakers, CIOs, and industry leaders is not whether Europe can build a “copy” of AWS, but whether it can develop a resilient, interoperable, and trusted cloud backbone that protects sensitive data, supports digital competitiveness, and leaves Europe better off in a world where cloud power equals economic and strategic power.
Source: IEEE Spectrum IEEE Spectrum
