Summary As proposed in the Cloud and AI Development Act (CADA), a data centre acceleration zone is a geographic area that a Member State designates to facilitate the development, expansion and modernisation of data centres. Article 10(1) introduces the shorthand term "acceleration zone" and requires a Member State that is deploying data centre capacity to designate at least one zone within its territory, within six months of the Regulation entering into force. Inside a zone, operators would get streamlined permitting (Article 13), a single information point (Article 12) and coordinated energy planning (Article 10(2)), in exchange for meeting harmonised sustainability KPIs and fair-access rules (Article 11). The goal is to let the EU expand computing capacity quickly without lowering environmental standards. CADA is a proposal and not yet in force, so this is what would apply if it is adopted.

Detail

CADA tackles the EU's shortage of computing capacity partly through a supply-side tool in Title III, Chapter I: the data centre acceleration zone. The term itself is introduced in Article 10(1), which abbreviates "data centre acceleration zone" to "acceleration zone". The proposal does not place a standalone definition in the definitions article (Article 2); instead, recital 38 explains the concept — zones "should be designated where the development, expansion and modernisation of data centres may be facilitated", to help "address the Union capacity gap and increase the Union's competitiveness, autonomy and technological resilience, while ensuring compliance with applicable Union law".

What a zone is

A zone is a strategically identified area where public authorities commit to clearing regulatory and infrastructure obstacles to data centre projects. Under Article 10(1), a Member State that is deploying data centre capacity must designate at least one zone within its territory by six months after entry into force. When doing so, Member States "shall consider" eight aspects set out in Article 10(1)(a)–(h):

  • the location and dimension of the site, and the minimum and maximum size of facilities that could be built (a);
  • available and future power grid capacity, and the possibility and conditions for on-site storage and clean energy generation (b);
  • available and future network connectivity capacity (c);
  • the capacity of the zone to support phasing out legacy copper networks (d);
  • available and future facilities that can reuse data centre waste heat (e);
  • all measures taken to accelerate permit-granting for data centres in the zone (f);
  • a preference for reusing brownfield sites over greenfield sites (g);
  • the ability of the site to function sustainably, particularly preventing or minimising environmental impacts and supporting carbon-emission reduction and climate resilience (h).

Why zones are needed

The EU has limited and geographically concentrated compute capacity, which pushes many European workloads onto non-EU infrastructure and creates strategic dependencies. The Commission's explanatory memorandum frames CADA as an effort to "triple EU capacity in the next five-to-seven years and reach the needed capacity by 2035", with balanced geographic deployment. Concentrating effort in designated zones lets Member States plan grid upgrades, secure connectivity and manage environmental impacts more effectively than if data centres were scattered.

How a zone works in practice

The proposal builds several mechanisms around the zone:

  1. Energy planning (Article 10(2)). Where appropriate to facilitate development, Member States would conduct and review at least every three years a comprehensive analysis of the energy needs and greenhouse-gas impacts of current and future zones, and feed it into the network development plans that transmission and distribution system operators prepare under Directive (EU) 2019/944 — encouraging anticipatory grid investment.
  2. Single information point (Article 12). Operators would have a right, on request, to be assisted by a single information point throughout the project lifecycle, covering authorisations from spatial planning and building permits to environmental assessments, water and heat authorisations, and grid connections. The point must pay particular attention to SMEs and, where appropriate, set up a dedicated SME channel (Article 12(4)).
  3. Facilitated permitting (Article 13). Projects in zones would be treated as strategic projects under the forthcoming Regulation on speeding-up environmental assessments (within the meaning of Article 14 of that Regulation, not of CADA). Member States would prepare an aggregated baseline permit per zone, and the permit-granting procedure could not exceed 12 months from a comprehensive application.

Sustainability and fair access

A zone is not a deregulation zone. Article 11(1) requires Member States, when setting sustainability requirements for data centres deployed in zones, to use the key performance indicators specified in Commission Delegated Regulation (EU) 2024/1364 (adopted under the Energy Efficiency Directive, Directive (EU) 2023/1791), Annex II, points (a) to (n). Article 11(2) requires that resource allocation and use within zones be fair, reasonable and non-discriminatory and not give rise to speculative reservation or foreclosure practices capable of impeding effective competition.

What this means for you

For public-sector and procurement officers, zones have practical consequences:

  • Engage early in designation. Your national or regional authorities will be identifying zones; align future public cloud and AI infrastructure needs with them.
  • Expect tighter timelines. With permitting capped at 12 months from a comprehensive application (Article 13(5)), projects can move faster — but the application must be complete and well prepared up front.
  • Coordinate on energy and grid. Anticipatory grid investment (Article 10(2)) means long-term energy planning has to account for the high, dense power demand of data centres.
  • Build in sustainability. Procurement tied to zones should reference the KPIs in Delegated Regulation (EU) 2024/1364 (Article 11(1)).
  • Use the single information point. It can guide you through permits, assessments and grid connections (Article 12), reducing the risk of delay.

Common misconceptions

  • "Zones are only for large hyperscalers." The framework supports a range of providers. Article 12(4) requires single information points to pay particular attention to SMEs and, where appropriate, establish a dedicated SME communication channel.
  • "Designating a zone removes environmental protection." No. Article 10(1)(h) requires the site to be able to function sustainably, and Article 11(1) imposes KPI-based sustainability requirements. Permitting is streamlined for compliant projects, not waived.
  • "A Member State can designate zones without any criteria." Article 10(1) lists eight aspects that Member States "shall consider", so designation is a structured, infrastructure-and-sustainability-driven decision.
  • "All permits are automatic in a zone." They are not. Article 13(4) requires additional permits for activities falling outside the aggregated baseline permit; the baseline permit covers commonly required authorisations but not everything.

Related

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