Summary As proposed in the Cloud and AI Development Act (CADA), the initial establishment costs of the EuroCloud Federation may be borne by the general budget of the Union. This transitional financing model allows the platform to launch without immediate upfront financial barriers for participating public bodies. However, this is not a permanent subsidy: Article 36(2) mandates that EuroCloud members must reimburse these initial costs over a period not exceeding three years from the date the costs were incurred. Once this period elapses, the federation operates on a cost-recovery basis, funded by fees levied on its members to cover ongoing administrative and operational expenses.

Detail

The Cloud and AI Development Act (CADA), as set out in COM(2026) 502 final, establishes the European public sector cloud federation (the "EuroCloud Federation") to facilitate the sharing of data centre and cloud computing services among Union entities and public sector bodies. A critical pillar of this framework is its financial architecture, designed to ensure rapid deployment while maintaining long-term fiscal sustainability.

The Transitional Financing Model: Article 36(2)

The proposal recognises that establishing a new, Union-wide digital federation requires significant upfront capital for platform development, governance setup, and initial operational readiness. To prevent these start-up costs from becoming a barrier to entry for Member States and Union entities, Article 36(2) introduces a specific transitional mechanism.

The text states:

"If the costs are initially borne by the general budget of the Union, they shall be reimbursed by the EuroCloud members over a period not exceeding three years from the date on which the costs were borne by the Union."

This provision creates a clear timeline for financial responsibility:

  1. Front-loading: The Commission may utilise the general EU budget to cover the initial establishment costs. This ensures the federation can be operationalised quickly, aligning with the proposal's broader objectives of accelerating data centre deployment and reducing dependencies.
  2. Reimbursement Obligation: The use of the general budget is not a grant. It creates a debt obligation for the federation members.
  3. Time Limit: The reimbursement must be completed within a maximum window of three years. This ensures that the burden on the general budget is temporary and that the federation transitions to self-sufficiency relatively quickly.

Ongoing Operations: Fee-Based Cost Recovery

Once the initial establishment phase is complete and the reimbursement period concludes, the EuroCloud Federation shifts to a sustainable, fee-based model. Article 36(1) establishes the principle that:

"The costs arising from the activities carried out by the Commission pursuant to this Chapter shall be jointly financed by the members of the EuroCloud Federation through fees levied by the Commission."

These fees are strictly designed to cover the costs incurred by the Commission in administering the federation. The scope of these activities, as defined in Article 36(3), includes:

  • Assessing requests to join the EuroCloud Federation.
  • Establishing and maintaining the platform referred to in Article 34(3) (which provides the catalogue of services and the orchestration platform for resource exchange).

The Status of Fee Revenue: Internal Assigned Revenues

A key feature of the CADA proposal is the treatment of the revenue generated by these fees. Article 36(3) specifies that:

"Revenues generated by the fees shall constitute internal assigned revenues within the meaning of Article 21(3), point (a), of Regulation (EU, Euratom) 2024/2509."

This legal classification has two important implications:

  1. Ring-fencing: The revenue is "assigned," meaning it is legally earmarked to cover the specific costs of the EuroCloud Federation activities. It cannot be diverted to other parts of the EU budget without specific legal provision.
  2. Surplus Handling: The regulation explicitly addresses what happens if the fees collected exceed the costs. Article 36(3) states:

    "Any revenue remaining after covering those costs shall be entered into the general budget of the Union."

This ensures the federation operates on a non-profit, cost-recovery basis. It prevents the accumulation of surplus funds within the Commission and ensures that any over-collection is returned to the general EU budget.

Determining Fee Amounts and Payment Conditions

The primary legislation (the Regulation itself) does not fix the exact monetary value of the fees. Instead, it empowers the Commission to define these details through secondary legislation. Article 36(4) states:

"The Commission shall adopt implementing acts laying down detailed rules for determining the estimated costs, the individual amount of the fees, and the manner and conditions under which the fees are to be paid."

These implementing acts will be adopted in accordance with the examination procedure referred to in Article 46(2). This process ensures that the fee structure is transparent, proportionate, and subject to scrutiny by Member State representatives. The fees will be calibrated to reflect the actual costs of administration and platform maintenance, ensuring that the federation remains financially neutral for the EU budget in the long term.

Distinction from Common Procurement Fees

It is important to distinguish the EuroCloud Federation fees from the fees associated with the common procurement activities described in Chapter IV of Title IV (Articles 37–40). While both mechanisms involve fees levied by the Commission to cover costs, they serve different purposes:

  • EuroCloud Federation Fees (Article 36): Cover the costs of the federation platform and membership administration (sharing idle capacity).
  • Common Procurement Fees (Article 40): Cover the costs of the Commission acting as a central purchasing body for cloud services, software, and AI systems.

Both follow a similar logic of cost recovery and assigned revenues, but they are legally distinct streams under different chapters of the proposal.

What this means for you

For public-sector bodies, IT directors, and financial officers in Member States, the funding model of the EuroCloud Federation has direct implications for budget planning and strategic procurement.

  1. Short-Term vs. Long-Term Budgeting: If your Member State or entity joins the federation, you should anticipate a two-phase financial impact. In the short term (the first few years), there may be no direct fee if the EU budget fronts the start-up costs. However, you must plan for a reimbursement liability that will materialise within a three-year window. Long-term, you must budget for annual fees that cover ongoing operations.
  2. Cost-Benefit Analysis: When evaluating participation in the EuroCloud Federation, consider that the fees are not profit-driven. They are strictly cost-recovery mechanisms. The value proposition lies in accessing shared, sovereign infrastructure and reducing the need for individual entities to invest in their own redundant capacity. The "cost" of the federation is the administrative fee, while the "benefit" is the efficiency of shared resources.
  3. Transparency and Engagement: Since the specific fee amounts and allocation methods are not yet fixed, stakeholders should monitor the Commission's work on the implementing acts under Article 46(2). The methodology for calculating individual fees (e.g., based on capacity shared, usage volume, or a flat rate) will be defined in these acts. Early engagement can help shape a fair and equitable fee structure.
  4. Compliance with Reporting: To ensure accurate fee calculation, participating entities will likely need to provide transparent data on their capacity contributions and usage. Accurate reporting is essential to ensure that the "joint financing" principle is applied fairly and that the reimbursement obligations are met within the three-year limit.

Common misconceptions

Misconception: The EuroCloud Federation is permanently funded by the EU budget. Correction: No. The EU budget may only bear the initial establishment costs as a transitional measure. Article 36(2) explicitly requires members to reimburse these costs within a maximum of three years. After this period, the federation is self-sustaining through member fees.

Misconception: Fees collected by the Commission will generate a profit for the EU. Correction: The fees are strictly for cost recovery. Article 36(3) mandates that any revenue remaining after covering the specific costs of the federation activities must be entered into the general budget of the Union. The federation cannot retain a surplus.

Misconception: The reimbursement period is flexible or open-ended. Correction: The proposal sets a strict upper limit. Article 36(2) states the reimbursement period must be "not exceeding three years." This provides legal certainty for both the Commission and the members regarding the timeline for financial closure of the start-up phase.

Misconception: The fees are a tax on public sector cloud usage. Correction: The fees are administrative charges levied on members of the federation to cover the specific costs of running the platform and assessing membership. They are not a general tax on cloud usage but a specific contribution to the shared infrastructure.

Related

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