Summary As proposed, the Cloud and AI Development Act (CADA) has two distinct, complementary general objectives, set out in Article 1. The first (Article 1(2)) is to ensure the conditions necessary for the competitiveness and innovation capacity of the EU's cloud and AI ecosystem. The second (Article 1(3)) is to improve the functioning of the single market by laying down a uniform framework that increases the Union's resilience and strategic autonomy in cloud and AI. These two objectives map onto CADA's dual legal basis — Article 173(3) TFEU (industrial competitiveness) and Article 114 TFEU (internal-market harmonisation) — and drive a mix of supply-side support and demand-side procurement rules. CADA is still a proposal.

Detail

CADA does not pursue a single goal. The text sets out two separate but complementary general objectives, each connected to a different Treaty basis, which is why the Regulation blends industrial policy with single-market harmonisation.

The two general objectives

Article 1(2): competitiveness and innovation. The first general objective is "to ensure the conditions necessary for the competitiveness and innovation capacity of the Union's cloud and AI ecosystem." This is the supply-side goal: build the industrial base, support research and development, and give European providers the conditions to compete. The recitals tie this to Article 173(3) TFEU, which concerns industrial competitiveness; the memorandum notes that measures under this basis should not entail harmonisation of national laws.

Article 1(3): single market, resilience and strategic autonomy. The second general objective — described in the text 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." This is the harmonisation-and-sovereignty goal, grounded in Article 114 TFEU.

How the objectives translate into measures

These objectives drive the five measures listed in Article 1(1).

  • Supply-side measures (competitiveness). CADA would establish the Cloud and AI Leadership Initiatives to support research, innovation and large-scale capacity, including next-generation, resource-efficient data centre technologies, open cloud-computing-stack technologies, and frontier, physical and industrial AI. The aim is to ensure public buyers and businesses have credible European alternatives.
  • Demand-side and sovereignty measures (resilience/autonomy). CADA would create the Union cloud computing sovereignty framework — the four Union assurance levels (Article 16, with criteria in Annex II) — and require public bodies to assess risk (Article 29) and procure at a matching assurance level (Article 30).

Why the single-market angle matters

National approaches to cloud sovereignty and data centre deployment currently differ, fragmenting the market and making it harder for European providers to scale. By harmonising these rules and the assurance framework, CADA aims to ensure that a service recognised at a given level in one Member State is recognised across the Union, improving how the single market functions — the core of the second objective.

What this means for you

For citizens, businesses and especially public-sector buyers, the dual objectives explain why CADA is part industrial-support programme and part procurement rulebook.

Procurement aligns with sovereignty. Because strategic autonomy is a core objective, public buyers would, if CADA is adopted, run risk assessments and procure cloud services at the matching Union assurance level — level 1 as a baseline, levels 2 to 4 where an activity has public-order relevance.

Value, not only price. The competitiveness objective is reflected in procurement: as proposed, contracting authorities would apply "Union added value" award criteria when procuring innovative cloud services and AI systems (Article 32), so contribution to the European cloud and AI ecosystem becomes part of the evaluation rather than price and performance alone.

More harmonised rules over time. The single-market objective means less national divergence: common definitions of sovereignty, harmonised assurance levels and the possibility of joint procurement facilitated by the Commission.

Open source as a lever. To support innovation and reduce vendor lock-in, CADA encourages open-source solutions and the reuse of public-sector software (Articles 41 to 43).

Common misconceptions

"CADA is only about restricting non-European providers." No. Reducing dependence is one outcome, but the first general objective is to strengthen the European ecosystem itself, through substantial supply-side support. It is as much about building capability as about regulating procurement.

"All cloud services must be 100% European." No. The sovereignty framework is tiered and risk-based. Not every public-sector activity needs the highest level; lower levels remain open to a broader range of providers that meet the criteria.

"CADA replaces data-protection law." No. CADA complements instruments like the GDPR and the Data Act. GDPR governs personal data; CADA addresses sovereignty, operational autonomy and industrial competitiveness. They work together.

"The two objectives are the same thing said twice." No. The text deliberately separates them and ties each to a different Treaty basis (Article 173(3) and Article 114), because a single basis would not support both the industrial-support measures and the harmonisation measures.

Official sources

Related

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