Summary As proposed in the Cloud and AI Development Act (CADA), the EuroCloud service platform must technically support two core functions: a catalogue of available public sector data centre and cloud services, and a service platform for the exchange and orchestration of computing, storage, and network resources. While Article 34(3) defines these functional mandates, the specific technical specifications—including interoperability protocols with EU building blocks like Simpl and common European data spaces—are not yet fixed in the text. Instead, the Commission is empowered to define these details through implementing acts under Article 34(4).

Detail

Article 34 of the CADA proposal (COM(2026) 502 final) establishes the European public sector cloud federation (the "EuroCloud Federation"). This initiative aims to facilitate the sharing of public sector data centre services and cloud computing services between Union entities and public sector bodies on a voluntary basis. The technological backbone of this federation is the EuroCloud service platform, which the Commission is explicitly mandated to establish.

Core Functional Mandates (Article 34(3))

The legislative text provides a clear, non-exhaustive list of the minimum technological capabilities the platform must support. Under Article 34(3), the Commission shall establish a platform providing at least:

  1. A Catalogue: As specified in Article 34(3)(a), the platform must provide "a catalogue providing information on available public sector data centre services and cloud computing services." This component serves as the discovery layer, ensuring transparency and allowing potential "using entities" to identify surplus capacity or specific services offered by "sharing entities" across the Union.
  2. A Service Platform for Exchange and Orchestration: Crucially, Article 34(3)(b) mandates that the platform provide "a service platform for the exchange and orchestration of computing, storage and network resources and services."

The term "orchestration" in this context implies a sophisticated technological capability beyond simple listing. It requires the platform to manage the dynamic provisioning, lifecycle management, and interconnection of heterogeneous resources. The platform must enable a sharing entity to allocate specific computing, storage, or network capacity to a using entity seamlessly. This necessitates robust Application Programming Interfaces (APIs), standardized metadata schemas for resource description, and secure identity management protocols to handle cross-border service instantiation and data flows.

Delegated Technical Specifications and Interoperability

A critical aspect of the CADA proposal is that while the functional requirements are set in the Regulation, the technical specifications are deferred to secondary legislation. Article 34(4) empowers the Commission to adopt implementing acts to "specify the procedure to participate in the EuroCloud Federation and template concerning the content and other details of the request for participation."

Although Article 34(4) explicitly mentions participation procedures, the broader legislative context and the Digital Dimensions section of the accompanying Legislative Financial Statement clarify the interoperability expectations. The platform is designed to align with existing EU digital infrastructure initiatives. Specifically, the proposal anticipates that the platform will interoperate with:

  • Simpl (Simplified Interconnection of Public Infrastructures): A key EU building block for public sector connectivity.
  • Common European Data Spaces: Ensuring that shared cloud resources can integrate into broader data ecosystems without creating new silos.

The technology stack must therefore be flexible enough to adopt the technical standards, protocols, and data models defined under these frameworks once they are finalized or updated. The Commission's implementing acts will likely specify the exact API standards, data formats, and security protocols required to ensure this interoperability.

Operational and Security Requirements

The platform's technology must also support the legal and operational constraints of the federation as defined in Article 35.

  • Cost Recovery Mechanisms: Article 35(5) states that fees charged by a sharing entity must be "limited to the costs that the sharing entity incurs" and must not constitute a pecuniary interest. Technically, this requires the platform to support granular metering and billing systems capable of tracking resource consumption (compute hours, storage volume, network bandwidth) with high precision to generate accurate cost reports.
  • Sovereignty and Security: The platform must enforce the strict access controls required for sovereign cloud services. This includes integrating with the Union assurance levels (Article 16) to ensure that only services meeting specific security criteria are listed or exchanged. The platform must support identity verification, access logging, and potentially the technical isolation of resources to prevent unauthorized access or data leakage, ensuring compliance with the "no consideration" principle of public-sector cooperation.

What this means for you

For CTOs, cloud architects, and public sector IT managers, the CADA proposal signals a shift from isolated national cloud deployments to a federated, interoperable architecture.

  • Prepare for Standardized Orchestration: If your organization intends to join the EuroCloud Federation as a sharing entity, your internal resource management systems must be capable of exposing computing, storage, and network resources via standardized interfaces. You should begin abstracting your underlying infrastructure to allow for dynamic allocation by a central platform.
  • Monitor Implementing Acts: The specific technical protocols (e.g., specific API versions, data schemas for the catalogue) are not yet in force. Architects must monitor the Commission's upcoming implementing acts under Article 34(4) for the precise technical requirements that will govern interoperability with Simpl and data spaces.
  • Implement Granular Metering: To comply with the cost-recovery-only model, your systems must be able to track resource usage at a detailed level. This is essential for generating the accurate cost reports required to justify fees under Article 35(5) without violating public procurement rules.
  • Align with Sovereignty Levels: Ensure your technical architecture can support the verification of Union assurance levels. This may involve integrating with national competent authorities' systems to prove that your shared resources meet the necessary security and sovereignty criteria before being listed on the platform.

Common misconceptions

"The EuroCloud platform is a new public cloud provider."

  • Reality: The platform is not a cloud provider itself. It is a coordination and orchestration layer. It does not host data or run workloads directly. Instead, it facilitates the connection between existing public sector entities that share their own capacities. The actual infrastructure remains under the control of the national or Union "sharing entity."

"The technical specifications are already fully defined in CADA."

  • Reality: Article 34(3) sets high-level functional requirements (catalogue and orchestration). The detailed technical specifications, including specific interoperability protocols with Simpl and data spaces, are to be defined in implementing acts by the Commission. The Regulation provides the mandate, but the technical blueprint is yet to be finalized.

"The platform will replace national cloud strategies."

  • Reality: The EuroCloud Federation is designed to complement national strategies. It provides a mechanism for cross-border sharing of idle or surplus capacity to enhance efficiency and resilience. It does not mandate a single centralized European cloud or force Member States to abandon their national infrastructure.

Related

This is general information about a draft EU regulation, not legal advice.