The acceptability of data centers
A data center's acceptability is the extent to which a project can be built on a territory without its effects — on energy, water, land and neighbours — exceeding what the community is willing to accept. It is not declared; it is measured, project by project.
Why the question is being asked now
The wave of AI-driven projects concentrates unprecedented demand for electricity, cooling water and land on a handful of territories. A building that asks for a hundred megawatts is not discussed like a warehouse: it commits a region's grid, sometimes a catchment's water, and it settles in for thirty years.
Acceptability has become the question that decides whether a project gets built, moved, or stalls. It rarely turns on the global argument — climate, data — and almost always on something local and concrete: what does this change, here?
Five dimensions, which are our five scoring pillars
- Energy — the electricity drawn by the site, and what the local grid can still give. A substation already at capacity is not duplicated overnight: it is often the grid connection, not the building, that sets a project's schedule.
- Water — the volume consumed for cooling and what is discharged — with what treatment, into what environment. A catchment already under summer stress does not read an abstraction the way an abundant one does.
- Land and biodiversity — the ground the site is built on. Farmland does not carry the same cost as a rehabilitated industrial brownfield: the second repairs, the first removes. Protected areas and the ecological corridors next door add to it.
- Local impact and absorption capacity — what the territory can take. A giga-project in a rural municipality is not the same thing as a compute centre in a city: same power, same noise, but not the same number of residents to absorb it, nor the same economic fabric to benefit from it.
- Transparency and governance — what the developer publishes, and how it involves the territory. A readable file and genuine consultation do not make a good project, but their absence weighs — it is the only pillar about conduct rather than effects.
How it is measured
We give every project two grades from A to E — one for the site, the context it endures and did not choose, one for the project and process, what the operator decides. Each grade comes with a confidence level stating how many sourced elements it rests on.
Missing data never becomes an A: below a coverage threshold we write “insufficient data” instead of a letter. Without that rule, the least transparent site would be the best graded. The calculation is public: the method and the grade, step by step.
Nuisances, the other half of the subject
Acceptability is also decided on what is heard and seen from the street: cooling noise, generator testing, fuel tanks, construction traffic. These are not file details — they are the first grounds for opposition we find in environmental opinions.
We publish them as facts, next to the grade: see data center nuisances.
A normative anchor, not an opinion
We measure standardised indicators — energy efficiency, water usage — in the spirit of the ISO/IEC 30134 series on data center performance indicators. We do not produce a life-cycle assessment: we make sourced facts comparable. See the standards and where we stand.
What acceptability is not
It is not a verdict for or against data centers. A territory can host a heavy project under good conditions, and a small project can be badly placed. We do not say whether to build: we say what this particular place costs, for this particular project, with the same grid for everyone.
See the map and the ranking.
More — why two grades rather than one
A project mixes what it endures — a saturated grid, a stressed catchment, farmland — with what it chooses: its efficiency, its cooling, its transparency. Merging both into a single letter would let an exemplary file buy off a badly chosen site, or the reverse.
Hence the split: an operator can do nothing about the site grade; it is entirely responsible for the project one. An elected official comparing two possible locations looks at the first; a resident judging an operator looks at the second.
More — who decides, and where
A project this size needs a building permit from the municipality, usually an environmental authorisation from the state services, and a grid connection negotiated with the network operator. An environmental authority issues a public opinion on the impact assessment, and the public is consulted.
Nobody in that chain produces a grade comparable from one site to the next: every file is examined alone, in its own district. That gap is exactly what this observatory fills.