Summary Under the proposed Cloud and AI Development Act (CADA), the European Commission would collect three specific categories of data to monitor the EU's compute capacity gap: available compute capacity (explicitly including edge computing), the volume of demand for data centre capacity, and the size of the capacity gap itself. As set out in Article 15, the Commission would identify underserved areas "in cooperation with the Member States" to inform the designation of future data centre acceleration zones. This monitoring is designed to guide investment, ensure geographically balanced deployment, and support the EU's Digital Decade targets.

Detail

The Cloud and AI Development Act (CADA), as proposed in COM(2026) 502 final, addresses a critical structural deficit in the EU's digital infrastructure: the shortage of computing capacity. To tackle this, the proposal establishes a rigorous monitoring framework to quantify the "capacity gap"β€”the difference between available supply and market demand. The legal basis for this data collection is Article 15, titled "Monitoring the capacity gap," found in Title III of the proposal.

The Three Core Data Points

Article 15(1) explicitly mandates that the Commission shall identify and monitor three distinct data points. These metrics are essential for assessing progress toward the objectives of the Digital Decade Policy Programme 2030 (Decision (EU) 2022/2481):

  1. Available Compute Capacity: The Commission would track the total compute capacity available within the Union. Crucially, the text of Article 15(1)(a) specifies that this definition is broad and explicitly includes "edge computing capacity." This ensures that the monitoring captures not only centralized hyperscale data centres but also distributed infrastructure located closer to end-users, which is vital for low-latency AI applications and real-time processing.
  2. Volume of Demand: The Commission would monitor the "volume of demand for data centre capacity" (Article 15(1)(b)). This metric is critical for distinguishing between a lack of physical infrastructure and a lack of market uptake. It allows policymakers to determine whether the bottleneck is supply-side (lack of buildings/power) or demand-side (lack of adoption), enabling more targeted policy interventions.
  3. Size of the Capacity Gap: By comparing the available supply against the volume of demand, the Commission would calculate the "size of the capacity gap" (Article 15(1)(c)). This aggregate figure serves as the primary indicator of the EU's infrastructure deficit.

Cooperation with Member States

The proposal does not envision the Commission acting in isolation to gather this data. Article 15(1)(c) explicitly states that the identification of underserved areas and the monitoring of the capacity gap would occur "in cooperation with the Member States."

This collaborative mechanism is essential because national authorities possess granular, localized data regarding existing infrastructure, planned projects, and regional economic needs that a central EU body cannot access directly. The Legislative Financial and Digital Statement (Section 4.2) confirms that Member States are the primary actors providing the data required for this monitoring.

The results of this cooperation are not merely for statistical reporting; they have direct operational consequences. Article 15(1)(c) notes that the underserved areas identified through this process could subsequently be used as a basis for designating "acceleration zones" for the deployment of new data centre capacity. This creates a direct link between the monitoring function in Article 15 and the permitting acceleration mechanisms described in Articles 10–14 of Title III. Essentially, the data collected under Article 15 determines where the EU will prioritize the streamlining of permits and the allocation of resources to build new infrastructure.

Data Sources, Annexes, and Methodology

While Article 15 establishes the obligation to monitor, the specific methodologies, templates, and detailed data formats are not enumerated in the enacting articles themselves. Instead, the proposal relies on secondary legislation and existing statistical frameworks to define the precise data requirements.

Recital 44 reinforces the strategic purpose of this monitoring, stating that the data may be used by the Commission to inform possible recommendations to guide Member States in accelerating deployment. It further notes that this monitoring aligns with the Digital Decade Policy Programme 2030, where the Commission reviews digital targets to reflect technical, economic, or societal developments.

The Legislative Financial and Digital Statement (Section 4.2, "Data") provides further clarity on the nature of the data. It categorizes the requirement under Article 15 as "Statistics and data required for the monitoring of the capacity gap." The statement confirms that this data collection aligns with the "once-only principle," aiming to reuse existing statistical frameworks and minimize the administrative burden on Member States and operators.

Furthermore, Annex III of the proposal, which details the audit evidence for the sovereignty framework, does not directly govern Article 15 monitoring. However, the data flows described in the Digital Statement (Section 4.2) indicate that Member States provide the data to the Commission, which then processes it to identify underserved areas. The Commission is empowered to request information from cloud service providers to support this analysis, as noted in the Digital Statement's data flow tables, ensuring the data is sufficiently complete and reliable.

Strategic Purpose of the Monitoring

The data collected under Article 15 serves several strategic objectives outlined in the explanatory memorandum and the proposal's specific objectives:

  • Geographic Balancing: By identifying underserved areas, the EU aims to prevent further concentration of data centres in established hubs (such as Northern Europe). This reduces latency for peripheral regions and ensures equal opportunities for businesses across the Union, addressing the "structural imbalances" mentioned in Recital 36.
  • Investment Guidance: Clear, EU-wide data on the capacity gap helps private investors understand where infrastructure is lacking. This transparency is intended to de-risk investments in underserved regions, encouraging the deployment of sustainable and innovative computing capacity.
  • Policy Adjustment: The monitoring allows the Commission to assess whether the EU is on track to meet its intermediate objective of tripling data centre capacity by 2030 and meeting its needs by 2035. If the gap widens, the Commission can issue recommendations or adjust the designation of acceleration zones.

What this means for you

For public-sector procurement officers, national competent authorities, and data centre operators, Article 15 has direct operational implications:

  1. Reporting Obligations: National authorities will likely be required to provide granular data on compute supply and demand to the Commission. If you are a national authority, ensure your internal systems can accurately track both traditional data centre capacity and emerging edge computing resources to meet these reporting needs.
  2. Acceleration Zone Designation: If your region is identified as "underserved" through this monitoring process, it may be designated as a data centre acceleration zone. This triggers streamlined permitting processes (Article 13) and the establishment of single information points (Article 12). Local authorities must be prepared to manage these accelerated procedures.
  3. Strategic Planning: For cloud service providers, understanding the capacity gap data can inform expansion strategies. Regions identified as having a high capacity gap may offer incentives or faster permitting, making them attractive for new investments.
  4. Procurement Alignment: When procuring cloud services, understanding the local capacity gap can inform risk assessments. If your region lacks sufficient sovereign capacity, you may face longer migration timelines or need to rely on cross-border solutions within the EuroCloud Federation to meet procurement requirements.

Common misconceptions

  • "The Commission monitors individual data centre operators in real-time."
    • Correction: Article 15 focuses on macro-level statistics: total capacity, total demand, and the aggregate gap. It does not mandate the Commission to collect real-time operational data from individual private operators. Granular operator data is more relevant to the sovereignty framework audits (Article 20) rather than capacity gap monitoring.
  • "Edge computing is excluded from the monitoring."
    • Correction: Article 15(1)(a) explicitly states that the Commission shall monitor compute capacity available in the Union, "including edge computing capacity." This is a critical inclusion for AI workloads requiring low latency and is a deliberate expansion of the monitoring scope beyond traditional data centres.
  • "This monitoring replaces national cloud strategies."
    • Correction: The monitoring complements national cloud and AI strategies (Article 7). Member States still set their own priorities and design their own strategies, but the Commission's monitoring ensures these national efforts contribute to the broader EU objective of closing the capacity gap and preventing market fragmentation.
  • "The Commission sets the capacity targets."
    • Correction: The Commission monitors progress against targets set in the Digital Decade Policy Programme 2030 (Decision (EU) 2022/2481). While the Commission can recommend measures to address the gap, the primary targets for capacity deployment are established by the Digital Decade framework, which CADA supports.

Official sources

Related

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