Euro-3C is Europe’s first serious test of federated cloud power

Euro-3C is not just another EU-funded technology project. It is the European Commission’s first large-scale attempt to show that telecom networks, edge computing, cloud infrastructure and AI orchestration can be joined into a working European platform, rather than discussed as separate policy ambitions. The project was unveiled at Mobile World Congress 2026 as a €75 million Horizon Europe initiative to build a federated Telco-Edge-Cloud infrastructure for digital sovereignty, with the Commission describing it as a way to deliver advanced digital services through Europe’s own connectivity infrastructure and reduce reliance on third-country providers.

Euro-3C lands at a moment when cloud sovereignty has become operational

Euro-3C matters because Europe has moved beyond the early language of “data sovereignty” and into a harder question: who controls the infrastructure, software, orchestration, security model and service continuity behind critical digital services? The announcement on 3 March 2026 put that question into a concrete programme. The Commission said Euro-3C would combine telecommunications networks, edge computing and cloud infrastructure into one integrated platform, with secure computing capacity closer to end users.

That is a narrower and more serious claim than the slogans around sovereign cloud that have circulated for years. Hosting data in Frankfurt, Paris, Madrid or Milan does not by itself create sovereignty if the management plane, software stack, privileged access model, contractual lock-in and security update chain remain outside European control. Euro-3C’s importance is that it tries to move the sovereignty debate from geography to architecture.

The project is also arriving after years of EU work on cloud, edge, data, telecom regulation, cyber resilience and AI compute. The Digital Decade policy programme sets 2030 targets around secure and sustainable digital infrastructure, digital transformation of businesses, skills and public services. The Commission’s cloud policy states that by 2030 75 percent of European businesses should use cloud-edge technologies and 10,000 climate-neutral and highly secure edge nodes should be deployed across Europe. Euro-3C is best read as an attempt to make part of that infrastructure target visible and testable.

The practical problem is direct. Europe regulates much of the digital economy but does not control enough of the infrastructure on which the digital economy runs. Hyperscale cloud, AI compute, advanced chip supply chains, developer platforms and many software ecosystems remain dominated by non-European providers. Euro-3C does not reverse that imbalance on its own. A €75 million project cannot match the capital expenditure of global hyperscalers. Its role is different: it tries to prove a federated European model that can be expanded, procured, standardised and connected to industrial use cases.

The word “federated” is doing real work here. Euro-3C is not a plan to build one central EU cloud. It is designed to connect existing capabilities from telecom operators, cloud providers, vendors, research centres, SMEs and public authorities under common technical and governance rules. Telefónica, which leads the consortium, described the project as the first pan-European sovereign infrastructure integrating Telco, Edge, Cloud and AI capabilities under a federated, open and secure model. That design choice reflects Europe’s fragmented market reality. No single European cloud or telecom actor can compete alone with the largest global platforms, but a federation can test whether distributed assets can behave like a coherent service layer.

The project’s hard facts define its political meaning

The strongest way to understand Euro-3C is to start with the confirmed facts. The European Commission announced it at Mobile World Congress 2026. It is funded through Horizon Europe. It carries a budget of €75 million. It aims to develop Europe’s first large-scale federated Telco-Edge-Cloud infrastructure. The Commission says it will reduce reliance on third-country providers by allowing advanced digital services to be delivered through Europe’s own connectivity infrastructure.

Telefónica’s announcement adds the operational shape. The consortium is led by Telefónica and includes more than 70 European entities. The system will deploy a federated multi-telco and multi-vendor infrastructure in production environments, with more than 70 edge and cloud nodes across more than 13 European countries. It is meant to support sectors including automotive, transport, energy and public safety, and it will validate nine high-business-value use cases.

The CISERO project, which supports the IPCEI-CIS community, frames Euro-3C as an execution layer for the European cloud-edge continuum. It describes the project as a working federated infrastructure connecting operators, vendors, SMEs, research centres and public authorities, with over 70 nodes across 13 countries and use cases in automotive, energy, transport and public safety.

These figures matter because they separate Euro-3C from policy theatre. A federation with 70-plus nodes, 13-plus countries and a large industrial consortium is not yet a market, but it is large enough to expose real technical and governance problems. Latency claims can be tested. Cross-border orchestration can be tested. Identity, access, workload placement, observability, incident response and service-level agreements can be tested. Vendor interoperability can be tested. Public safety requirements can be tested against commercial platform design.

There is also a notable difference between a research demo and a production-environment pilot. Telefónica says Euro-3C deploys infrastructure in production environments. That phrase should not be overread as proof of mature commercial services, but it does imply a stronger standard than laboratory prototyping. The question is not whether a consortium can make a dashboard work for a conference. The question is whether telecom and cloud assets in different countries, owned by different organisations, can supply dependable services under shared rules.

The consortium list also shows the project’s industrial breadth. Telefónica identifies beneficiaries including telecom operators such as British Telecom, Deutsche Telekom, KPN, Orange, Swisscom, Telenor, TIM and Vodafone; cloud and software players including Ionos, OVH, OpenNebula, SUSE and Nearby Computing; vendors and technology companies including Ericsson, Nokia and Thales; research institutions including Fraunhofer, IMEC, INRIA and TNO; and industrial or sectoral participants such as EDF, Stellantis, Teltronic, CAF, Frequentis and public safety organisations. This breadth is necessary. It is also one of the project’s risks. Federations fail when governance becomes heavier than the technical value they create.

Telco-edge-cloud means computing becomes part of the network

Euro-3C uses a term that can sound like EU jargon: Telco-Edge-Cloud. The concept is simple enough, but its implications are large. Telco-edge-cloud means that telecommunications networks, distributed edge nodes and cloud resources are treated as one programmable infrastructure layer. Applications do not merely connect to the network. They run across a distributed network-compute fabric.

Traditional cloud computing centralised workloads in large data centres. That model works well for many enterprise applications, storage, analytics and web services. It works less well when applications require very low latency, local data processing, high availability near users, or strict controls over where sensitive data moves. Edge computing responds by placing compute closer to devices, machines, vehicles, factories, ports, hospitals or emergency services. Telecom operators already own distributed network assets, rights of way, spectrum relationships, customer access networks and operational knowledge. Euro-3C tries to join those assets to cloud-native service models.

ETSI’s Multi-access Edge Computing work has long defined the edge as an IT service environment at or near the network edge, characterised by low latency, high bandwidth and access to network information that applications can use. Euro-3C takes that logic into a European industrial-policy frame. It asks whether edge computing can become part of a sovereign cloud and telecom market, rather than a feature bolted onto global cloud platforms or isolated operator projects.

The architecture also matters for 6G. The Commission’s Euro-3C announcement links the project to European innovation in 6G, AI, cybersecurity and telecoms. 6G is not only about faster radio. Its expected use cases include sensing, ultra-reliable services, distributed intelligence, industrial automation and immersive communications. Those use cases need compute placement, data handling and network programmability. A 6G economy cannot be built only on antennas. It needs a service fabric.

3GPP began preparing 6G study work through Release 20 discussions and a 2025 workshop covering radio, system architecture and core network requirements. ITU agreed draft IMT-2030 technical performance requirements for 6G radio interfaces in March 2026. Euro-3C is not a 6G standardisation body, but it sits close to the problem that 6G standards will face: network capabilities need to be exposed, orchestrated and monetised as services.

For telecom operators, this is existential. Connectivity revenue has been pressured for years while cloud platforms captured much of the value created above the network. If operators remain only access providers, edge computing will be a cost. If operators can federate their assets into programmable compute and service platforms, edge becomes part of a new business model. Euro-3C is partly a sovereignty project and partly a test of whether European telecoms can move up the value chain without each building a closed national island.

Federation is Europe’s workaround for scale

The United States built cloud scale through hyperscalers. China built scale through giant platform companies tied to a large domestic market and state priorities. Europe has strong telecom operators, industrial firms, software companies, research institutions and cloud providers, but it does not have an equivalent hyperscale champion with the same global depth across infrastructure, platform services, AI tooling and developer ecosystems.

Euro-3C’s answer is federation. A federation does not erase fragmentation. It creates rules that allow fragmented assets to cooperate. The strategic bet is that Europe can turn its distributed market structure from a weakness into an infrastructure model. That is ambitious, but it is not irrational. Critical European sectors often require local presence, regulatory assurance, public procurement compliance, language coverage, national security controls and sector-specific integration. A federated model may fit those needs better than a single platform imported from abroad.

The Commission’s cloud policy already points in this direction. The European Alliance for Industrial Data, Edge and Cloud aims to support next-generation edge and cloud technologies, bringing together businesses, Member State representatives and experts to define investment roadmaps for secure, distributed, interoperable and resource-efficient computing technologies. Euro-3C becomes a live test of those words.

Federation also gives Europe a way to use what it already has. Telecom operators have networks and edge sites. Cloud providers have infrastructure and service platforms. Industrial companies have use cases and data. Research centres have technical depth. Public authorities have procurement demand and security requirements. SMEs have specialised software. The challenge is not the absence of capability. It is the absence of a common operating model.

That operating model must include workload portability, identity federation, policy enforcement, service discovery, common APIs, observability, auditability, data governance, billing, procurement rules, security certification and incident response. Federation is not just a diagram of connected nodes. A federation without enforceable rules is a loose partnership. A federation with too many rules becomes unusable. Euro-3C’s success depends on finding the line between those failures.

The project also faces a market truth: developers follow simplicity. If a global cloud platform gives a developer one account, one documentation model, one API catalogue, one billing system and one support path, a European federation must offer enough coherence to compete for real workloads. Sovereignty may matter to governments and regulated sectors, but poor developer experience kills adoption. Euro-3C will need to prove not only that workloads can run across European nodes, but that service builders can use the platform without negotiating every deployment as a bespoke integration.

Euro-3C is linked to the Digital Networks Act and telecom market reform

The Commission says Euro-3C is directly aligned with the proposed Digital Networks Act. That link is important because infrastructure projects and regulation must move together. The Digital Networks Act proposal, published on 21 January 2026, offers a modernised legal framework intended to strengthen Europe’s competitiveness, replace the EU Electronic Communications Code and address fragmentation in the electronic communications sector. It also aims to support network security and resilience by limiting dependencies and promoting EU-level cooperation.

The DNA context explains why Euro-3C is political. Europe’s telecom market is fragmented across national licensing systems, spectrum histories, consumer pricing dynamics and regulatory traditions. Operators argue that fragmentation limits scale and investment capacity. Regulators worry that consolidation may raise consumer prices or reduce competition. Euro-3C sits between those positions. It does not require a single telecom market to be completed before infrastructure cooperation begins. It uses a federated technical project to show what cross-border cooperation could look like.

The Commission’s broader message is that advanced connectivity, cloud, AI and space technologies need a more coherent network base. This is not just about telecom operators seeking regulatory relief. Europe’s industrial sectors increasingly rely on data movement, low-latency processing, software-defined operations and secure digital services. Factories, energy grids, transport systems, emergency services and vehicle platforms all become more network-dependent as they digitise.

Euro-3C could help policymakers see which regulatory barriers are real and which are excuses. If cross-border service deployment runs into incompatible security rules, procurement clauses, spectrum constraints, data localisation requirements or certification gaps, those lessons are valuable. A pilot cannot solve the single market, but it can reveal where the single market is operationally thin.

There is also a competition issue. A federated European infrastructure must avoid becoming a protected club that raises barriers to smaller providers. The Commission’s language around open and interoperable systems suggests awareness of that risk. But openness has to be tested in procurement, APIs, governance seats, certification costs and onboarding timelines. A sovereign infrastructure that only large incumbents can join would reproduce the concentration problem under a European label.

The cloud-edge target shows the size of the gap

Europe’s official targets are not modest. By 2030, 75 percent of European businesses should use cloud-edge technologies, and 10,000 secure, climate-neutral edge nodes should be deployed across the continent. Yet the same Commission cloud page reports that in 2023, 45.2 percent of businesses used cloud services, with strong differences by company size: 77.6 percent of large enterprises, 59 percent of medium enterprises and 41.7 percent of small businesses. It also states that edge node deployment grew from 498 in 2022 to about 1,836 in 2024.

Those numbers reveal two different gaps. The first is adoption. Many European SMEs still do not use cloud services at the level needed for a digital industrial base. The second is infrastructure. Edge deployment is growing, but 1,836 nodes is far from 10,000. Euro-3C’s 70-plus nodes are therefore meaningful as a pilot but small compared with the 2030 target.

Euro-3C against Europe’s 2030 cloud-edge targets

The table shows Euro-3C’s proper scale. It is not the fulfilment of Europe’s cloud-edge ambition; it is a testbed for the model Europe wants to scale. Its value will depend on whether the pilot produces reusable architecture, procurement confidence, open components, sector demand and investment follow-through.

This distinction matters because Europe has a record of launching high-ambition digital initiatives that do not always become market structure. The gap between pilot and platform is where many projects fail. A pilot can absorb complexity through public funding and motivated partners. A platform needs commercial clarity. Customers must know what they can buy, who is responsible, how performance is guaranteed, where liability sits, how data is governed and how switching works.

For SMEs, the gap is sharper. A small manufacturer or mobility startup will not adopt a federated edge-cloud platform because it fits EU strategy. It will adopt it if the service is simpler, safer, faster, cheaper or more compliant than the alternatives. Euro-3C’s nine use cases therefore need to be judged not only on technical success but on whether they reveal repeatable market offers.

Sovereignty is shifting from data location to control of operations

European cloud sovereignty used to be framed heavily around data location: where data is stored, which jurisdiction applies and whether sensitive data stays inside the EU. Those questions still matter. GDPR, the Data Act, public procurement rules, national cybersecurity schemes and sectoral laws all keep location and access controls relevant. But the infrastructure debate has become more demanding.

The Commission’s April 2026 sovereign cloud procurement is useful context. The Commission awarded four cloud contracts to diversify providers and avoid lock-in. It said its Cloud Sovereignty Framework measured sovereignty through eight objectives, including strategic, legal, operational and environmental considerations, supply-chain transparency, technological openness, security and compliance with EU law. It also introduced Sovereignty Effectiveness Assurance Levels, from SEAL-0 to SEAL-4.

That framework shows where the EU’s thinking is moving. Sovereignty is becoming an evidence-based control model, not a branding claim. It is no longer enough to say that a data centre is European. A provider must show who controls the service, whether non-EU third parties can disrupt it, how supply chains are managed, what legal exposure exists, how operations are staffed, which technologies are open or proprietary, and how customers can verify compliance.

Euro-3C should be understood through that same lens. A federated infrastructure will have many participants, which means sovereignty cannot be assumed from nationality alone. Some members may rely on global components. Some may use open-source stacks. Some may operate under national security rules. Some may bring specialised industrial software. The federation will need a way to express and enforce trust levels across heterogeneous assets.

This is technically hard. In a single cloud provider, control is centralised. In a federation, control is distributed. Every cross-domain service raises questions: who authenticates the workload, who authorises placement, who holds keys, who sees logs, who responds to incidents, who patches the stack, who reports outages, who certifies compliance and who accepts liability? A sovereign federation must answer those questions with machinery, not slogans.

The sovereignty debate also includes legal exposure to non-EU jurisdictions. European customers in sensitive sectors often worry that foreign laws, corporate control chains or extraterritorial access demands could affect their data or operations. Euro-3C cannot remove all such concerns across all components. Its contribution would be to make controls explicit, auditable and selectable by workload sensitivity.

IPCEI-CIS gives Euro-3C its industrial backbone

Euro-3C does not start from zero. It connects with the IPCEI on Next Generation Cloud Infrastructure and Services, known as IPCEI-CIS. The Commission describes IPCEI-CIS as the first Important Project of Common European Interest in the cloud and edge computing domain. It aims to create an interoperable and openly accessible European data processing ecosystem, the multi-provider cloud-to-edge continuum, and to develop federated, energy-efficient and trustworthy cloud and edge distributed data processing technologies. Seven Member States are providing up to €1.2 billion in public funding, expected to unlock €1.4 billion in private investment.

That background matters because Euro-3C is not merely a standalone pilot. It is part of a chain of EU efforts to build a cloud-edge continuum. IPCEI-CIS focuses on major industrial research, development and first deployment. Euro-3C adds a telco-edge-cloud federation layer with live nodes, telecom participation and sector use cases.

CISERO frames Euro-3C as the clearest signal that the convergence infrastructure Europe has been designing is ready to scale. That claim is optimistic, but the connection is real. IPCEI-CIS develops components, architectures and industrial capacity. Euro-3C tests how those capabilities can work across telecom and cloud environments.

The relationship also highlights a funding contrast. IPCEI-CIS involves billions in public and private commitments. Euro-3C is €75 million. The difference does not make Euro-3C minor. It means Euro-3C has to convert earlier investments into visible infrastructure learning. If Euro-3C produces reusable federation patterns, it can punch above its budget. If it becomes an isolated showcase, its strategic value will fade.

The IPCEI model also brings state-aid discipline and industrial-policy complexity. Member States support national champions and strategic projects, but European value depends on interoperability across borders. Euro-3C’s federated design can act as a bridge between national investments and a European service market. That bridge will be tested when commercial interests differ. Operators may prefer to defend their own platforms. Cloud providers may want differentiation rather than standardisation. Vendors may support openness until it reduces lock-in. Public authorities may demand sovereignty guarantees that slow deployment.

The project’s governance must therefore reward integration. Participants need reasons to expose capabilities into the federation rather than simply use the project to subsidise their own roadmaps. The strongest output would be a set of open interfaces, certification models, reference implementations and procurement patterns that survive after the Horizon Europe funding cycle.

Open source is not optional for a federated European stack

The Euro-3C ecosystem sits beside the Commission’s Open Internet Stack work for 3C building blocks. The CORDIS programme page for “Open Internet Stack” says the action will support an open-source framework governed by contributor communities, providing technology components for the operation of the 3C large-scale pilot. It identifies trust technologies, network and connectivity technologies, and decentralised technologies based on open standards as core areas. It also says applicants should cooperate with the 3C pilot to integrate requirements, specifications and building blocks.

This is more than a philosophical preference. A federated infrastructure cannot rely only on closed bilateral integrations. Open interfaces and open-source components reduce the cost of joining, auditing and extending the federation. They also make it easier for SMEs and research institutions to participate without being trapped behind proprietary gates.

Open source does not automatically guarantee sovereignty. A dependency can be open and still poorly maintained. A project can be open but controlled by a narrow contributor base. A software bill of materials can be visible but still vulnerable. Yet open source gives Europe a better chance to audit, adapt and govern critical components than black-box infrastructure.

The Open Internet Stack call also refers to privacy-enhancing technologies, AI-based agents, trusted identity, security, resilience, energy efficiency, accessibility audits, packaging, localisation, documentation and licensing. Those details are important because real infrastructure fails in the unglamorous layers. Packaging, documentation and localisation often determine whether public administrations and SMEs can adopt a stack. Licensing determines whether commercial actors can build on it. Security audits determine whether it can be used in sensitive sectors.

Euro-3C’s open-source posture should be judged by outputs. Does the project release usable components? Are APIs documented? Can third parties test integration without insider access? Are conformance tools available? Are identity, trust and orchestration modules reusable? Are components governed by credible communities after funding ends? If the answer is yes, Euro-3C could strengthen a European digital commons. If the answer is no, it risks becoming a consortium-only architecture.

Open source also helps with standardisation. The European Alliance for Industrial Data, Edge and Cloud published a Telco Cloud Reference Architecture in 2025 and has produced roadmaps around open source and trust principles. Reference architectures gain value when they are paired with running code, testbeds and procurement criteria. Euro-3C can connect those layers.

AI changes the economics of edge and cloud

Euro-3C is being launched into an AI infrastructure race. The Commission’s AI Continent Action Plan says Europe aims to mobilise €200 billion for AI development, finance up to five AI gigafactories with €20 billion, and support startups, industry and research through 19 AI factories. The AI Factories programme also links supercomputing resources, startups, industry, research and support initiatives across Member States, with investments in supercomputing infrastructure and AI factories expected to reach €10 billion over 2021-2027 through EuroHPC JU.

Euro-3C is not an AI factory and should not be confused with GPU mega-infrastructure. Its relevance to AI is different. AI workloads need a continuum. Training frontier-scale models may require massive centralised compute. But inference, industrial AI, robotics, public safety applications, transport optimisation, energy balancing and connected-vehicle services often need compute closer to where data is generated. The AI economy will not run only in giant data centres; it will also run at the edge.

That makes telco-edge-cloud important. A factory using computer vision for quality control may not want to stream all raw video to a distant cloud. A connected vehicle system may need low-latency coordination and local hazard awareness. An energy grid application may require local resilience during network disruption. A public safety system may need guaranteed availability, prioritised connectivity and strict access controls. These are not abstract use cases. They are the kinds of sectors Euro-3C names.

The AI layer also increases orchestration complexity. A workload may need to run partly on a device, partly at an edge node, partly in a regional cloud and partly in a central compute facility. Models may need updating. Data may need filtering before leaving a local site. Sensitive information may need privacy-enhancing processing. Inference may need fallback paths when connectivity degrades. This requires more than cloud hosting. It requires policy-aware placement and lifecycle management.

Telefónica says Euro-3C integrates AI-enabled orchestration capabilities and interoperable services. That detail deserves scrutiny. AI-enabled orchestration could help optimise workload placement, energy use, latency, resilience and security. It could also create new opacity if operators cannot explain why a workload moved, why a service degraded, or why a policy decision was made. In critical sectors, AI orchestration needs audit trails, override controls and explainable policy enforcement.

The link between Euro-3C and AI sovereignty is therefore not just about where models run. It is about who controls the operational substrate for AI services. If Europe builds AI factories but lacks a European edge-cloud layer for deployment, much industrial AI value may still flow through non-European platforms. Euro-3C tests whether deployment infrastructure can become part of Europe’s AI strategy.

Public safety use cases will expose the toughest requirements

Public safety is one of the most revealing Euro-3C sectors. Telefónica’s announcement lists public safety among target sectors, and CISERO notes that national public safety and civil protection authorities are affiliated through PSCE, including authorities from Finland, Greece, Czechia, Spain, France, Ireland, the Netherlands, Norway, Poland, Romania and Sweden.

Public safety networks have requirements that ordinary enterprise applications often do not. They need availability during crisis, priority access, resilience against cyberattack, interoperability across agencies, lawful governance, data protection, secure identity, reliable location, and sometimes cross-border coordination. Emergency services cannot treat edge-cloud federation as a best-effort experiment.

This makes public safety a useful stress test. If Euro-3C can support public safety scenarios, it will have passed a more demanding benchmark than many commercial demos. The project will have to address identity and access management across organisations, trusted data sharing, incident escalation, operational continuity and network prioritisation.

Public safety also exposes sovereignty in its clearest form. A state must know who can access emergency communications data, who can operate the infrastructure, who can update software, who can see logs, who can disrupt services and how systems recover under attack or disaster. These questions cannot be outsourced to generic cloud terms. They require sovereign control, or at least sovereign assurance.

The risk is that public safety requirements become so specific that they do not translate into broader market products. That is a common problem in public-sector innovation. A platform built for emergency services may become too complex or expensive for SMEs. Euro-3C will need to separate reusable federation components from sector-specific controls. Identity, audit, orchestration and resilience features can serve many sectors. Public safety workflows and legal requirements may remain specialised.

The public safety dimension also connects to NIS2 and broader EU cybersecurity policy. Cloud computing providers, data centres, digital infrastructure and essential services operate under growing cybersecurity obligations. The Commission’s cybersecurity policy page states that the Cyber Resilience Act entered into force on 10 December 2024 and sets common standards for products with digital elements, including lifecycle security requirements. A federated infrastructure touching public safety will need security-by-design, supply-chain visibility and incident reporting discipline from the start.

Automotive, transport and energy are where edge becomes industrial

Euro-3C’s named sectors — automotive, transport, energy and public safety — are not random. They share a need for distributed intelligence. They also have strong European industrial bases. If Europe wants digital sovereignty to mean industrial competitiveness rather than only regulatory independence, these sectors matter.

Automotive is moving toward software-defined vehicles, connected mobility services, fleet data platforms, driver-assistance systems and eventually more automated operations. Many services depend on low-latency data, regional processing, secure updates and cross-border continuity. A car may travel through several European countries in a day. A federated edge-cloud infrastructure could support services that need local responsiveness without losing a European service model.

Transport systems face similar needs. Rail, ports, logistics, road traffic management and urban mobility generate large data flows and require resilient coordination. Edge computing can reduce latency and bandwidth use by processing data near terminals, depots, intersections and vehicles. A federated model could allow transport operators to use distributed resources without building everything themselves.

Energy is perhaps even more important. Europe’s power systems are becoming more digital as renewable generation, storage, grid balancing, electric vehicles and demand response expand. These systems need secure, low-latency control and monitoring. They also need resilience because energy infrastructure is a strategic target. Edge-cloud federation could support local processing and regional coordination while reducing dependence on distant central clouds.

The business case in these sectors will not be generic “cloud migration.” It will be specific: predictive maintenance at the edge, grid anomaly detection, vehicle-to-infrastructure services, local digital twins, video analytics, safety monitoring, emergency coordination, industrial control support and secure data exchange. Euro-3C will succeed commercially only if it turns broad sector labels into repeatable service patterns.

European industry also needs trust. Industrial firms are often cautious about sharing operational data. They worry about intellectual property, cyber exposure, contractual lock-in and unclear liability. A European federated infrastructure may appeal if it offers stronger governance, local presence, sector-specific assurance and easier compliance. But trust will depend on measurable controls, not European branding.

The project could also support data-space initiatives. Europe has promoted common European data spaces in sectors such as mobility, energy, health and manufacturing. Data spaces need trusted exchange rules. Edge-cloud federation could provide infrastructure for data processing and sharing near data sources. The challenge is to align governance across data spaces, cloud services and telecom networks rather than create parallel frameworks.

The strongest use cases will be measurable, not decorative

Euro-3C will validate nine high-business-value use cases, according to Telefónica. The phrase is promising, but the quality of those use cases will decide much of the project’s credibility. European technology pilots sometimes suffer from a familiar weakness: they produce showcases that demonstrate possibility but not adoption logic.

A strong Euro-3C use case should answer several questions. What workload is being run? Why does it need federation? Why does it need edge? Why does it need telecom integration? What latency, resilience, security or sovereignty requirement cannot be met as well by a conventional cloud setup? Who is the buyer? What is the cost model? What regulation or procurement requirement makes the European model attractive? What would it take to scale from pilot to paid deployment?

A weak use case will show a dashboard, a sensor feed or an AI demo without proving why Euro-3C’s architecture is necessary. That would be a missed opportunity. The project’s value lies in proving where federated telco-edge-cloud is the right architecture, not in proving that distributed computing can run an application.

Measurement should include latency, uptime, failover, workload portability, cross-provider orchestration, energy use, security events, onboarding time, integration cost and user outcomes. A use case in transport, for example, should report whether edge placement reduced response time enough to matter. A public safety use case should show whether agencies can share data without losing control. An energy use case should show whether local processing improves resilience or reduces bandwidth.

Commercial measurement is equally important. Can a customer procure the service without custom legal work across every partner? Can an SME integrate through documented APIs? Can a public authority specify sovereignty levels in a tender? Can a provider join the federation without months of one-off negotiation? These are platform questions.

Euro-3C should also publish negative lessons. If certain workloads do not benefit from edge placement, that is useful. If cross-border legal rules slow deployment, that is useful. If identity federation is harder than expected, that is useful. Publicly funded infrastructure projects create more value when they share failure modes, not only success stories.

The consortium model brings capacity and friction

Euro-3C’s consortium is large by design. The Commission says 87 consortium members are involved. Telefónica’s announcement lists more than 70 European entities and names many beneficiaries across telecom, cloud, software, equipment, research, industry and public authorities. Large consortia are often necessary for EU infrastructure projects because the market is fragmented and the political goal is cross-border participation. But scale creates friction.

The advantage is breadth. No single actor has all the assets. Telecom operators bring networks and edge sites. Cloud providers bring compute platforms. Vendors bring network and orchestration technology. Research centres bring architecture and testing. SMEs bring specialised software. Industrial firms bring use cases. Public authorities bring demanding requirements. This is the right mix for a federation.

The problem is incentives. Each participant has its own commercial roadmap. Operators may compete with each other. Cloud providers may resist common interfaces that make switching easier. Vendors may prefer architectures that favour their products. Research institutions may prioritise technical novelty. Public authorities may prioritise risk avoidance. SMEs may need speed that large governance structures do not provide.

A successful federation needs governance that is strict where trust requires it and loose where innovation needs it. That means common rules for security, identity, interoperability and compliance, but room for providers to differentiate services. If Euro-3C standardises too little, it will not be a platform. If it standardises too much, it will move too slowly.

The consortium also needs a credible path after funding. Horizon Europe funding can pay for coordination, testing and development. It cannot by itself create a durable commercial operating body. Euro-3C will need some combination of association, foundation, standardisation group, procurement framework, marketplace, certification scheme or integration with existing EU instruments. The final structure matters because customers will not buy critical services from a temporary project.

The presence of ETSI in the beneficiary list is notable. Standards bodies can help convert project learning into reusable specifications. But standards alone do not create markets. They need implementations, certification and demand. Euro-3C’s best route is to generate running reference implementations and then feed standards, not the other way around.

Telecom operators need Euro-3C to prove a new role

European telecom operators face a strategic squeeze. They carry the traffic generated by cloud, streaming, platforms, enterprise software and AI services, but they capture only part of the value. Network investment demands remain high while revenue growth is limited. Edge computing has long been presented as a new opportunity, yet many operator edge initiatives have struggled to create broad demand.

Euro-3C gives operators a chance to test a different role. Instead of selling connectivity alone, they can contribute network-aware compute, local presence, guaranteed performance, security, identity, service orchestration and sector-specific capabilities. The operator becomes part of a distributed cloud service, not only the pipe leading to it.

This is difficult because cloud culture and telecom culture differ. Cloud platforms move fast, expose developer-friendly services and expect programmable self-service. Telecom networks are built around reliability, standards, spectrum, regulation and long investment cycles. Telco-edge-cloud convergence requires both cultures to change. Operators need better software and developer experience. Cloud actors need deeper integration with network capabilities and stricter guarantees for critical use cases.

Euro-3C’s multi-telco model is important. A service that works only on one operator’s network has limited European value. Industrial customers need cross-region and cross-border coverage. If a logistics company uses edge services in Spain, Germany, France and the Netherlands, it does not want four separate operator-specific platforms. Federation is the way to offer broader coverage without requiring all operators to merge their systems.

Operators also need a monetisation model. Edge services may include compute rental, managed application hosting, quality-of-service guarantees, private network integration, security services, data processing, industry platforms or outcome-based contracts. Euro-3C’s use cases should clarify which of these models are credible. The telecom sector has often overestimated willingness to pay for abstract low latency. Customers pay for solved problems.

There is also a risk of strategic ambiguity. Operators may say they want openness while trying to protect control of their own edge assets. The federation will need to balance local operator autonomy with common service expectations. If every deployment requires customer-specific integration with each operator, the model will fail to scale.

European cloud providers need a market, not only recognition

Euro-3C includes European cloud and software actors such as Ionos, OVH, OpenNebula and others named by Telefónica. Their role is central. A sovereign telco-edge-cloud federation cannot be built by telecom operators alone. It needs cloud platforms, orchestration software, developer tools, storage, identity, automation, security, observability and managed services.

European cloud providers have often faced a brutal market reality. They may offer strong compliance, local support and sovereignty advantages, but global hyperscalers dominate developer mindshare, service breadth and enterprise procurement. Euro-3C gives European providers a route into differentiated workloads where sovereignty, low latency, industrial integration and public-sector assurance matter.

The Commission’s April 2026 sovereign cloud procurement also sends a signal. The Commission awarded contracts to four providers or partnerships: Post Telecom with OVHcloud and CleverCloud, STACKIT, Scaleway, and a Proximus-led partnership involving S3NS, Clarence and Mistral. It used the Cloud Sovereignty Framework to translate sovereignty into measurable criteria and said the tender set a benchmark for secure, compliant and values-based cloud adoption in the public sector.

That procurement context matters for Euro-3C. Demand is the missing piece in many European cloud projects. If EU institutions, Member States and regulated sectors begin to procure measurable sovereignty, European cloud providers can invest with more confidence. Euro-3C can help define services that public and industrial buyers can specify.

But recognition is not enough. European cloud providers need to compete on technical quality, automation, managed services, price transparency, ecosystem support and reliability. The Commission’s procurement note said selected providers had to demonstrate reliable technology, fully managed services, developer experience and automation, and that EU providers are closing the gap. That phrase — closing the gap — is the right standard. Sovereignty may open the door, but technical quality keeps customers.

Euro-3C can help by giving European cloud actors a bigger combined surface. A provider with strong cloud services but limited edge reach can connect with telco nodes. An open-source platform can become part of a broader federation. A specialised SME can deploy into multiple countries through common mechanisms. The federation becomes a market multiplier if onboarding and interoperability are real.

Developer experience may decide adoption faster than politics

Infrastructure projects often speak to policymakers, operators and industrial executives. Developers decide whether platforms become used. A developer building an industrial AI application, transport analytics service or emergency response dashboard will ask direct questions: Where is the documentation? How do I deploy? How do I test latency? How do I choose a node? How do I manage secrets? How do I debug failures across providers? How do I estimate cost? How do I get support?

If Euro-3C cannot answer those questions, its market adoption will be weak. A federated cloud must feel less complex than the infrastructure beneath it. That is the central product challenge.

Global cloud platforms became powerful partly because they reduced friction. Developers could access compute, databases, messaging, identity, observability and AI services through a common interface. Enterprises adopted them because the platform abstracted infrastructure. A European federation starts with more complexity because ownership is distributed. The user interface, API model and operational tooling must hide that complexity without hiding the controls that sovereignty requires.

This is a difficult balance. Sovereign customers need transparency. Developers need simplicity. Security teams need policy control. Procurement teams need measurable assurance. Operators need autonomy. The platform must satisfy all without becoming unusable.

Euro-3C should therefore treat developer experience as infrastructure. Documentation, SDKs, sample applications, sandboxes, conformance tests, onboarding flows and support models are not secondary deliverables. They are adoption mechanisms. A technically impressive federation that requires insider knowledge will remain a research consortium asset.

The Open Internet Stack work may help here if it produces packaged, documented, auditable components. But the federation still needs a product layer. Developers do not build on policy documents. They build on APIs, templates, workflows and trusted services.

Security has to be built into the federation rather than wrapped around it

Euro-3C’s security challenge is larger than the sum of its participants. A federated system has more interfaces, more trust relationships, more operational domains and more possible failure paths than a single-provider platform. It also targets sectors where security failures can become public-safety, energy or transport failures.

The Commission’s Digital Networks Act proposal stresses network security and resilience, including limiting dependencies in the connectivity ecosystem and promoting EU-level cooperation. The Cyber Resilience Act sets lifecycle cybersecurity expectations for products with digital elements. NIS2 raises obligations for many essential and important entities, including digital infrastructure and service providers. Together, these frameworks mean Euro-3C must be designed for compliance and assurance from the start.

Security in a federation starts with identity. Every workload, operator, administrator, service, device and API call needs trusted identity. Access must be scoped, logged and revocable. Privileged access is especially sensitive. A sovereign infrastructure cannot allow unclear administrator control across borders or providers.

Key management is equally important. Customers will ask who holds encryption keys, where keys are stored, whether hardware security modules are used, whether providers can access data, and how keys are recovered. In cross-provider deployments, key custody can become complicated. A weak answer undermines sovereignty claims.

Observability and incident response are harder in a federation. Logs may sit across providers. Security events may cross domains. An incident may involve a telecom node, cloud platform, application provider and public authority. The federation needs shared playbooks, escalation paths, evidence preservation and reporting rules. Without common incident response, federation becomes a blame-distribution system.

Supply-chain security also matters. Hardware, firmware, orchestration software, containers, dependencies and AI models can all introduce risk. The Commission’s Cloud Sovereignty Framework includes supply-chain transparency and technological openness among its objectives. Euro-3C should align with that direction by making component provenance and dependency risks visible.

Security cannot be only restrictive. It must also support adoption. If compliance demands make deployment too slow, users will bypass the platform. The right model is policy automation: controls embedded into deployment workflows, with evidence generated automatically. That would make Euro-3C more attractive to regulated sectors.

Interoperability is the project’s make-or-break test

Euro-3C’s core claim is federation. Federation without interoperability is marketing. Interoperability means that services, workloads, policies and data can move or cooperate across providers without expensive custom work every time. It does not require every provider to be identical. It requires common layers where common behaviour matters.

The Commission’s IPCEI-CIS page defines the cloud-edge continuum as interoperable and openly accessible, with federated, energy-efficient and trustworthy cloud and edge distributed data processing technologies. The European Alliance for Industrial Data, Edge and Cloud also focuses on secure, distributed, interoperable and resource-efficient computing technologies. Euro-3C is where those concepts must survive contact with deployed infrastructure.

Interoperability has several layers. Infrastructure interoperability allows workloads to run on different compute environments. Service interoperability allows identity, storage, networking, monitoring and orchestration to behave consistently. Data interoperability allows information to be exchanged with agreed formats and semantics. Governance interoperability allows policies, assurance levels and compliance evidence to be understood across organisations.

The hardest layer may be operational interoperability. A workload can be technically portable but operationally stuck if monitoring, billing, support, security approvals or liability do not travel with it. True portability includes the boring parts of service management.

Euro-3C should avoid pretending that all workloads need full portability. Some industrial systems will be tied to specific sites or hardware. Some public safety applications will have national constraints. The goal should be clear workload classes and federation patterns. Which workloads can move freely? Which can fail over regionally? Which are pinned to a country? Which can burst into another provider? Which require special assurance?

Open standards and APIs will help, but certification is needed. Participants need to know whether an implementation conforms. Customers need to know whether a service meets a sovereignty or performance level. Certification can become bureaucratic, but without it, trust becomes manual.

The Data Act and cloud switching strengthen the logic of federation

The EU Data Act is relevant because it addresses access to and use of data, and it also includes rules intended to make switching between data processing services easier. The Commission describes the Data Act as a law to make industrial data more accessible and usable, encourage data-driven innovation and clarify who can use which data under which conditions.

For Euro-3C, the cloud-switching logic is important. A federated infrastructure should not reproduce lock-in under another name. Customers should be able to move workloads, use multiple providers and avoid dependence on a single stack where practical. This aligns with the European desire for competitive cloud and edge services.

Switching is not easy in practice. Data gravity, proprietary APIs, managed services, identity systems, networking configurations and operational tooling create lock-in. Edge workloads add location dependencies. Public-sector compliance adds approval dependencies. The Data Act can reduce contractual barriers, but technical portability must be engineered.

Euro-3C can become a practical answer to cloud switching if it offers common deployment patterns, open interfaces and cross-provider management. A federation should make multi-provider use normal, not exceptional. That would differentiate it from single-provider sovereign cloud offers that may keep customers inside one vendor’s environment.

The Data Act also intersects with industrial data. Euro-3C’s target sectors produce valuable operational data. Automotive, energy and transport firms will not share that data unless usage rights, access controls and processing locations are clear. Federation can help if it allows data to be processed near source under agreed policies. It can hurt if governance becomes unclear.

The project should therefore connect technical federation to data governance. Workload placement decisions should reflect data rights and sensitivity. Data-sharing services should include consent, contractual terms, logging and policy enforcement. Industrial customers need to know not only where compute runs, but who can use resulting data.

Energy efficiency will be judged against real deployment choices

The EU’s cloud-edge ambitions include climate-neutral and highly secure edge nodes. IPCEI-CIS also emphasises energy-efficient cloud and edge distributed data processing technologies. Euro-3C therefore has to make an energy argument, not only a sovereignty argument.

Edge computing can reduce data transmission by processing information locally. That can lower bandwidth demand and improve latency. It can also increase energy use if many distributed nodes are underutilised, poorly cooled or duplicated. The environmental case for edge depends on workload placement, utilisation, hardware efficiency, cooling, renewable energy access and lifecycle management.

A federated model could improve energy efficiency if orchestration places workloads where capacity is available and energy conditions are favourable. It could also allow local processing that avoids unnecessary data movement. AI-enabled orchestration may support this if it optimises for energy alongside latency and resilience. But energy claims need measurement.

Europe should avoid treating “edge” as automatically green. Distributed infrastructure is efficient only when designed and operated with utilisation, cooling, power sourcing and lifecycle impact in mind. Euro-3C’s reporting should include energy metrics for use cases, not only performance metrics.

The energy issue is also tied to AI. AI inference at the edge can reduce data movement, but running models across many sites can consume significant power. Model size, hardware acceleration, batching, caching and update frequency all matter. Industrial AI services will need energy-aware deployment patterns.

The Commission’s AI Continent Action Plan also says the proposed cloud and AI development act aims to at least triple EU data-centre capacity within five to seven years, prioritising sustainable data centres. That creates tension. Europe wants more compute capacity and lower environmental impact. Euro-3C can contribute if it shows how distributed compute can be used intelligently rather than simply multiplied.

Euro-3C is not big enough to solve Europe’s hyperscaler dependency

Euro-3C’s budget is €75 million. That is large for a research and pilot project, but tiny compared with the capital expenditure of global cloud and AI infrastructure leaders. The right critique is not that Euro-3C is too small to matter. The right critique is that it must not be mistaken for a full industrial answer.

Europe’s dependency on non-European cloud providers is structural. It includes infrastructure scale, developer ecosystems, managed service depth, AI tooling, enterprise contracts, cybersecurity operations, chips, storage systems and global regions. A federation of European nodes can address some sovereignty-sensitive workloads, especially in regulated sectors. It does not instantly create a full alternative to AWS, Microsoft Azure or Google Cloud.

That limitation should sharpen Euro-3C’s mission. The project should focus where European federation has a real advantage: regulated, latency-sensitive, cross-border, industrial and public-interest workloads. Trying to replicate every hyperscaler service would be wasteful. Competing where sovereignty, local presence and telecom integration matter is more credible.

The April 2026 Commission cloud procurement shows a similar realism. It did not choose a single European mega-provider. It awarded four contracts to diversify and avoid lock-in. That approach recognises Europe’s market structure. Euro-3C follows the same logic at the infrastructure layer.

The risk is political overclaiming. If Euro-3C is presented as “Europe’s answer to Big Tech,” expectations will exceed delivery. If it is presented as a test of federated infrastructure for specific high-value use cases, it can be judged fairly. The project’s strongest contribution may be to create a repeatable model that others can fund, extend and procure.

Scale still matters. If Euro-3C works, Europe will need larger deployment programmes, private investment, public procurement demand and standardisation. It will also need to connect Euro-3C with AI factories, data spaces, IPCEI-CIS, Digital Europe deployments and national cloud strategies. A pilot without scale-up money becomes a report.

The single market problem will surface in procurement

Euro-3C’s federation crosses more than 13 countries. That is one of its strengths and one of its risks. Cross-border infrastructure in Europe often runs into procurement fragmentation, national security rules, certification differences, public-sector buying habits and local market preferences.

Public procurement can make or break sovereign infrastructure. If public authorities continue buying mostly from incumbent global providers because procurement frameworks reward familiarity, service breadth and low short-term risk, Euro-3C-type services will struggle. If procurement criteria begin to measure sovereignty, interoperability, resilience and European control, demand can shift.

The Commission’s Cloud Sovereignty Framework is important here because it turns sovereignty into measurable procurement criteria. That approach could support Euro-3C by giving buyers a language for specifying requirements. A public authority might ask for a certain sovereignty assurance level, cross-provider portability, EU-law compliance, supply-chain transparency and operational resilience.

But procurement must avoid becoming protectionism without performance. Buyers still need quality, security, support, cost control and service reliability. A weak European service should not win only because it is European. The stronger standard is values-based competition: European services should meet measurable sovereignty and technical criteria.

Private-sector procurement is also relevant. Industrial buyers will use Euro-3C services if they solve business problems. They may value compliance and sovereignty, but they will compare against global platforms. Procurement teams will ask for service-level commitments, liability, integration support and price. The federation needs commercial packaging.

The single market problem is especially hard for SMEs. A small provider cannot manage different procurement processes in 20 countries. If Euro-3C creates common onboarding and procurement templates, it could lower market barriers. If every country adds its own conditions, the federation will favour large incumbents.

Regulation can support Euro-3C or slow it down

Europe has built a dense digital rulebook: GDPR, Data Act, Data Governance Act, AI Act, NIS2, Cyber Resilience Act, Digital Services Act, Digital Markets Act, sectoral cyber rules, public procurement standards and national sovereignty schemes. Some of these rules support Euro-3C by creating demand for trusted, secure, interoperable infrastructure. Others can slow deployment if obligations overlap or remain unclear.

The AI Act entered into force on 1 August 2024 and becomes fully applicable in stages, with broad application scheduled two years later and exceptions for some provisions. For Euro-3C, the AI Act matters where AI orchestration, industrial AI or public safety AI systems are involved. Providers and deployers will need clarity on roles, risk categories and documentation responsibilities.

The Cyber Resilience Act matters for products with digital elements and lifecycle security. NIS2 matters for cybersecurity risk management and incident reporting across essential and important entities. The Data Act matters for cloud switching and industrial data access. The Digital Networks Act may reshape connectivity regulation. Together, these frameworks create a compliance environment that can favour well-governed European infrastructure.

The danger is compliance drag. A federated project with many partners may spend too much energy mapping obligations and too little building usable services. This is where automation and shared assurance become strategic. Euro-3C should produce compliance evidence as part of operations, not as paperwork after deployment.

Regulation also creates a trust opportunity. European firms often complain about regulatory burden, but regulated sectors need infrastructure that understands European law by design. A platform that embeds EU compliance, data rights, security controls and sovereignty evidence can reduce customer burden. That becomes a competitive feature if executed well.

The Commission’s ongoing work on digital simplification shows awareness that overlapping rules can create uncertainty. But Euro-3C cannot wait for a perfect rulebook. It has to build in the current environment and document where rules obstruct deployment. Those lessons can inform policy better than abstract lobbying.

The 6G connection is stronger than it first appears

Euro-3C’s link to 6G may sound promotional, but there is substance behind it. 6G is expected to combine connectivity with sensing, distributed intelligence, high reliability, immersive communication and machine coordination. These capabilities will require compute and data resources close to users and devices. A pure connectivity network will not be enough.

ITU’s IMT-2030 process defines the global framework for 6G development, and ITU agreed performance requirements for 6G radio interfaces in March 2026. 3GPP’s Release 20 work is part of the transition toward 6G study and standardisation. NGMN’s 6G use-case work also points to emerging requirements for future network evolution.

Euro-3C does not write 6G standards, but it can influence what European actors want from them. If the project proves that network-aware compute federation is valuable, European operators and vendors can bring stronger requirements into standards discussions. If it fails, 6G may again be shaped around radio and vendor roadmaps rather than operator-controlled service capabilities.

The project also tests the business model for guaranteed digital services. Future networks may expose capabilities such as latency, reliability, location, quality of service, sensing or security through APIs. Those capabilities need compute platforms behind them. Euro-3C could provide a European environment for experimenting with such service exposure across multiple operators.

This matters for industrial sectors. A factory, port, energy operator or emergency service does not buy “6G” as a technology label. It buys guaranteed outcomes: response time, coverage, resilience, security, data control and service continuity. Telco-edge-cloud federation is one way to deliver those outcomes.

The timing is useful. Decisions made in the second half of the 2020s will shape 6G architecture. Euro-3C can give Europe a practical testbed before specifications and commercial deployments harden. If Europe wants 6G to support industrial sovereignty, it needs infrastructure experiments before 6G arrives, not after.

The project will test Europe’s ability to execute across institutions

Europe is good at strategies, roadmaps and regulatory frameworks. Execution is harder. Euro-3C brings together the Commission, Horizon Europe funding, telecom operators, cloud providers, industrial firms, research centres, public authorities, IPCEI-CIS links, Digital Decade targets, cloud-edge roadmaps and cybersecurity frameworks. That is impressive. It is also a coordination burden.

The execution question has several parts. Can the consortium make decisions quickly? Can technical work avoid duplication? Can use cases stay focused? Can governance remain clear? Can outputs be reused outside the consortium? Can policymakers learn from deployment rather than only celebrate launch? Can commercial actors carry work forward after public funding?

Europe’s digital sovereignty agenda often suffers from scattered initiatives. AI factories, data spaces, cloud alliances, IPCEIs, national cloud projects, telecom reforms and cybersecurity rules each have their own governance. Euro-3C’s value increases if it connects them. It decreases if it becomes another isolated acronym.

The Commission’s cloud policy page shows how many programmes already exist: Horizon Europe, Digital Europe, Connecting Europe Facility and broader industrial alliance work. Coordination is necessary because cloud-edge infrastructure is not one project. It is a stack of funding, regulation, standards, procurement, deployment and adoption.

Euro-3C should therefore be assessed on integration. Does it feed lessons into the Digital Networks Act debate? Does it reuse IPCEI-CIS components? Does it connect to open-source 3C building blocks? Does it support AI factory deployment needs? Does it inform the Cloud Sovereignty Framework? Does it help public authorities write better tenders? These are more important than producing another polished final report.

Execution also requires political patience. Infrastructure markets do not change in one funding cycle. The project may show results that require follow-on funding or procurement in 2027 and beyond. Europe’s problem has often been discontinuity: a pilot ends, a new programme starts, and accumulated knowledge dissipates. Euro-3C needs an institutional home after the pilot.

The risk of fragmentation remains inside the federation

Federation is meant to solve fragmentation, but it can also hide it. A network of partners may look unified in a press release while remaining fragmented in practice. Customers will notice quickly if services differ too much by country, provider or sector.

Fragmentation can appear in APIs, service catalogues, pricing, legal terms, support models, certifications, identity systems, deployment workflows and performance guarantees. It can also appear in governance. If each participant can veto changes or insist on local exceptions, the federation may become slow and inconsistent.

Euro-3C’s architecture should distinguish between mandatory common layers and optional local layers. Mandatory layers might include identity, trust, security baselines, workload descriptors, observability, service discovery and compliance evidence. Optional layers might include specialised managed services, local integrations and sector-specific tools. The federation needs enough sameness to be usable and enough diversity to attract providers.

The project also needs customer-facing clarity. A customer should not need to understand the entire consortium structure to buy a service. It should know who contracts, who supports, who bills, who is liable and who operates the service. Multi-party delivery is acceptable only if accountability is clear.

There is a danger that federation becomes a compromise word used to avoid hard choices. Some providers may prefer minimum interoperability. Some policymakers may prefer maximum inclusion. Some customers may prefer a single accountable supplier. Euro-3C must prove that federation is not just politically convenient, but operationally superior for selected workloads.

Competition policy will shape the market response

European digital infrastructure policy has to balance sovereignty, competition and openness. Euro-3C involves many major telecom and technology actors. It is publicly funded. It aims to create a shared infrastructure model. That raises competition questions even when the goal is legitimate.

A federation can increase competition by lowering switching costs and allowing smaller providers to join a broader market. It can also reduce competition if incumbents control access, set rules that disadvantage outsiders or use public funding to reinforce existing positions. The difference lies in governance.

Open APIs, transparent certification, fair onboarding, published technical requirements and non-discriminatory access are essential. SMEs should not need deep political connections to participate. Cloud providers outside the original consortium should be able to test integration if they meet requirements. Customers should be able to compare services.

The Commission’s broader digital policy often stresses fair competition and open markets. The European Alliance for Industrial Data, Edge and Cloud is open to EU-established businesses, with additional proof required for entities controlled by third-country actors to ensure compliance with EU data protection. That approach reflects Europe’s attempt to protect sovereignty without simply closing markets.

Euro-3C can support competition if it becomes a common layer rather than a club. It should make it easier for European providers to offer services across borders. It should not force all innovation through a few large operators. The test is whether the federation creates more routes to market or fewer.

Competition with global hyperscalers is another layer. Europe should not pretend that customers will abandon global platforms for all workloads. A more realistic approach is multi-cloud and workload segmentation. Sensitive, latency-critical or public-interest workloads may move to sovereign federated infrastructure. Less sensitive workloads may remain on global clouds. The federation should support interoperability with the wider cloud market where appropriate, while preserving sovereignty controls for workloads that need them.

The economic impact depends on repeatable services

Euro-3C’s economic impact will not come from the €75 million grant itself. It will come from services, procurement, private investment, industrial productivity, SME participation and reduced dependency risk. That impact is uncertain because it depends on what the project produces.

Repeatable services are the key. A public safety data-sharing service that can be adapted across countries is valuable. An industrial edge AI deployment pattern that can be reused in factories is valuable. A transport analytics model that can operate across different operators is valuable. A secure workload placement policy engine that many providers can implement is valuable. A one-off demo is not.

The business impact can appear in several ways. Telecom operators may gain new revenue from edge and managed services. Cloud providers may gain access to distributed infrastructure and public-sector demand. SMEs may sell specialised applications into a European marketplace. Industrial companies may reduce latency, improve resilience or meet compliance requirements. Public authorities may get better sovereign procurement options.

But these outcomes require commercial packaging. Customers need service catalogues, prices, contracts and support. Euro-3C should not wait until the end of the project to think about go-to-market models. Technical architecture without a commercial path becomes a publicly funded prototype.

The project could also influence investment. If Euro-3C proves demand, investors may back European edge-cloud software, orchestration tools, security platforms, sector applications and infrastructure providers. If it shows only subsidised interest, investment will remain cautious.

Economic impact also includes risk reduction. Dependence on external providers has a cost even when services work well. Geopolitical tension, legal conflicts, supply-chain disruption, export controls and service discontinuity can affect critical operations. A credible European federation gives buyers optionality. Optionality has economic value.

The public-sector cloud procurement signal is getting stronger

The Commission’s April 2026 sovereign cloud tender is one of the clearest signs that Europe is turning sovereignty into purchasing behaviour. The Commission awarded four contracts to diversify providers and avoid lock-in, and it assessed providers through the Cloud Sovereignty Framework. Reuters reported the tender value as €180 million over six years and described it as part of a push to reduce dependence on non-European technology.

This procurement signal matters for Euro-3C because public-sector demand can anchor markets that private buyers consider risky. If governments and EU institutions buy sovereign cloud, edge and connectivity services, providers have reason to invest. If public bodies praise sovereignty but continue to buy mainly non-European platforms for sensitive workloads, the market signal is weak.

The Commission’s framework also introduces a vocabulary that Euro-3C can reuse. Sovereignty levels, supply-chain transparency, legal control, operational control, technological openness and compliance evidence can become procurement criteria for federated telco-edge-cloud services. That would help buyers compare offers and reduce vague claims.

Public procurement can also support standardisation. If tenders require open APIs, portability, security certification and federation compatibility, providers will implement them. If tenders accept proprietary lock-in, federation will remain optional. Procurement is where Europe’s sovereignty agenda becomes real or decorative.

Euro-3C should therefore engage with procurement officials early. Technical teams often underestimate procurement timelines and risk models. Public buyers need requirements they can include in tenders, not architecture diagrams alone. Model clauses, assurance templates and certification mappings could be among the project’s most useful outputs.

Europe’s cloud sovereignty debate is becoming more contested

Euro-3C arrives amid a sharper political debate about Europe’s dependence on U.S. and Chinese technology. Reuters reported in May 2026 that European leaders were divided over how aggressively to challenge U.S. Big Tech dominance, including debates over satellite spectrum and cloud service tenders. The same report said the expected Cloud and AI Development Act aimed to reduce reliance on Amazon, Google and Microsoft, and cited concerns about a large investment gap.

This debate will affect Euro-3C. Some policymakers and industry leaders want stronger “Buy European” rules for strategic digital infrastructure. Others worry that excluding non-European firms could reduce competition, raise costs or slow innovation. Euro-3C is positioned in the middle. It promotes European control and federation, but it exists within a global technology ecosystem.

The Commission’s sovereign cloud tender shows that nuance. Most selected providers are strongly European, but one Proximus-led partnership uses S3NS, a Thales-Google Cloud joint venture, under EU-operated conditions. That choice reflects a practical question: can sovereignty be achieved through operational and legal controls even when some underlying technology has non-European origins? Different stakeholders will answer differently.

Euro-3C should avoid ideological simplification. Full-stack European control may be desirable for the most sensitive workloads, but not always available. Mixed models may be acceptable for lower-risk services if controls are strong. The right approach is workload-based sovereignty: define the required control level based on risk.

Digital sovereignty is not a binary condition. It is a set of control requirements that vary by workload, sector and threat model. Euro-3C can make that approach practical if it supports different assurance levels and makes dependencies transparent.

The debate will remain political because infrastructure is power. Cloud, AI, telecom and data systems now shape economic competitiveness, state capacity and security. Euro-3C is small compared with the global power struggle, but it is part of Europe’s attempt to regain agency.

Technical governance needs to be as visible as political governance

Public announcements usually name budgets, partners and strategic goals. Technical governance is less visible, but it will decide whether Euro-3C works. A federated infrastructure needs architecture governance, release management, security governance, certification, dispute resolution, API lifecycle rules, data governance and operational governance.

Architecture governance decides what is common and what is local. Release management prevents incompatible versions from breaking federation. Security governance sets baselines and response procedures. Certification verifies that participants meet requirements. Dispute resolution handles failures, liability and policy conflicts. API lifecycle rules prevent fragmentation. Data governance defines rights and restrictions. Operational governance decides who acts during incidents.

These functions are not glamorous. They are the difference between a federation and a collection of projects. Euro-3C’s governance model should be treated as a technical deliverable, not an administrative appendix.

Transparency will matter. External providers and customers should be able to understand how decisions are made. If the federation is governed only by consortium insiders, adoption will be limited. If governance is open enough to attract new participants while strict enough to protect trust, the model can grow.

Technical governance also needs alignment with standards bodies and EU frameworks. ETSI, cloud alliance roadmaps, IPCEI-CIS reference architectures, Open Internet Stack components and procurement frameworks should not evolve separately. Euro-3C can become a convergence point if it produces practical mappings.

The project should also define metrics for governance success. How long does onboarding take? How often do interoperability tests pass? How quickly are vulnerabilities patched? How are API changes managed? How many external developers use the platform? How many components are reused beyond the consortium? These metrics reveal whether governance is enabling or blocking.

AI-enabled orchestration could become the hidden control plane

Telefónica says Euro-3C integrates AI-enabled orchestration capabilities. This could become one of the most important parts of the project. Orchestration decides where workloads run, how resources are allocated, how failures are handled, how policies are applied and how performance is balanced against cost and energy.

In a federated telco-edge-cloud system, orchestration is difficult because resources are distributed across providers, countries and network domains. Manual placement will not scale. AI-assisted systems may help predict demand, optimise latency, reduce energy use, detect anomalies and automate recovery.

But orchestration is also a control plane. Whoever controls orchestration influences service behaviour. In sovereign infrastructure, that creates accountability questions. Customers need to know which policies guide orchestration. Regulators may need audit trails. Operators need override mechanisms. Security teams need assurance that AI decisions do not violate data location, access or resilience rules.

AI orchestration should be policy-bound, auditable and explainable enough for critical sectors. It should not become a black box that moves workloads in ways customers cannot verify. The platform should separate optimisation from authorisation: AI can recommend or execute within allowed policies, but policy rules must be explicit.

The orchestration layer also affects competition. If one vendor controls orchestration, others may become dependent. Open interfaces and modular design can reduce that risk. A federation should avoid replacing hyperscaler lock-in with orchestrator lock-in.

Euro-3C can make a major contribution if it defines practical patterns for sovereign AI orchestration across edge and cloud. That includes policy languages, audit logs, simulation tools, failover models, energy-aware placement and compliance checks. These are the mechanics of future infrastructure.

The role of SMEs will show whether the model is open

EU announcements often mention SMEs, and Euro-3C is no exception. Telefónica lists SMEs among the consortium categories and names several specialised companies. The Open Internet Stack call also explicitly targets European open-source communities, SMEs, research institutes and individual developers for third-party projects, with typical funding ranges of €50,000 to €150,000.

SME participation is important because Europe’s digital strength is not only in large incumbents. Many specialised software, cybersecurity, industrial AI, data, orchestration and edge applications come from smaller firms. A federated infrastructure could give them access to cross-border markets they could not reach alone.

But SMEs face barriers. Certification can be expensive. Procurement can be slow. Consortium governance can be hard to enter. Documentation can be incomplete. Large partners can dominate roadmaps. If Euro-3C wants SME participation to be more than decorative, it needs low-friction onboarding and clear commercial routes.

A strong SME model would include sandbox access, published APIs, open-source components, testing credits, lightweight certification paths, marketplace visibility and standard contracts. It would also include support for localisation and compliance documentation, because SMEs often lack legal resources.

The number of SMEs in the consortium matters less than whether non-consortium SMEs can build on the platform. That is the real openness test. A publicly funded federation should create market access beyond its founding members.

SMEs can also help avoid over-centralisation. If the platform supports specialised services from many providers, customers get diversity and innovation. If it becomes a few large providers reselling generic services, the federation will not fulfil its promise.

The public narrative should stop treating sovereignty as isolation

Euro-3C’s political language includes reducing reliance on third-country providers. That is a legitimate goal. But reducing reliance is not the same as isolating Europe from global technology. Europe’s economy depends on international supply chains, open standards, global software communities and cross-border digital services. The practical aim should be resilience, control and choice.

A sovereign system can still interoperate with global systems. It can use open-source components with global contributors. It can allow non-European technology under specific controls for lower-risk workloads. It can support export markets. What it cannot do is leave critical operations dependent on opaque control chains that Europe cannot govern.

Euro-3C’s federated model fits this more mature sovereignty concept. It does not propose a sealed European cloud island. It proposes a European-controlled infrastructure fabric that can support sensitive and strategic services. That fabric should be open where openness strengthens resilience and controlled where control is necessary.

Sovereignty should mean the ability to decide, verify and recover. It should not mean rejecting every non-European component or duplicating every technology at any cost. Workload risk should drive control requirements.

This distinction matters for business credibility. Industrial firms do not want ideology. They want reliable infrastructure, regulatory confidence, cost control, security and innovation. Public authorities want control and accountability. Developers want usable platforms. Euro-3C must serve all of them.

The public narrative should also acknowledge trade-offs. Higher sovereignty assurance may cost more. Full supply-chain control may limit service options. Open federation may move slower than a single provider. Edge deployment may increase operational complexity. Honest trade-offs build trust.

Euro-3C’s success metrics need to be public

A project like Euro-3C needs public success metrics because its goals are strategic and publicly funded. Without metrics, success can be claimed through launch events, partner counts and broad language. That would not be enough.

Technical metrics should include node availability, latency performance, failover times, workload portability, cross-provider deployment success, security incident response, energy use, API conformance and orchestration accuracy. Governance metrics should include onboarding time, certification results, vulnerability remediation time, documentation completeness and external participation.

Market metrics should include number of pilot customers, sector adoption, services converted from use cases into offerings, SME participation, procurement references, private investment and follow-on deployments. Policy metrics should include contributions to standards, procurement frameworks, Digital Networks Act discussions, Cloud Sovereignty Framework updates and Open Internet Stack integration.

Practical metrics that would make Euro-3C credible

The point of these metrics is not to punish the project for early-stage complexity. It is to make learning visible. Euro-3C should be judged by evidence of repeatability, not by the scale of its launch announcement.

Public metrics would also help external stakeholders. Member States could decide where to invest. Public buyers could write better tenders. SMEs could decide whether to build on the platform. Standards bodies could use real deployment data. Investors could assess market readiness.

The Commission and consortium do not need to publish sensitive operational details. But they should publish enough to show whether federation works. Strategic infrastructure requires public trust.

The project could reshape European telecom policy if it works

If Euro-3C proves that multi-operator, multi-vendor, cross-border edge-cloud services can work, it will strengthen the case for telecom policy reform. It would show that telecom networks are not only connectivity utilities but part of Europe’s cloud and AI infrastructure.

That could affect debates around the Digital Networks Act, spectrum policy, cross-border consolidation, network investment, service-level guarantees and network APIs. It could also support a new view of telecom operators as infrastructure partners for AI, industry and public services.

The risk is that operators use Euro-3C rhetorically without changing their own product models. Europe does not need another argument that telecoms deserve support. It needs evidence that telecom assets can create new services and industrial value. Euro-3C can provide that evidence only if operators expose capabilities in usable, standardised ways.

The project may also influence how Europe thinks about network APIs. Global initiatives have tried to expose telecom capabilities to developers. The problem has often been fragmentation and unclear demand. A federated European edge-cloud platform could give network APIs a more concrete environment: APIs tied to workloads, edge placement, security, identity and sector use cases.

Telecom policy will become more convincing when it is connected to services customers can buy. Euro-3C can help make that connection.

If it fails, the lesson may be that telecom-cloud convergence remains too complex under current market structures. That would also be valuable, though politically uncomfortable. It would suggest Europe needs stronger consolidation, simpler regulation, more focused funding or different commercial models.

Europe’s strategic autonomy depends on boring infrastructure layers

Digital sovereignty is often discussed through high-profile topics: AI models, chips, cloud contracts, cybersecurity incidents and platform regulation. Euro-3C points to less visible layers: orchestration, identity, edge nodes, APIs, network integration, procurement criteria, compliance evidence and service management.

These layers are boring only to outsiders. They determine who can deploy services, who can move workloads, who can audit systems, who can respond to failures and who can extract value from data. Strategic autonomy lives in control planes, not press releases.

Europe’s challenge is that many of these control planes are currently provided by global platforms. Cloud consoles, identity systems, deployment pipelines, observability tools, AI platforms and managed databases shape how organisations operate. Even when data is stored locally, operational control may remain elsewhere.

Euro-3C’s contribution is to build and test European control planes for distributed infrastructure. That includes technical control, governance control and commercial control. The project will not replace global platforms across the economy, but it can create alternatives for sensitive and high-value workloads.

This is why the project should not be judged only by node count. Nodes are necessary, but control mechanisms are more important. A thousand poorly governed nodes would not create sovereignty. A smaller number of well-governed, interoperable nodes could create a template for scale.

Europe’s strategic autonomy also depends on skills. Operating a federated edge-cloud infrastructure requires cloud engineers, telecom specialists, cybersecurity experts, data governance professionals, AI operations teams and sector integrators. Euro-3C should therefore support training and operational knowledge transfer, not only technology deployment.

The likely winners if Euro-3C succeeds

If Euro-3C succeeds, the first winners will be regulated and infrastructure-heavy sectors that need low-latency, secure and sovereign digital services. Public safety agencies, energy operators, transport networks, automotive ecosystems and industrial firms could gain new deployment options.

European telecom operators could win if they turn network assets into service platforms. Cloud providers could win if federation expands their reach and makes sovereignty a measurable market advantage. SMEs could win if open interfaces give them access to cross-border customers. Research centres could win if their architectures become deployed infrastructure rather than papers.

Public authorities could win through better procurement choices. A government agency that needs secure cloud-edge services would have more than a binary choice between global hyperscaler convenience and bespoke national systems. Euro-3C could support a middle path: European, federated, measurable, interoperable.

European citizens could benefit indirectly if critical services become more resilient and if public data is handled under stronger control. But the citizen benefit will be indirect unless the project improves services people use: emergency response, transport reliability, energy resilience, safer mobility or digital public services.

The broader European technology ecosystem could gain confidence. Success would show that Europe can execute cooperative infrastructure across countries and sectors. That matters because Europe’s problem is often not lack of talent, but difficulty scaling collective action.

The biggest winner would be the idea that Europe can build shared infrastructure without needing a single dominant platform company. That idea has been asserted many times. Euro-3C gives it a serious test.

The likely losers if Euro-3C fails

If Euro-3C fails, the immediate loss will be credibility. European digital sovereignty has already produced many acronyms. Another project that launches strongly but fails to produce reusable infrastructure would feed cynicism among industry and developers.

Telecom operators would lose a chance to prove relevance beyond connectivity. European cloud providers would lose a possible federation route to scale. SMEs would lose a potential cross-border platform. Public authorities would remain more dependent on existing global providers or fragmented national solutions.

The policy cost would also be high. The Digital Networks Act and broader cloud-edge strategy rely partly on the idea that Europe can build more coherent digital infrastructure. If Euro-3C cannot demonstrate practical federation even with public funding and a strong consortium, policymakers will need to ask whether the model is too complex.

Failure could happen in several ways. The project might produce demos but no reusable services. Governance might become too slow. Large partners might protect their own interests. APIs might remain closed or poorly documented. Use cases might lack commercial buyers. Security and compliance might become too burdensome. Funding might end before a market structure exists.

The worst failure would be quiet success language masking operational weakness. That would waste learning. A more honest failure — one that documents what did not work — would still help Europe. The only unacceptable outcome is a polished story with little evidence.

The next 24 months should show whether the model is real

Euro-3C was announced in March 2026. The next phase should reveal whether it is moving from launch to substance. Early signs to watch include technical architecture publications, use-case definitions, open-source releases, onboarding procedures, partner integration reports, interoperability tests, procurement engagement and public metrics.

The project should also show how it relates to parallel EU initiatives. Does it use IPCEI-CIS outputs? Does it align with the Telco Cloud Reference Architecture? Does it feed the Open Internet Stack? Does it connect with AI factories? Does it provide input to the Cloud Sovereignty Framework? Does it support Digital Networks Act implementation debates?

A credible timeline would include early integration milestones, then use-case pilots, then service packaging, then external onboarding. If the first visible outputs are only conference panels and promotional videos, skepticism will grow. If the project publishes practical artefacts, confidence will rise.

Stakeholders should also watch for procurement signals. Public-sector buyers may begin asking for federated edge-cloud capabilities. Industrial firms may join pilots. Member States may align national cloud or edge investments. Standards bodies may pick up Euro-3C interfaces. These are signs that the project is becoming more than its founding consortium.

The decisive question is whether Euro-3C produces infrastructure that others can use. Not admire. Not cite. Use.

Euro-3C’s best case is a new European infrastructure template

The best-case scenario is not that Euro-3C becomes a single giant European cloud. That is not its design. The best case is that it creates a template for federated infrastructure: common trust, common APIs, common orchestration patterns, common procurement language, open components, sector-ready services and measurable sovereignty.

Such a template could scale through public procurement, national deployments, private investment, SME applications, industrial partnerships and standards. It could connect AI factories to edge deployment. It could give telecom operators a service role in 6G. It could give European cloud providers broader reach. It could give public authorities credible alternatives for sensitive workloads.

The template would need to be practical. It should tell a provider how to join, a developer how to deploy, a buyer how to procure, a regulator how to verify, an operator how to interconnect and an industrial customer how to measure value. This is the difference between an initiative and infrastructure.

Euro-3C’s long-term value may therefore be less about the first 70-plus nodes and more about the rules, software and trust model that connect them. If those outputs survive the project, Euro-3C will matter. If they do not, the nodes will remain a temporary pilot.

Europe does not lack ambition. It lacks enough operational proof that ambition can become market infrastructure. Euro-3C is important because it turns the sovereignty debate into an engineering, procurement and governance test. That is exactly where the debate needed to go.

The strategic reading is cautious optimism

Euro-3C deserves cautious optimism. The project is well timed, strategically coherent and connected to real EU priorities. It has a meaningful budget for a pilot, a broad consortium, production-environment ambitions, sector use cases and links to Digital Decade, Digital Networks Act, IPCEI-CIS, cloud-edge policy and AI infrastructure.

It also faces serious constraints. The budget is small compared with global cloud investment. Federation is difficult. Developer experience could be weak. Governance could become heavy. Use cases could remain decorative. Commercial models could be unclear. Public procurement may move slowly. Large incumbents may dominate. Open-source outputs may be less reusable than promised.

The right stance is neither hype nor dismissal. Euro-3C is not Europe’s cloud independence delivered. It is not a symbolic press release either. It is the first serious test of whether Europe can turn distributed telecom, edge, cloud and AI assets into a sovereign service fabric.

If it works, Europe gains a model for infrastructure cooperation that fits its market structure and political values. If it fails honestly, Europe gains evidence about what must change. If it fails quietly, Europe loses time it cannot afford.

Questions readers are asking about Euro-3C

Author:
Jan Bielik
CEO & Founder of Webiano Digital & Marketing Agency

This article is an original analysis supported by the sources cited below

Commission announces €75 million EURO-3C Project to build a federated Telco-Edge-Cloud infrastructure for digital sovereignty
European Commission announcement of Euro-3C, including the budget, Horizon Europe support, Mobile World Congress 2026 context and the project’s sovereignty framing.

Europe takes a decisive step towards digital sovereignty with the launch of EURO-3C
Telefónica’s launch release describing the consortium, more than 70 nodes, more than 13 countries, sector use cases and named beneficiaries.

EURO-3C: what the launch means for the IPCEI-CIS community
CISERO analysis connecting Euro-3C with IPCEI-CIS, public safety authorities, the 3C pilot concept and the European cloud-edge continuum.

Cloud computing
European Commission policy page covering cloud and edge targets, Digital Decade goals, business cloud adoption data and edge-node deployment progress.

Digital Decade policy programme
European Commission page explaining the Digital Decade governance framework, 2030 objectives and secure sustainable digital infrastructure pillar.

Proposal for a Regulation for the Digital Networks Act
European Commission proposal page for the Digital Networks Act, including its role in modernising connectivity rules and addressing fragmentation and resilience.

European Alliance for Industrial Data, Edge and Cloud
European Commission page on the alliance, its role in next-generation cloud and edge technologies, investment roadmaps, procurement recommendations and governance issues.

Open Internet Stack: development of technological commons open-source 3C building blocks
CORDIS programme page describing open-source 3C building blocks, trust technologies, network technologies, decentralised technologies and cooperation with the 3C pilot.

Cloud IPCEI
European Commission competition policy page on IPCEI-CIS, including the multi-provider cloud-to-edge continuum, public funding and expected private investment.

IPCEI on Next-Generation Cloud Infrastructure and Services to boost Europe’s Digital Decade
European Commission news article explaining IPCEI-CIS and its role in interoperable European data processing technologies and cloud-edge development.

Commission advances cloud sovereignty through strategic procurement
European Commission announcement of its 2026 sovereign cloud procurement, awarded providers and Cloud Sovereignty Framework criteria.

EU Commission awards 180 million euro cloud contract to four European providers
Reuters report on the European Commission’s sovereign cloud contract, provider selection and wider digital sovereignty context.

AI Factories
European Commission page explaining AI factories, EuroHPC links, selected locations and the role of AI infrastructure for startups, industry and research.

AI continent
European Commission page on the AI Continent Action Plan, including investment figures for AI development, AI gigafactories and data-centre capacity ambitions.

AI Act
European Commission page on the EU AI Act, its entry into force and application timeline for AI regulation.

Data Act explained
European Commission explainer on the Data Act, industrial data access, data-use rights and the EU data economy.

Cybersecurity policies
European Commission cybersecurity policy page covering the Cyber Resilience Act and lifecycle security requirements for products with digital elements.

ISG MEC
ETSI page defining Multi-access Edge Computing as cloud-computing capability and IT service environment at the network edge.

Rel-20 planning and progress in TSG SA
3GPP update on Release 20 planning and 6G preparation work across radio, architecture and core network requirements.

IMT-2030: technical requirements for the 6G future
ITU article on agreed draft IMT-2030 technical performance requirements for 6G radio interfaces.

6G use cases and analysis
NGMN publication page on future 6G use cases and the requirements they imply for next-generation network development.

Thematic roadmap on open source and inputs on common trust principles
European Commission page on the Cloud-Edge Industrial Working Group’s open-source roadmap and common trust principles for cloud, edge and IoT.