A Sovereignty Requirement Written Into a Procurement Contract
When the European Central Bank put its digital euro payment-messaging component out to tender, it did not simply prefer European suppliers. It restricted eligibility to companies based in the European Union, full stop. That single procurement line did more to exclude Amazon Web Services, Microsoft Azure and Google Cloud from a flagship euro-area payment system than any digital sovereignty white paper the Commission has published to date. The component in question, SEPI, stands for Secure Exchange of Payment Information: the plumbing that would let banks and payment providers exchange digital euro transaction data securely if the currency goes live.
Senacor Technologies, a German-headquartered consultancy, won the SEPI tender and, per its own statement, named the sovereign cloud infrastructure as central to the bid. Senacor's partner principal consultant Dr. Ruben Debeerst said the digital euro was 'a key strategic project for the European financial market' and that the sovereign cloud fit was 'a very good fit' for the requirements. The eligibility rule, not a marketing preference, is what kept the tender inside the EU.
Who Is Actually Building It: Senacor, OVHcloud, Scaleway
Senacor named two subcontractors to deliver the cloud layer: OVHcloud and Scaleway, both headquartered in France. OVHcloud announced the selection on March 19, 2026, with Sylvie Houliere Mayca, the company's head for France, Middle East, Africa and BeLux, calling it confirmation of OVHcloud's position 'as the European Cloud leader' in the digital euro's build-out. Neither OVHcloud nor Scaleway is a niche player: both already sell EU-region cloud infrastructure at commercial scale to banks and public administrations, and both have separately positioned themselves around the EU's Cloud Sovereignty Framework's higher assurance tiers.
What makes this different from the dozens of 'sovereign cloud' marketing announcements European vendors put out every year is the counterparty. This is not a national ministry procurement or a mid-sized bank's back office; it is the European Central Bank's own payment infrastructure for a currency instrument the Eurosystem hopes will process consumer transactions across the entire euro area. If the digital euro launches on schedule, OVHcloud and Scaleway will be running cloud infrastructure that touches a meaningful share of European point-of-sale and peer-to-peer payments, without a single US hyperscaler in the stack by design.
The Market Share Gap the Digital Euro Is Designed to Close
The numbers explain why the ECB wrote the eligibility rule this tightly. US hyperscalers control roughly 70 percent of the European cloud infrastructure market, while EU-headquartered providers hold around 15 percent, according to market estimates cited in coverage of the tender. On the payments side, the imbalance is just as stark: more than two-thirds of card transactions in the euro area settle through international, US-dominated payment schemes such as Visa and Mastercard rather than domestic or European alternatives. Both figures describe the same underlying condition - critical financial infrastructure routed, by default, through non-EU companies - and the digital euro is explicitly pitched as an answer to both at once, on the payment-rail side and now, through this tender, on the cloud-infrastructure side too.
That is a more concrete sovereignty claim than most EU cloud initiatives get to make. The EU Cloud and AI Development Act's four-tier sovereignty framework, in force since mid-2026, sets rules for how public-sector contracts should weigh sovereignty; the ECB's SEPI tender simply enforced the toughest version of that logic on its own procurement, months before most public bodies had to.
The Law Is Still Catching Up to the Infrastructure
The digital euro's legal basis is not finished. The European Parliament backed a negotiating mandate for the digital euro regulation by a vote of 416 to 169, with 22 abstentions, on July 9, 2026, clearing the way for trilogue negotiations between Parliament, the Council of the European Union and the Commission. The Eurosystem's stated goal is to close that legislative process by the end of 2026, with a 2027 pilot phase and a potential first issuance of the digital euro as early as 2029, contingent on the ECB Governing Council's final decision after the law is adopted.
The sequencing is the detail worth sitting with: the cloud vendor selection closed in March 2026, four months before Parliament even cleared its negotiating mandate in July, and years before any final regulation exists. Procurement did not wait for the law to be settled before deciding who gets to run the infrastructure. That is either efficient parallel planning or a sign that the sovereignty requirement was treated as non-negotiable regardless of how the legislative debate over the digital euro itself turns out.
Why This Matters Beyond One Payment App
The SEPI tender is a template, not a one-off. It shows what an EU institution does when it is willing to write 'EU-headquartered only' into a contract rather than 'EU-preferred': the pool of eligible bidders shrinks to companies like OVHcloud and Scaleway that most enterprise buyers still treat as second-tier alternatives to the big three US clouds, and those companies win nine-figure infrastructure roles they would rarely land in an open global tender. If the digital euro launches with this cloud stack intact, it becomes the highest-profile proof point EU institutions have that a fully sovereign infrastructure chain is operationally possible for critical financial systems, not just legally mandated on paper.
The open question is whether other EU bodies follow the same eligibility logic for their own critical infrastructure - defense procurement, health data platforms, energy grid systems - or whether SEPI remains the exception that proves how rarely 'EU-based only' actually gets written into a contract rather than just argued for in a white paper. The Cloud and AI Development Act gives every EU public body the framework to make that same choice. Whether they use it the way the ECB just did is a 2027 question, not a 2026 one.
Read next: Europe's Cloud Law Now Ranks Providers 1 to 4 | Europe Gets S3 Storage That Skips US Clouds



