Summary An Important Project of Common European Interest (IPCEI) is a State aid mechanism, grounded in Article 107(3)(b) TFEU, that lets Member States jointly subsidise large, cross-border strategic projects — including cloud and AI infrastructure — that the market alone would not finance. As proposed, the Cloud and AI Development Act (CADA) does not create or run IPCEIs and does not change State aid law. Instead, CADA names IPCEIs as one of the instruments expected to keep supporting large-scale, cross-border cloud and AI projects alongside the framework, and it provides the strategic direction (national strategies, capacity monitoring, procurement rules) that helps such projects fit into the EU's wider sovereignty goals.

Detail

What is an IPCEI?

State aid — public support that favours certain undertakings — is in principle incompatible with the internal market under Article 107(1) TFEU because it can distort competition. Article 107(3)(b) TFEU creates an exception for aid "to promote the execution of an important project of common European interest." An IPCEI is the vehicle for that exception: a Commission-approved framework under which several Member States can pool public funding for an ambitious, cross-border project that addresses a market failure, with each IPCEI assessed and cleared individually by the Commission.

For cloud and AI, the relevant example is the IPCEI on Next Generation Cloud Infrastructure and Services, which has supported the development of European cloud and edge capabilities across participating Member States. IPCEIs typically address situations where private investment alone is insufficient to build strategic, large-scale infrastructure.

How IPCEIs relate to CADA — coordination, not creation

CADA is a regulatory and strategic framework; it does not establish a new funding pot for cloud infrastructure, and it does not amend State aid rules. The proposal is explicit that its financing relies on existing or planned EU instruments. In the explanatory memorandum's section on synergies with the multiannual financial framework, the Commission states that "IPCEIs would continue to support large-scale, cross-border projects where cloud, edge, chips, cybersecurity or AI infrastructure require coordination among Member States and private investment." IPCEIs are therefore positioned as a complementary instrument that continues in parallel with CADA.

The connection between the two is best understood as coordination across several CADA provisions:

1. Strategic alignment via national strategies (Article 7). CADA would require each Member State to adopt a national cloud and AI strategy within one year of entry into force (Article 7(1)). Among other things, these strategies must include "measures to invest in high-intensity computing infrastructure, including AI factories, AI gigafactories and quantum computers as strategic national and cross-border assets" (Article 7(2)(e)), and measures to support the deployment of data centre capacity (Article 7(2)(d)). IPCEI projects are natural components of such strategies, and the strategy requirement helps ensure nationally funded infrastructure pulls in the same direction as Union goals. Recital 31 calls for consistency and synergies between the Leadership Initiatives and national plans, including recovery and resilience plans, to maximise impact and avoid duplication of funding.

2. The Leadership Initiatives and their funding (Article 6). Article 6 sets out how the Cloud and AI Leadership Initiatives are implemented, and Article 6(3) provides that they may be supported by funding from Union programmes, including Horizon Europe and the Digital Europe Programme. Recital 29 adds that Member States may support the initiatives through research, development and innovation measures "in line with the applicable State aid rules", as well as through private investment. IPCEIs are one State aid route through which such national support can flow into the physical and digital infrastructure the initiatives rely on.

3. Demand-side support through procurement (Title IV and related provisions). Where IPCEIs help build supply, CADA shapes demand. National strategies must include public procurement and procurement-of-innovation measures (Article 7(2)(f), Article 33), and CADA's wider procurement provisions steer public buyers toward services meeting Union assurance levels. This helps ensure that European providers — including those benefiting from IPCEI support — find customers in a market currently dominated by non-EU hyperscalers.

The role of State aid rules

IPCEIs remain subject to State aid scrutiny, and the Commission must approve each one. CADA does not alter that assessment. What CADA adds is policy context and common benchmarks: by defining Union assurance levels and identifying strategic data centre projects and capacity gaps (Articles 14 and 15), it gives Member States and the Commission a shared understanding of what counts as strategically important cloud and AI infrastructure. The recitals also stress that support for strategic projects should address market failure proportionately "without duplicating or crowding out private financing."

IPCEIs alongside the other instruments CADA names

It is worth seeing where IPCEIs sit relative to the other financing routes the proposal mentions, because they are complementary rather than competing. The explanatory memorandum's synergies section lists, in addition to IPCEIs: FP10 and the European Competitiveness Fund (the ECF expected to be the main deployment instrument, especially under its Digital Leadership window); European Digital Infrastructure Consortiums (EDICs) as governance vehicles for groups of Member States operating common infrastructure; cohesion policy instruments such as the ERDF and the Cohesion Fund for co-financing digital infrastructure in less-developed regions; and InvestEU for improving the investment environment and mobilising private and public capital. IPCEIs are the route specifically suited to large, cross-border projects requiring coordinated Member State funding and significant private investment — for example, building out cloud, edge, chips, cybersecurity or AI infrastructure across several countries at once. A single CADA-aligned ambition might therefore be supported by an IPCEI for the cross-border build-out, ECF or Digital Europe funding for deployment, and national or private money on top.

How the supply side and demand side fit together

A useful way to picture the relationship is supply versus demand. IPCEIs (and the other instruments above) chiefly address the supply side: they help finance the construction of European cloud, edge, chips and AI infrastructure that the market would underinvest in. CADA's procurement-related provisions address the demand side: by steering public buyers toward services that meet Union assurance levels and by requiring national strategies to include public procurement and procurement-of-innovation measures (Article 7(2)(f) and Article 33), the framework helps ensure that the capacity built with public support actually finds customers. Article 33 also sets the objective that at least 25% of Member States' procurement for cloud computing services and AI systems be awarded to innovative SMEs, and that strategies include plans to achieve it. This pairing matters: in a market where three non-EU hyperscalers control over 70% of European cloud, IPCEI-supported European providers could struggle to win business without a corresponding pull from public demand. CADA is designed to supply that pull, while leaving the actual financing to instruments like IPCEIs.

The recitals reinforce that the goal is coherence, not consolidation. Recital 31 asks the Commission and Member States to ensure consistency, complementarity and synergies between the Leadership Initiatives and national and regional plans — including recovery and resilience plans and smart specialisation strategies — "to maximise the impact of public investments [and] avoid duplication of funding." IPCEIs, which often interlock with national plans, are exactly the kind of instrument this coordination is meant to keep aligned with Union-level objectives.

What this means for you

For public-sector and procurement officers, the IPCEI–CADA relationship matters for planning and tender design:

  • Build on IPCEI-supported capacity in procurement. Aligning procurement requirements with Union assurance levels supports the European providers that IPCEIs help build, turning public spending into demand for sovereign infrastructure.
  • Keep your strategy coherent with the national one. Your organisation's cloud plans should fit your Member State's national cloud and AI strategy under Article 7, including its choices about high-intensity computing investment.
  • Watch State aid boundaries in tenders. Technical requirements must not be discriminatory; CADA does not change that. It does, however, provide the policy rationale for treating certain cloud and AI infrastructure as of common European interest.

Common misconceptions

  • "CADA funds cloud infrastructure directly." As proposed, no. CADA is a framework; funding comes from instruments such as IPCEIs, Union programmes (Horizon Europe, Digital Europe), the future European Competitiveness Fund, InvestEU and national budgets.
  • "IPCEIs and CADA do the same thing." They are complementary. IPCEIs are a State aid mechanism for funding cross-border projects; CADA sets the rules and strategic direction within which those projects operate.
  • "CADA changes State aid law." No. It does not touch Article 107 TFEU. IPCEIs continue to be assessed and approved under the existing State aid framework.

Related

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