Summary The proposed Cloud and AI Development Act (CADA) does not pre-select specific sites in Austria. As proposed in Article 10, where data centre capacity is being deployed in its territory, Austria would have to designate at least one data centre acceleration zone within six months of the Regulation's entry into force. The location would be chosen against the aspects in Article 10(1)(a)–(h) — grid capacity, network connectivity, waste-heat reuse, a preference for brownfield over greenfield sites and sustainability, among others. Once designated, Article 11 requires Austria to set sustainability requirements using the key performance indicators in Delegated Regulation (EU) 2024/1364 and to allocate resources on fair, reasonable and non-discriminatory terms.

Detail

CADA, COM(2026) 502 final, is a proposed Regulation introducing a harmonised framework to accelerate sustainable computing capacity across the EU. For Austria, the most concrete operational effect would be the designation of "data centre acceleration zones" — specific areas where infrastructure planning is prioritised and permitting is streamlined. Where these zones would physically sit in Austria is not fixed by CADA; it would be determined by the Austrian authorities applying the Article 10 criteria.

The obligation to designate: Article 10

As proposed in Article 10(1), where data centre capacity is being deployed within the territory of a Member State, that Member State "shall designate at least one data centre acceleration zone" within six months of entry into force. The obligation is conditional on actual deployment activity. When designating, Austria would consider the following aspects:

  • Site location and dimension, including the minimum and maximum size of facilities that could be built (Article 10(1)(a)).
  • Current and future power-grid capacity, and the possibility and conditions for on-site storage and clean-energy generation (Article 10(1)(b)).
  • Current and future network connectivity capacity (Article 10(1)(c)).
  • Capacity to support phasing out legacy copper networks (Article 10(1)(d)).
  • Facilities that can reuse data centre waste heat (Article 10(1)(e)) — relevant where district-heating networks could absorb it.
  • Measures taken to accelerate permitting for constructing and operating data centres in the zone (Article 10(1)(f)).
  • A preference for reusing brownfield sites over greenfield sites (Article 10(1)(g)).
  • The site's ability to function sustainably, particularly preventing or minimising environmental impacts and supporting carbon-emission reductions and climate resilience (Article 10(1)(h)).

Article 10(2) adds that, where appropriate, Austria 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 ensure that the network development plans prepared by transmission and distribution system operators take that analysis into account, considering anticipatory investments. Article 10(3) requires authorities responsible for spatial and development plans to consider including provisions for data centre projects in zones, and where those plans are subject to assessment under Directive 2001/42/EC and Article 6 of Directive 92/43/EEC, those assessments are to be combined. Article 10(4) requires coordination among all relevant national, regional and local authorities, including telecoms operators and transmission and distribution system operators.

Conditions within zones: Article 11

Sustainability. As proposed in Article 11(1), when setting sustainability requirements for data centres in acceleration zones, Member States "shall use the key performance indicators specified in Delegated Regulation (EU) 2024/1364" (adopted under the Energy Efficiency Directive (EU) 2023/1791), Annex II, points (a) to (n). For Austrian operators, this ties zone-level sustainability obligations to EU-wide metrics.

Fair, reasonable and non-discriminatory access. Article 11(2) requires that the allocation and use of resources within zones take place on fair, reasonable and non-discriminatory terms and not give rise to speculative reservation or foreclosure practices capable of impeding competition or the effective development or use of the zones. The reference to "speculative reservation" is significant: it targets the practice of locking up scarce inputs — land, grid connection capacity, fibre routes — without building, which can otherwise stall a zone. The provision does not prescribe a single allocation mechanism, leaving Austria room to choose how to police it, but it sets the outcome that the chosen mechanism must achieve.

The single information point: Article 12

Under Article 12(1), a data centre operator has the right, on request, to be assisted by a single information point throughout the entire lifecycle of a project in an acceleration zone, in respect of all the authorisations required for deployment. Austria would designate one or more such points. This one-stop function is the practical counterpart to the aggregated baseline permit under Article 13: rather than navigate spatial, building, environmental, water, heat and grid-connection procedures separately, the operator routes its interactions through a single contact tasked with assisting across the project lifecycle.

What this means for you

For CTOs, architects and SMEs assessing CADA's practical impact in Austria, the designation of acceleration zones would be both a constraint and an opportunity.

1. Site selection. Anticipate that Austria would publish its designated zone(s) within six months of entry into force. Areas meeting the Article 10(1) aspects — strong grid capacity, connectivity and waste-heat reuse — would be the ones to benefit from streamlined permitting. The brownfield preference in Article 10(1)(g) may make brownfield sites the path of least resistance.

2. Permitting timelines. Article 13 provides that data centre projects in acceleration zones are treated as strategic projects under the proposed Regulation on speeding-up environmental assessments, that each zone receives an aggregated baseline permit (Article 13(2)–(4)), and that the permit-granting procedure must not exceed 12 months from a comprehensive application (Article 13(5)), without prejudice to shorter national limits. The baseline permit is prepared at zone level after Austria carries out the necessary zone-level assessments (Article 13(3)), and projects then need additional permits only for activities falling outside it (Article 13(4)). Two consequences for planning: the "comprehensive application" is what starts the 12-month clock, so a complete, well-evidenced submission is your main lever over timeline; and you should map early which of your requirements are installation-specific and therefore fall outside the baseline permit.

3. Sustainability compliance. Article 11(1) ties your sustainability metrics to Delegated Regulation (EU) 2024/1364; benchmark current and planned facilities against those KPIs early.

4. Competitive access. The prohibition on speculative reservation and foreclosure in Article 11(2) is a safeguard for smaller operators — but you must ensure your own reservations are genuine and timely.

5. Engagement. Article 10(4) requires coordination among national, regional and local authorities and with grid and telecoms operators. Engaging during consultation, with data on your connectivity, energy and waste-heat profile, can help shape the zone that hosts you.

6. Sustainability is a gate, not a label. Because Article 11(1) binds zone sustainability requirements to the KPIs in Delegated Regulation (EU) 2024/1364 (points (a) to (n) of its Annex II), the metrics that matter — covering energy, water and related indicators under the Union data centre rating framework — are fixed at EU level rather than negotiable locally. Design and report against those KPIs from the outset; retrofitting measurement after a facility is built is far costlier than building it in.

Why the planning integration in Article 10(3) and (4) matters

Two procedural features make the difference between a zone that exists on paper and one that actually accelerates deployment. First, Article 10(3) pulls data centre provisions into national, regional and local spatial and development plans and, where Directive 2001/42/EC (strategic environmental assessment) and Article 6 of Directive 92/43/EEC (Habitats) apply, requires the relevant assessments to be combined — and, where applicable, to address impacts on water bodies under Directive 2000/60/EC. Combining assessments at zone level is what allows the later, project-level baseline permit under Article 13 to be issued quickly. Second, Article 10(4) requires Austria to coordinate among all relevant national, regional and local authorities and with telecoms, transmission and distribution system operators when designating zones. For an operator, this coordination is the reason a designated zone should come with grid and connectivity headroom already considered, rather than discovered late.

Common misconceptions

"All data centres in Austria will be inside acceleration zones." Article 10 requires designating at least one zone where capacity is being deployed; it does not confine all data centre activity to zones. Projects outside a zone simply would not get the zone-specific facilitations.

"Acceleration zones override national environmental law." Article 10(1)(h) expressly requires the site to function sustainably and minimise environmental impacts; the proposal combines assessments (Article 10(3)) rather than disapplying environmental protections.

"Brownfield sites are mandatory." Article 10(1)(g) states a preference for brownfield over greenfield; it is not a ban on greenfield development.

"Designation happens automatically." Designation is an active administrative act required within six months of entry into force, involving analysis, coordination and formal designation.

Related

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