Summary The EuroCloud Federation would be legally established automatically upon the entry into force of the proposed Cloud and AI Development Act (CADA), but it would not become operational until the European Commission builds a dedicated platform and adopts specific implementing acts. As a proposal, CADA has no fixed calendar start date; if adopted, the Regulation would enter into force 20 days after publication and apply one year later. However, the Federation's actual functionality depends on secondary legislation and technical development, meaning a gap of several months (or potentially longer) would exist between the Regulation's application date and the Federation's ability to facilitate service sharing.

Detail

The operational timeline of the EuroCloud Federation is a two-stage process defined by the distinction between legal existence and functional capability within the proposed Cloud and AI Development Act (CADA), COM(2026) 502 final.

1. Legal Establishment: Automatic upon Entry into Force

Under Article 34(1) of the proposal, the European public sector cloud federation is "hereby established." This phrasing indicates that the Federation's legal existence is not contingent on a separate decision or a future date; it is created directly by the Regulation itself.

If CADA is adopted, the timeline for this legal establishment follows Article 48:

  • Entry into force: The Regulation would enter into force on the 20th day following its publication in the Official Journal of the European Union.
  • Application: The Regulation would apply from one year after that entry into force.

Consequently, the Federation would legally exist as soon as the Regulation enters into force, but it would remain dormant until the application date and the completion of necessary preparatory measures.

2. Operational Launch: Dependent on Platform and Implementing Acts

Legal existence does not equate to operational readiness. The Federation cannot facilitate the sharing of data centre or cloud computing services until two critical conditions are met, as outlined in Article 34(3) and Article 34(4):

  • The Platform (Article 34(3)): The Commission is mandated to "establish a platform for the EuroCloud Federation." This platform is the technical backbone required for the Federation to function. It must provide:

    • A catalogue providing information on available public sector data centre services and cloud computing services.
    • A service platform for the exchange and orchestration of computing, storage, and network resources. Without this infrastructure, Member States and Union entities cannot discover available capacity or execute the sharing of resources.

  • Implementing Acts (Article 34(4)): The Commission is empowered to adopt implementing acts to specify:

    • The procedure to participate in the EuroCloud Federation.
    • Templates concerning the content and details of the request for participation. These acts are essential to define the administrative pathway for Union entities and public sector bodies to formally join the Federation. Until these acts are adopted, there is no standardized mechanism for membership requests.

3. The Timeline Gap

Because the platform development and the adoption of implementing acts are administrative processes that occur after the Regulation enters into force, there is no fixed "launch day" in the text of CADA. The operational start date would be determined by the Commission's ability to:

  1. Procure and develop the secure, interoperable platform.
  2. Draft, consult on, and adopt the necessary implementing acts via the examination procedure (Article 46).
  3. Ensure the platform is ready for the voluntary participation of Member States.

While the Regulation would apply one year after entry into force, the Federation's operational start would likely occur after this date, once the platform is live and the procedural templates are available.

4. Voluntary Nature and Purpose

The Federation is designed as a voluntary mechanism. Article 34(1) states it is "open for the participation of Union entities and public sector bodies on a voluntary basis." Entities may request to join once the framework is operational. The core purpose, defined in Article 34(2), is to "facilitate the sharing of public sector data centre services and cloud computing services" under the conditions set out in Articles 35 and 36. This sharing is intended to optimize the use of idle capacity and improve resource efficiency across the EU public sector.

What this means for you

For public-sector IT directors, procurement officers, and national cloud strategists, the distinction between legal establishment and operational launch is critical for planning.

  • No Immediate Action Required: You cannot currently apply to join or contract with the Federation, as it does not yet exist operationally. Even after CADA is adopted, you must wait for the Commission to publish the implementing acts and launch the platform.
  • Prepare Your Inventory: The Federation relies on members sharing capacity they own. Begin auditing your national or institutional data centre and cloud infrastructure to identify "idle capacity" that could be shared. Article 35(1) specifies that a sharing entity must own the hardware (directly or through a controlled intermediate entity) to share services.
  • Monitor Secondary Legislation: Watch for the Commission's adoption of the implementing acts under Article 34(4). These documents will provide the specific templates and procedural steps for joining. Until they are published, no formal application process exists.
  • Budget for Fees: While the goal is efficiency, Article 36 establishes that the Commission will levy fees on members to cover the costs of administering the Federation and maintaining the platform. These fees are intended to be cost-recovery based, but you should anticipate administrative costs in your long-term IT budgets.
  • Technical Readiness: The platform will require technical integration for the "exchange and orchestration" of resources. Assess your current IT architecture's compatibility with potential federation standards to ensure you can interconnect efficiently once the platform launches.

Common misconceptions

"The EuroCloud Federation starts operating the day CADA is adopted." Reality: No. Adoption triggers the legislative process, but the Regulation only enters into force 20 days after publication and applies one year later. Even then, the Federation remains non-operational until the Commission builds the platform and adopts implementing acts.

"Any cloud provider can join the EuroCloud Federation." Reality: No. Article 34(1) explicitly limits participation to "Union entities and public sector bodies." Private cloud providers cannot join the Federation directly. They may, however, provide services to public sector bodies that are members, provided those services meet the relevant sovereignty and security requirements under CADA.

"Joining the Federation is mandatory for all public sector bodies." Reality: No. Participation is explicitly voluntary. Article 34(1) states the Federation is open for participation "on a voluntary basis." Public sector bodies may request to join, but they are not compelled to do so.

"The Federation will replace existing national cloud strategies." Reality: No. The Federation is a complementary mechanism for sharing capacity. It does not replace national strategies, which are required under Article 7 to be established within one year of CADA's entry into force.

Related

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