Summary The proposed Cloud and AI Development Act (CADA) separates two general objectives from five concrete measures. The two objectives, in Article 1(2) and Article 1(3), correspond to the proposal's dual legal basis: strengthening competitiveness and innovation capacity (grounded in Article 173(3) TFEU) and improving the functioning of the single market through a uniform legal framework (grounded in Article 114 TFEU). The five measures, listed in Article 1(1), are the specific policy tools — the Cloud and AI Leadership Initiatives, accelerated data centre deployment, the sovereign cloud and AI offer, reducing dependencies, and fostering public-sector adoption — delivered across Titles II to IV.

Detail

As proposed, CADA combines supply-side support with demand-side regulation. To read its architecture, distinguish why the EU is acting (the objectives) from how it is acting (the measures). The distinction matters because CADA rests on a cumulative legal basis, with different parts serving different treaty purposes.

The two general objectives

Article 1 of the proposal sets out two separate general objectives that map to the legal bases cited in the recitals.

  1. Competitiveness and innovation (Article 1(2)): The first general objective is "to ensure the conditions necessary for the competitiveness and innovation capacity of the Union's cloud and AI ecosystem." Recital 8 grounds the related measures in Article 173(3) TFEU, noting expressly that such measures "should not entail the harmonisation of national laws or regulations." This is the supply side: technological base, capacity and resilience.
  2. Internal market functioning (Article 1(3)): The second general objective, described as "separate from and complementary to" the first, is "to improve the functioning of the single market by laying down a uniform Union legal framework for increasing the Union's resilience and strategic autonomy in cloud and AI technologies." Recital 9 grounds this in Article 114 TFEU, which allows harmonisation to ensure the functioning of the internal market. This is the demand-side and regulatory-alignment dimension.

Recital 7 of the proposal confirms the split, stating that "[t]he framework pursues separate objectives, relying on two distinct legal bases."

The five concrete measures

While the objectives define the ends, Article 1(1) lists the five concrete means CADA would use, distributed across Titles II, III and IV.

  1. Cloud and AI Leadership Initiatives (Article 1(1)(a)): Establishing the Cloud Leadership Initiative and the AI Leadership Initiative. Found in Title II, these support research, innovation and large-scale capacity, implemented through "grand challenges" set out in Annex I (such as frontier AI, physical and industrial AI, and energy-efficient data centres). They serve the competitiveness objective.
  2. Accelerated data centre deployment (Article 1(1)(b)): "[S]etting the framework for the accelerated deployment of data centres across the Union." Detailed in Title III — data centre acceleration zones, single information points for permits, and the designation of strategic projects (Article 14). It supports both objectives by removing national permitting barriers and boosting physical capacity.
  3. Sovereign cloud and AI offer (Article 1(1)(c)): "[E]nabling the availability of a sovereign cloud and artificial intelligence (AI) offer to safeguard the Union's public order." This is the core of Title IV, Chapter I — the Union cloud computing sovereignty framework with four assurance levels (Article 16, criteria in Annex II). It serves the internal-market objective by harmonising what counts as a recognised sovereign service.
  4. Reducing dependencies (Article 1(1)(d)): "[R]educing dependencies on critical technologies." This thread runs through the sovereignty framework and the leadership initiatives, aiming to cut reliance on third-country providers and strengthen supply-chain resilience.
  5. Fostering public-sector adoption (Article 1(1)(e)): "[F]ostering the adoption of cloud computing services across the public sector." Reflected across Title IV through risk assessments, procurement rules, the EuroCloud Federation and open-source/reuse provisions. It drives demand for recognised sovereign services.

How they connect

The relationship is hierarchical: the objectives justify EU intervention under the Treaties, while the measures are the operational mechanisms. The competitiveness objective (Article 1(2), via Article 173(3) TFEU) is pursued through measures like the Leadership Initiatives; the internal-market objective (Article 1(3), via Article 114 TFEU) is pursued through measures like the sovereignty framework and public-sector adoption that harmonise otherwise divergent national rules.

What this means for you

For in-house counsel and compliance officers, this distinction helps map obligations to regulatory intent.

  • Procurement teams: As a contracting authority, you are primarily affected by Title IV (sovereignty and adoption). You would conduct risk assessments (Article 29) and procure services meeting the appropriate Union assurance level (Article 30). The competitiveness objective is less directly relevant to daily compliance but explains why European alternatives are promoted.
  • Cloud providers: Under the sovereignty framework (Title IV), you must navigate the assurance levels (Article 16, Annex II) and the recognition process (Article 17) to serve the public-sector market. This supports the internal-market objective of harmonised trust standards.
  • Data centre operators: You are most affected by Title III (acceleration zones and strategic-project designation), whose streamlined permitting serves the competitiveness objective.

Knowing which objective drives a measure also helps anticipate secondary legislation. Measures resting on Article 114 TFEU (internal market) tend toward strict harmonisation; measures resting on Article 173(3) TFEU (competitiveness) involve coordination rather than harmonisation of national laws, as Recital 8 makes explicit.

Common misconceptions

  • Misconception: "CADA is just about cloud sovereignty."
    • Reality: Sovereignty is one of five measures (Article 1(1)(c)). CADA also invests heavily in supply-side capacity through the Leadership Initiatives (Article 1(1)(a)) and data centre deployment (Article 1(1)(b)).
  • Misconception: "The objectives are just vague goals."
    • Reality: The two objectives in Article 1(2) and (3) are legally significant because they justify the dual legal basis, which underpins the scope of EU competence for the regulation.
  • Misconception: "Measures are optional policy suggestions."
    • Reality: As proposed, CADA is a Regulation — directly applicable. The five measures translate into binding provisions across Titles II–IV, such as mandatory risk assessments for public bodies and the criteria for cloud assurance levels.

Official sources

Related

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