Summary Under the proposed Cloud and AI Development Act (CADA), the "data centre capacity gap" is the specific shortfall between the total computing capacity currently available in the European Union and the volume of demand for that capacity. As proposed, Article 15 mandates the European Commission to actively identify and monitor this gap by tracking three key metrics: available compute capacity (including edge), the volume of demand, and the size of the gap itself. Recital 44 clarifies that this monitoring is essential to inform recommendations to Member States and to address the strategic deployment of data centre capacity across the Union, ensuring the EU can meet its digital sovereignty and AI development goals.

Detail

The Cloud and AI Development Act (CADA), as proposed in COM(2026) 502 final, addresses a critical structural bottleneck in the European digital ecosystem: the shortage of computing infrastructure. To tackle this, the proposal establishes a rigorous, data-driven mechanism for defining and monitoring the "data centre capacity gap." This is not a static statistic but a dynamic metric that drives the EU's infrastructure policy.

Defining the Capacity Gap

In the context of CADA, the capacity gap is not merely a vague notion of "not enough servers." It is a precise calculation derived from the difference between two primary, monitored factors:

  1. Available Compute Capacity: This refers to the actual computing power currently deployed and operational within the Union. Crucially, Article 15(1)(a) explicitly defines this to include not only traditional data centre capacity but also edge computing capacity. This broad definition ensures that distributed, low-latency computing resourcesβ€”essential for AI and real-time applicationsβ€”are accounted for in the total supply.
  2. Volume of Demand: This refers to the total demand for data centre capacity across the Union, as referenced in Article 15(1)(b). This demand is driven by the rapid proliferation of AI workloads, which require unprecedented computational capabilities.

The gap exists where the demand for these resources exceeds the available supply. As noted in the explanatory memorandum, this shortage currently forces European enterprises to route critical workloads through foreign hyperscaler infrastructure, creating dependencies that the EU seeks to reduce.

The Commission's Monitoring Mandate: Article 15

The proposal places the responsibility for tracking this gap squarely on the European Commission. Article 15, titled "Monitoring the capacity gap," outlines the Commission's specific duties.

According to Article 15(1), for the purpose of monitoring progress in the achievement of the objectives of the Digital Decade Policy Programme, the Commission shall identify and monitor:

  • The compute capacity available in the Union, including edge computing capacity.
  • The volume of demand for data centre capacity.
  • The size of the capacity gap and underserved areas that could be identified by the Commission, in cooperation with the Member States.

This monitoring is not a passive exercise. Article 15(1)(c) specifies that the Commission will identify underserved areas in cooperation with Member States. These areas are critical because they can subsequently be identified as acceleration zones for the deployment of new data centre capacity. This links the abstract concept of a "gap" to concrete geographic and strategic actions, allowing the EU to target infrastructure investment where it is most needed.

The Strategic Rationale: Recital 44

Recital 44 of the explanatory memorandum provides the essential context for why this monitoring is necessary. It states that "to foster the strategic deployment of data centre capacity across the Union, the Commission should monitor the available compute capacity and the volume of demand for data centre capacity and identify the size of the capacity gap across the Union."

The Recital further explains the utility of this data:

  • Informing Recommendations: "Such monitoring may be used by the Commission to inform its possible recommendations."
  • Addressing the Gap: "To guide Member States in accelerating the deployment of data centre capacity, the Commission may recommend, where appropriate, measures to address the identified Union capacity gap."
  • Reviewing Targets: The monitoring aligns with the Digital Decade Policy Programme 2030, allowing the Commission to "review the digital decade targets to reflect the technical, economic or societal developments and the evolution of the Union's priorities in that regard."

The proposal recognizes that the current landscape is characterized by a pronounced dependence on a limited pool of third-country providers and a geographically concentrated availability of capacity. By monitoring the gap, the EU aims to move from a reactive stance to a proactive, data-driven strategy for infrastructure development.

Linking Monitoring to Action

The identification of the gap under Article 15 is the precursor to the deployment measures found in Title III of the proposal. Once the Commission identifies underserved areas, Member States are empowered to designate data centre acceleration zones under Article 10. These zones are intended to facilitate the rapid deployment of capacity in the specific regions where the gap is most acute.

Furthermore, the monitoring process ensures that the EU's ambition to "triple EU capacity in the next five-to-seven years" (as stated in the explanatory memorandum) is grounded in reality. By continuously tracking the gap, the Commission can assess whether current measures are sufficient or if additional interventions are required to meet the 2035 capacity targets.

What this means for you

For public-sector procurement officers, digital strategy leads, and infrastructure investors, understanding the data centre capacity gap under CADA is crucial for several strategic reasons.

1. Strategic Procurement and Location Planning

As public bodies procure cloud and AI services, you must be aware of the underlying infrastructure constraints. The CADA proposal aims to triple EU data centre capacity, but until that capacity is built, shortages may persist. Being aware of the "underserved areas" identified by the Commission under Article 15 can help you anticipate potential latency issues or availability constraints in specific regions. If your organization requires low-latency access, you may need to align your procurement with regions where the Commission has identified sufficient capacity or where acceleration zones are being established.

2. Alignment with National Strategies

Member States are required to adopt national cloud and AI strategies under Article 7. These strategies must include measures to support the deployment of data centre capacity, informed by the Commission's monitoring. As a procurement officer or strategist, you should ensure that your organization's digital infrastructure plans align with these national strategies, particularly regarding the location and sovereignty of data processing. The national strategies will likely reflect the specific capacity gaps identified in the Commission's monitoring reports.

3. Sovereignty and Assurance Levels

The monitoring of the capacity gap is part of a broader framework to ensure sovereignty. As the EU works to close the gap, it will also enforce stricter sovereignty requirements (Union Assurance Levels) for cloud services used by the public sector. You will need to ensure that your procurement processes can distinguish between providers who meet these assurance levels, as mandated by Articles 16–30 of the proposal. The capacity gap monitoring ensures that the push for sovereignty does not come at the cost of availability; the goal is to close the gap with sovereign providers.

4. Future-Proofing Contracts

With the Commission monitoring demand and supply, there may be shifts in the market as new capacity comes online, particularly in designated acceleration zones. When drafting long-term cloud service contracts, consider clauses that allow for flexibility as the EU's compute capacity landscape evolves. The goal is to reduce reliance on non-European providers, so your procurement decisions should increasingly favor providers who contribute to closing the EU capacity gap, potentially benefiting from the streamlined permitting and support measures in acceleration zones.

Common misconceptions

Misconception 1: The capacity gap only refers to large data centres.

  • Reality: Article 15(1)(a) explicitly includes edge computing capacity in the definition of available compute capacity. The EU recognizes that low-latency applications and AI workloads require distributed computing resources, not just centralized hyperscale facilities. The gap is a holistic measure of all available compute.

Misconception 2: The Commission will build the data centres itself.

  • Reality: The Commission's role under Article 15 is to identify and monitor the gap and identify underserved areas. It may recommend measures, but the actual deployment is driven by Member States, private investors, and data centre operators. The Commission facilitates the environment for this deployment but does not act as the primary builder.

Misconception 3: The gap is a static number.

  • Reality: The gap is a dynamic metric. Article 15 requires ongoing monitoring of both supply and demand. As AI workloads surge and new data centres come online (particularly in acceleration zones designated under Article 10), the size of the gap will change. The Commission's monitoring is intended to be a continuous process to inform policy adjustments and ensure the EU remains on track to meet its 2035 capacity goals.

Misconception 4: Closing the gap is solely about quantity.

  • Reality: While Article 15 focuses on the size of the gap, the broader CADA proposal emphasizes quality and sovereignty. Recital 44 mentions fostering "strategic deployment." This implies that closing the gap isn't just about adding more megawatts, but about deploying capacity that meets EU sovereignty, sustainability, and security standards. The monitoring ensures that the right kind of capacity is being built in the right places.

Official sources

Related

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