Summary Under the proposed EU Cloud and AI Development Act (CADA, COM(2026) 502 final), the members of the EuroCloud Federation would jointly pay for running it. As proposed in Article 36(1), the costs the Commission incurs in carrying out its tasks for the Federation would be financed by the members through fees that the Commission levies. Where the Union budget pays upfront, members would have to reimburse it within three years (Article 36(2)). These administrative fees are separate from the cost-recovery payments that one body would make to another when it actually shares cloud or data centre capacity (Article 35(5)). Because CADA is still a proposal, the figures, detailed rules, and timing could all change before any text is adopted.
Detail
The EuroCloud Federation is a mechanism proposed under CADA to make it easier for public bodies across the EU to share data centre and cloud computing capacity. Membership, as proposed in Article 34(1), would be open to Union entities (such as EU institutions, bodies, offices, and agencies) and to public sector bodies, and would be voluntary. A natural question for anyone watching this proposal is who would foot the bill for setting up and running the Federation. The answer in the draft is clear in principle: the members would.
As proposed, the financing model rests on a cost-recovery logic rather than a standing line in the EU's general budget. The idea is that the bodies that benefit from the shared infrastructure and the administrative support around it would also be the ones paying for it.
Joint financing through fees
The core rule is in Article 36(1), which provides 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."
In practice, this would cast the Commission as the body that administers the Federation and bears the running costs in the first instance — for example, the work of assessing requests to join and of establishing the platform referred to in Article 34(3). Under the proposal, those costs would not sit permanently on the EU budget. Instead they would be recovered through fees charged to the participating members, who would share the burden collectively.
The "members" here are the Union entities and public sector bodies that, as proposed in Article 34(1), choose to take part. Participation would be voluntary, but a body that opts in would, under Article 36(1), be agreeing to contribute to the collective cost of running the Federation.
Reimbursement of upfront costs
Setting up new shared digital infrastructure requires money before any fees can be collected. The proposal addresses this in Article 36(2): "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."
As proposed, this would let the Union budget carry the early establishment costs so that the platform could get off the ground without each member having to pay in advance. Crucially, though, this would be a bridge, not a grant. Members would be legally bound to pay the Union back, and the reimbursement would have to be completed within three years of the date the relevant costs were borne. The three-year ceiling is a maximum, so the detailed schedule could in principle be shorter.
How the fee revenue would be treated
According to the proposal's explanatory memorandum, the additional administrative expenditure for the Commission's new tasks "will be mostly financed through fee-based revenue streams that fall under internal assigned revenues," and this is said to include administration of the EuroCloud initiative for sharing idle cloud and data centre capacity.
Article 36(3) would give this legal effect. The fee revenues would be treated as internal assigned revenues within the meaning of Article 21(3)(a) of Regulation (EU, Euratom) 2024/2509, and would be assigned to cover the Commission's activities under this Chapter — expressly "including assessing request to join the EuroCloud Federation and the establishment of the platform referred to in Article 34(3)." Any amount left over after those activities are covered would, as proposed, be entered into the general budget of the Union. In plain terms, the money raised would be ring-fenced for the Federation's own costs rather than flowing into general spending.
The proposal does not set the fee levels itself. Under Article 36(4), the Commission would adopt implementing acts laying down detailed rules on the estimated costs, the individual amount of the fees, and the manner and conditions of payment, following the examination procedure in Article 46(2). So the actual numbers, payment mechanics, and any differentiation between members would be settled later, if and when the regulation is adopted.
What this means for you
For public bodies and procurement teams considering the Federation, the funding model matters for budgeting and planning. The points below describe what the proposal would mean — none of it is in force yet.
- Budget for administration on top of services. As proposed, you would need to account for ongoing administrative fees under Article 36 in addition to whatever you pay for the capacity you use. The shared model may bring savings, but running the Federation would carry its own cost.
- Be aware of reimbursement exposure. If your entity joins while the Union budget is pre-financing the setup, you could be liable for a share of those upfront costs, repayable within three years under Article 36(2).
- It is opt-in. Under Article 34(1), membership would be voluntary; you would not be a member automatically and would have to request to join. Once in, you would be subject to the fee framework set by the Commission's implementing acts.
- Watch for the implementing acts. The amounts and payment conditions are not in the proposal itself. They would come from implementing acts under Article 36(4), so the practical cost picture will only become clear later.
Common misconceptions
- "Joining the Federation would be free." As proposed, running the Federation is funded by member fees. Article 36(1) provides that members jointly finance the Commission's activities through fees levied by the Commission.
- "The EU budget would pay for it permanently." Under the proposal, the Union budget might cover initial costs, but Article 36(2) would require members to reimburse those costs within three years. Ongoing administration would be member-funded.
- "The Article 36 fees pay for the cloud storage and compute itself." No. The Article 36 fees, as proposed, cover the Commission's administration of the Federation (such as assessing membership requests and establishing the Article 34(3) platform). Paying for the capacity actually shared between a sharing body and a using body is dealt with separately: Article 35(5) provides for a distinct cost-recovery fee between those two bodies. Article 36 admin fees and the Article 35(5) service-sharing fee are not the same thing.
- "There is a published fee figure." The proposal does not set any amounts. Under Article 36(4), the individual fee amounts and payment conditions would be fixed later through implementing acts, so no figure should be assumed today.
Related
- Who runs the EuroCloud Federation under CADA?
- Who can join the EuroCloud Federation under CADA?
- EuroCloud Federation: Who is liable when public bodies share services?
- Why was the EuroCloud Federation created? CADA's public-sector cloud strategy
- Why does CADA separate the EuroCloud Federation from Commission procurement?
This is general information about a draft EU regulation, not legal advice.