Summary Under the proposed Cloud and AI Development Act (CADA), the full regulatory framework and its support mechanisms would become applicable one year after the Regulation enters into force, as explicitly set out in Article 48. While the text enters into force 20 days after publication in the Official Journal, the substantive obligations for Member States and the availability of support structuresβ€”such as Experience and Acceleration Centres for AI and the central repository of sovereign cloud servicesβ€”would only trigger after this one-year transition period. Startups should anticipate a phased rollout: national strategies and Centres for AI would be established within that first year, while access to the sovereign cloud marketplace and specific compute allocations would follow as recognition procedures and work programmes are operationalised.

Detail

The Cloud and AI Development Act (CADA), as proposed in COM(2026) 502 final, is designed to strengthen Europe's cloud and AI ecosystem through a combination of supply-side measures, demand-side adoption, and a new sovereignty framework. For AI startups, the timing of when these mechanisms become actionable is a critical variable for strategic planning. The proposal establishes a clear, legally binding timeline grounded in Article 48, which distinguishes between the entry into force of the law and its application date.

Entry into Force vs. Application: The One-Year Gap

The proposal specifies a distinct two-step timeline in Article 48:

  1. Entry into Force: The Regulation "shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union."
  2. Application Date: The Regulation "shall apply from [same day and month as date of entry into force plus 1 year]."

This one-year gap is not merely a formality; it is a mandatory transition period designed to allow Member States and Union entities to prepare the necessary administrative and technical infrastructure. During this year, the legal text is binding, but the active deployment of the support measures described in Title II (Research, Development and Deployment) and Title IV (Autonomy) would not yet be in effect. For startups, this means that while the legal framework would be set, the actual "benefits"β€”such as access to Centres for AI, specific compute allocations, or listing in the sovereign cloud repositoryβ€”would not be available until the application date arrives.

Rollout of National Strategies and Acceleration Centres

A primary channel for startup support under CADA is the network of Experience and Acceleration Centres for AI (referred to as "Centres for AI"). These centres are tasked with accelerating the adoption of AI and cloud technologies, particularly for SMEs and start-ups, by providing access to technologies, upskilling schemes, and connections to European providers (Article 5).

The operationalisation of these centres is tightly coupled with the national cloud and AI strategies. Article 7(1) mandates that Member States "shall establish national cloud and AI strategies" by a specific deadline: "[same day as entry into force plus one year]." This deadline aligns precisely with the application date set in Article 48.

Consequently, the rollout sequence for startups would be:

  • Month 0–12 (Transition Period): Member States draft and adopt their national strategies. These strategies must include measures to accelerate AI adoption and support the deployment of Centres for AI (Article 7(2)).
  • Month 12+ (Application Date): The national strategies are in force, and the Centres for AI are expected to be fully operational. Article 5(1) requires Member States to establish these centres, building on existing European Digital Innovation Hubs. Startups should expect that from the application date, a designated local or regional body will be available to provide tailored support, facilitate expertise transfer, and assist in scaling up spin-offs and start-ups emerging from universities and incubators (Article 5(3)).

Access to Compute and the Leadership Initiatives

CADA establishes the Cloud and AI Leadership Initiatives to promote research, innovation, and large-scale capacity building (Article 3). These initiatives include operational objectives for advancing frontier AI, physical AI, and industrial AI, as well as increasing adoption at regional and local levels (Article 4).

For startups seeking access to high-performance computing (HPC), Article 9 outlines the mechanism for resource allocation. The Union and Member States "shall ensure that sufficient AI computing resources... are allocated to support the development of frontier AI priority projects" and other industrial innovation projects. However, this access is not automatic or immediate upon application.

The process involves:

  1. Designation: Projects must be recognised as "frontier AI priority projects" by the Commission based on specific criteria, including participation by a European digital infrastructure consortium and involvement of at least three Member States (Article 8).
  2. Allocation: Once designated, the Union and Member States "shall at least match the AI computing resources contributed by Member States" within the limits of available European high-performance computing capacity (Article 9(2)).

The timeline for startups to access these resources depends on the Commission's adoption of work programmes and the operational readiness of the EuroHPC Joint Undertaking or other implementing structures. While the legal framework for allocation would be active from the application date, the actual availability of compute resources would follow the selection of projects through open calls and "grand challenges" outlined in Annex I.

The Sovereign Cloud Marketplace and Repository

A significant market opportunity for startups lies in the central repository of recognised cloud computing services. Article 22 requires the Commission to establish and maintain a dedicated repository of services recognised as offering Union assurance levels 1 through 4.

The availability of this "marketplace" is contingent on the prior establishment of the recognition and audit mechanisms:

  • Recognition Procedures: Cloud providers must submit applications to national competent authorities (Article 17). For Level 1, this involves a self-assessment; for Levels 2–4, it requires independent third-party audits (Article 20).
  • National Competent Authorities: Member States must designate these authorities by "[date of entry into force plus 1 year]" (Article 25(1)), coinciding with the application date.
  • Repository Launch: Once the first recognitions are granted and registered by the competent authorities, the Commission would populate the central repository (Article 22(2)).

Therefore, while the legal basis for the repository exists from the application date, the marketplace itself would likely become functional in the months following, as the first wave of providers undergoes the recognition process. For startups developing cloud or AI services, listing in this repository would be a prerequisite for accessing public procurement opportunities that require specific assurance levels (Article 30).

Additionally, Article 43 mandates the creation of an EU Open Source Solutions Catalogue. This centralised catalogue, hosted on the Interoperable Europe portal, would allow public administrations to search for and access software made available for reuse. Startups contributing to open-source AI components could gain visibility and adoption channels once this catalogue is launched, which is expected to follow the establishment of the necessary network of Open Source Programme Offices (Article 44).

What this means for you

For CTOs, founders, and architects at AI startups, the CADA timeline suggests a "prepare now, engage later" strategy.

  1. Monitor the One-Year Transition: Mark the date of the Regulation's publication. The one-year countdown to application is the critical window for national strategy formulation. Engage with your national government during this period to ensure your sector's needs are reflected in the national cloud and AI strategy (Article 7).
  2. Identify Your Local Centre for AI: Once the application date arrives, locate the Experience and Acceleration Centre for AI in your region. These centres are your primary entry point for upskilling, networking, and accessing European providers (Article 5).
  3. Align with Sovereignty Criteria Early: If you target the public sector, begin aligning your software supply chain and data practices with the criteria for Union assurance levels (Annex II) well before the application date. This preparation will accelerate your path to recognition and listing in the central repository (Article 22).
  4. Prepare for Compute Access: While direct HPC access is not immediate, familiarise yourself with the criteria for "frontier AI priority projects" (Article 8). Position your startup's R&D roadmap to meet these criteria, as this will be the gateway to accessing matched computing resources under Article 9.
  5. Leverage Open Source: Consider releasing non-core components under open-source licences and registering them in the future EU OSS Catalogue (Article 43) to increase discoverability among public sector buyers.

Common misconceptions

  • Misconception: Support is available immediately upon publication.
    • Reality: Article 48 clearly establishes a one-year gap between entry into force and application. The Centres for AI, the central repository, and the compute allocation mechanisms would not be operational until this transition period concludes.
  • Misconception: All startups get automatic access to HPC.
    • Reality: Access to AI computing resources under Article 9 is conditional. It is prioritised for "frontier AI priority projects" and specific industrial innovation categories. Startups must compete for these resources based on specific criteria, not simply by virtue of being a startup.
  • Misconception: The sovereign cloud marketplace is a general public cloud.
    • Reality: The central repository under Article 22 lists services recognised for specific Union assurance levels. It is primarily a tool for public sector procurement compliance (Article 30), not a general commercial marketplace. Startups must meet strict sovereignty and audit criteria to be listed.
  • Misconception: CADA replaces existing national funding.
    • Reality: CADA complements existing instruments like Horizon Europe and the Digital Europe Programme. It creates a framework for coordination and new mechanisms (like the EuroCloud Federation), but it does not eliminate national initiatives.

Related

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