Grassroots Revolt Against Data Centers Goes National: Water Use Now the Flashpoint

Over the last two weeks, grassroots opposition to data centers has moved from sporadic local skirmishes to a recognizable national pattern. While earlier fights centered on land use, noise, and tax incentives, the current phase is more focused and more dangerous for developers: water.

Across multiple states, residents are demanding to see the “water math” behind proposed data centers—how much water will be consumed (not just withdrawn), where it will come from, whether utilities can actually supply it during drought conditions, and what enforceable reporting and mitigation requirements will apply. In arid regions, water scarcity is an obvious constraint. But what’s new is that even in traditionally water-secure states, opponents are now framing data centers as industrial-scale consumptive users whose needs collide directly with residential growth, agriculture, and climate volatility.

The result: moratoria, rezoning denials, delayed hearings, task forces, and early-stage organizing efforts aimed at blocking projects before entitlements are locked in.

Below is a snapshot of how that opposition has played out state by state over the last two weeks.

State-by-State Breakdown

Virginia  

Virginia remains ground zero for organized pushback.

Botetourt County: Residents confronted the Western Virginia Water Authority over a proposed Google data center, pressing officials about long-term water supply impacts and groundwater sustainability.  

Hanover County (Richmond region): The Planning Commission voted against recommending rezoning for a large multi-building data center project.  

State Legislature: Lawmakers are advancing reform proposals that would require water-use modeling and disclosure.

Georgia  

Metro Atlanta / Middle Georgia: Local governments’ recruitment of hyperscale facilities is colliding with resident concerns.  

DeKalb County: An extended moratorium reflects a pause-and-rewrite-the-rules strategy.  

Monroe County / Forsyth area: Data centers have become a local political issue.

Arizona  

The state has moved to curb groundwater use in rural basins via new regulatory designations requiring tracking and reporting.  

Local organizing frames AI data centers as unsuitable for arid regions.

Maryland  

Prince George’s County (Landover Mall site): Organized opposition centered on environmental justice and utility burdens.  

Authorities have responded with a pause/moratorium and a task force.

Indiana  

Indianapolis (Martindale-Brightwood): Packed rezoning hearings forced extended timelines.  

Greensburg: Overflow crowds framed the fight around water-user rankings.

Oklahoma  

Luther (OKC metro): Organized opposition before formal filings.

Michigan  

Broad local opposition with water and utility impacts cited.  

State-level skirmishes over incentives intersect with water-capacity debates.

North Carolina  

Apex (Wake County area): Residents object to strain on electricity and water.

Wisconsin & Pennsylvania 

Corporate messaging shifts in response to opposition; Microsoft acknowledged infrastructure and water burdens.

The Through-Line: “Show Us the Water Math”

Lawrence of Arabia: The Well Scene

Across these states, the grassroots playbook has converged:

Pack the hearing.  

Demand water-use modeling and disclosure.  

Attack rezoning and tax incentives.  

Force moratoria until enforceable rules exist.

Residents are demanding hard numbers: consumptive losses, aquifer drawdown rates, utility-system capacity, drought contingencies, and legally binding mitigation.

Why This Matters for AI Policy

This revolt exposes the physical contradiction at the heart of the AI infrastructure build-out: compute is abstract in policy rhetoric but experienced locally as land, water, power, and noise.

Communities are rejecting a development model that externalizes its physical costs onto local water systems and ratepayers.

Water is now the primary political weapon communities are using to block, delay, and reshape AI infrastructure projects.

Read the local news:

America’s AI Boom Is Running Into An Unplanned Water Problem (Ken Silverstein/Forbes)

Residents raise water concerns over proposed Google data center (Allyssa Beatty/WDBJ7 News)

How data centers are rattling a Georgia Senate special election (Greg Bluesetein/Atlanta Journal Constitution)

A perfect, wild storm’: widely loathed datacenters see little US political opposition (Tom Perkins/The Guardian) 

Hanover Planning Commission votes to deny rezoning request for data center development (Joi Fultz/WTVR)

Microsoft rolls out initiative to limit data-center power costs, water use impact (Reuters)

Taxpayer-Backed AI? The Triple Subsidy No One Voted For

OpenAI’s CFO recently suggested that Uncle Sam should backstop AI chip financing—essentially asking taxpayers to guarantee the riskiest capital costs for “frontier labs.” As The Information reported, the idea drew immediate pushback from tech peers who questioned why a company preparing for a $500 billion valuation—and possibly a trillion-dollar IPO—can’t raise its own money. Why should the public underwrite a firm whose private investors are already minting generational wealth?


Meanwhile, the Department of Energy is opening federal nuclear and laboratory sites—from Idaho National Lab to Oak Ridge and Savannah River—for private AI data centers, complete with fast-track siting, dedicated transmission lines, and priority megawatts. DOE’s expanded Title XVII loan-guarantee authority sweetens the deal, offering government-backed credit and low borrowing costs. It’s a breathtaking case of public risk for private expansion, at a time when ordinary ratepayers are staring down record-high energy bills.

And the ambition goes further. Some of these companies now plan to site small modular nuclear reactors to provide dedicated power for AI data centers. That means the next generation of nuclear power—built with public financing and risk—could end up serving private compute clusters, not the public grid. In a country already facing desertification, water scarcity, and extreme heat, it is staggering to watch policymakers indulge proposals that will burn enormous volumes of water to cool servers, while residents across the Southwest are asked to ration and conserve. I theoretically don’t have a problem with private power grids, but I don’t believe they’ll be private and I do believe that in both the short run and the long run these “national champions” will drive electricity prices through the stratosphere—which would be OK, too, if the AI labs paid off the bonds that built our utilities. All the bonds.

At the same time, Washington still refuses to enforce copyright law, allowing these same firms to ingest millions of creative works into their models without consent, compensation, or disclosure—just as it did under DMCA §512 and Title I of the MMA, both of which legalized “ingest first, reconcile later.” That’s a copyright subsidy by omission, one that transfers cultural value from working artists into the balance sheets of companies whose business model depends on denial.


And the timing? Unbelievable. These AI subsidies were being discussed in the same week SNAP benefits are running out and the Treasury is struggling to refinance federal debt. We are cutting grocery assistance to families while extending loan guarantees and land access to trillion-dollar corporations.


If DOE and DOD insist on framing this as “AI industrial policy,” then condition every dollar on verifiable rights-clean training data, environmental transparency, and water accountability. Demand audits, clawbacks, and public-benefit commitments before the first reactor breaks ground.

Until then, this is not innovation—it’s industrialized arbitrage: public debt, public land, and public water underwriting the private expropriation of America’s creative and natural resources.