Zoning hearings in Tucson, Reno and smaller towns across the American West now fill up with residents holding groundwater charts and utility bills.

At least 75 U.S.

projects worth roughly $130 billion were blocked or delayed in the first quarter of 2026, a total nearly equal to the whole of the previous year.

Active opposition groups climbed from 396 to 833 across 49 states over those same three months.

Reporting on the revolt usually settles on the physical inputs like megawatts, acre-feet, transmission corridors and generator noise.

Most of those objections survive scrutiny.

Sitting underneath them is a question about ownership that gets much less airtime.

Who owns the compute, and who gets to participate in the economy it creates? Costs land inside county lines Every physical burden an A.I.

campus imposes can be mapped inside a county line, starting with water.

Cooling demand in the Phoenix area is on track to rise roughly 870 percent, from 385 million gallons a year to more than 3.7 billion, in a basin where Lake Mead holds about a third of its capacity and Reclamation has already declared a shortage condition.

Electricity impacts are wider, yet still bounded by the reach of the regional grid operator.

Electricity bills for households hundreds of miles from any server hall carry a similar imprint.

Data center demand drove 63 percent of one year’s capacity price increase across the 13-state PJM grid region, or about $9.3 billion recovered from ratepayers, including households and small businesses.

Whatever these buildings produce departs the county almost immediately after it is computed.

Compute belongs to a handful of firms; the weights trained on it stay proprietary; and the revenue books in Seattle, Redmond or Menlo Park.

A county keeps the substation, the truck traffic and a property-tax line frequently discounted in advance by state incentives.

Loosening the co-location rule The physical burdens stay unusually local.

A county 30 miles up the road feels very little of them because the aquifer draw, the substation and the truck traffic all land on whoever sits closest.

Piling more load onto those same few spots looks perverse until you examine what forces the concentration in the first place.

These problems are not true of data centers as such.

They become serious at a certain scale.

A modest site rarely drains an aquifer, moves a regional power market or fills a zoning hall.

So why squeeze as many chips as possible into the same spot, rather than spread them across smaller sites? Several forces pull operators toward enormous single sites, from power contracts to construction economics.

But those constraints can be overcome.

They mainly raise costs, and paying more to spread the chips can look like a reasonable trade once local objections, grid limits and permitting are counted.

The binding constraint on the largest sites is the training of new models.

That one is closer to binary: either there is enough capacity to train a model at the next scale, or there isn’t.

Training a frontier model has typically required thousands of high-end GPUs packed into a single facility.

The algorithms that train these models depend on constant synchronization, with chips exchanging updates at every training step.

That traffic demands ultra-low latency and massive bandwidth, which traditionally exist only inside one tightly networked building.

That is why A.I.

data centers have grown so large, and why they are now pressing against the physical limits of how many chips can sit in one place.

That requirement is starting to loosen.

In 2023, Google DeepMind researchers showed that machines in separate locations could train a model just as well while exchanging roughly....