Should Water Availability Become Part of Data-Center Permitting?

Photo: Jet Lowe, Wikimedia Commons, Public domain

01 A demand curve nobody modeled

The question sounds mundane until the numbers land. A large hyperscale campus using evaporative cooling can consume on the order of a million gallons of water a day at peak — over a year, a figure comparable to a small town. Unlike electricity, which a utility can buy from anywhere on the grid, cooling water is drawn from a specific aquifer, river, or reservoir, in a specific county, on days when that county is often in drought. Yet in most U.S. jurisdictions, water supply has not traditionally been a standard condition of data-center permitting: rezonings and special-use permits turn on traffic, noise, and power availability, while water is assumed to follow.

That assumption is cracking. AI's training clusters concentrate heat loads in fewer, bigger buildings, and the load forecasts that startled Georgia and Virginia utility regulators translate into cooling demand nobody's local water plan priced in. As EarthX framed it in an April 2026 session on water agreements for data-center growth, the conversation has moved past whether a permit issues to on what hydrological terms.

Analysis — not prediction. N43 and Hermes AI grounds every scenario in the documented record and verified reporting as of September 21, 2026; where evidence is incomplete we say so.

02 Three cooling strategies, three water signatures

Evaporative cooling remains the workhorse because it is cheap: water absorbs heat by vaporizing, and the tower blows it off as steam, consuming roughly one to two gallons per kilowatt-hour of heat rejected in typical designs. Closed-loop systems recirculate a fixed charge through chillers and dry coolers, losing only small top-off amounts — but they use more electricity, which shifts the water burden upstream to the power plant. Liquid immersion submerges servers in dielectric fluid, replacing most consumptive use entirely, at a cost premium and an operations regime most facilities have not adopted. Dry air cooling approaches zero consumption outright, at the highest energy and capital cost of all.

The engineering tradeoff is therefore a transfer of scarcity between water and energy, and it is priced locally. In Phoenix, where electricity is plentiful and water is not, the calculus differs from Northern Virginia, where power is the binding constraint and the Potomac watershed looks generous until a drought year. A permitting regime that ignores which side of that ledger a county sits on will systematically approve the wrong cooling design for its own geography.

03 Arizona, Georgia, Virginia: the stress map

The stress cases are documented. In Maricopa County, Arizona, approvals for large data-center projects have proceeded even as the state's own water department has for decades refused to certify new assured water supplies dependent purely on groundwater around Phoenix — recorded aquifer declines and the 2023 Phoenix Active Management Area finding made the mismatch explicit. In Georgia, the fight over a utility's load-growth forecast in 2024 pulled data-center water demand into the open; in Loudoun County, Virginia, supervisors have tied approvals to commitments on utility water capacity. Local officials who once rubber-stamped rezonings now ask for hydrological findings the applicant never budgeted for.

Some jurisdictions have gone further than conditions: moratoria and de facto pauses on new approvals pending water studies have appeared in county-level debates across the boom belt, from the Atlanta exurbs to the high desert. The precedent being set is that water availability — like sewer capacity and road concurrency — can be a concurrency requirement: no certified supply, no building permit.

04 The pledge era and its limits

The industry's answer has been the water-positive pledge. Microsoft has promised water positivity — replenishing more than it consumes — by 2030; Google has pledged 120 percent replenishment; Amazon and Meta have net-positive commitments of their own. These are real programs funding wetland restoration, leak repair in municipal systems, and aquifer recharge. But a replenishment project in a distant watershed does not refill the aquifer under the county that just approved the campus, and permit negotiations are increasingly refusing to accept offset geography as a substitute for local supply.

There is also a measurement gap the pledges expose. Water-use effectiveness varies wildly by climate and season, corporate disclosures report it unevenly, and a county engineer usually cannot reconcile a company-wide replenishment claim with a site-level consumption estimate. The predictable result is a push toward site-level water budgets written into permits — metered, reported, and enforceable the way wastewater discharges already are.

05 Dry cooling and the capex premium

The technology to remove water from the equation exists; what is missing is agreement on who pays for it. Dry and hybrid cooling carry a meaningful capital and operating premium — more fans, more chillers, more electricity per kilowatt of compute, and degraded efficiency on the hottest days, precisely when AI clusters run hardest. Immersion plumbing adds construction complexity that operators say complicates the rapid server-refresh cycles AI economics demand. For a campus in a water-rich basin, that premium buys little; for one over a stressed aquifer, it is the cost of a license to operate.

That asymmetry is why a uniform national rule is the wrong shape. The efficient design is local water-cost pass-through: counties that price their hydrology accurately let applicants choose — cheap evaporative designs where water is abundant, dry systems where it is not. The risk is the opposite failure mode, in which thirsty jurisdictions race to the bottom and approve evaporative campuses precisely where they can least afford them, because the tax revenue arrives years before the aquifer bill does.

06 What a water-aware permitting regime would say

A workable regime would need four elements, none exotic. A certified water budget for the facility, stated in gallons per day at design load, as a permit condition. Metered reporting to the local utility, the way effluent is reported now. A concurrency trigger — approvals pause when the basin's safe yield is fully allocated, with recharge credits counted only inside the same basin. And a cooling-design disclosure, so the county knows whether it is approving a water consumer or an electricity consumer before the concrete pours.

The deeper question is whether water follows power as the second resource crisis of the AI buildout, or the first one that gets solved before it becomes one. The permitting wars over electricity took nearly a decade of grid queues and rate shocks before regulators began reforming interconnection. Water has an advantage: it is governed locally, by the same boards that sign the rezonings. If counties use the leverage they already hold, water availability becomes part of data-center siting not by federal mandate but by the ordinary arithmetic of a permit hearing — no supply, no signature.