Climate
Privacy
Bob Dylan
Drones
Data Centers
AI Governance
2026 Maine Senate Race
Data Center Growth Meets Earlier Gatekeeping
This was the week when power queues, water rights, local moratoria, and cost-allocation rules became more visible as front-door risks for AI data center projects.
This was not a week of a single national break in the data center buildout. It was more revealing than that: a week in which the approval environment around large AI and cloud campuses became visibly more front-loaded.
Communities, utilities, courts, and state lawmakers are no longer waiting for projects to reach construction before asking whether the power exists, who pays for the grid, how cooling water will be secured, and whether local zoning is ready for facilities that increasingly resemble major industrial loads.
The demand signal remained intact. But the week made clearer that demand alone is no longer the useful way to understand the sector. The decisive question is becoming whether a project can assemble land, power, water, public consent, and enforceable cost responsibility before opposition or utility constraints harden.
The Week in Context
The clearest pattern of the week was the migration of data center conflict upstream. Seattle approved a one-year moratorium after its power utility flagged five proposed projects totaling about 369 MW of demand. San Marcos, Texas went further, adopting a citywide prohibition. Red Bank, New Jersey banned new data centers and urged a statewide pause; Superior, Wisconsin approved a moratorium even without a pending project; Nashville moved toward a pause around a DC BLOX proposal near the zoo. These were not isolated neighborhood objections. They were local governments deciding that standard zoning and permitting tools may not be adequate for facilities whose impacts arrive through power systems, water systems, noise, backup generation, traffic, and public subsidies.
That distinction matters because it changes where project risk lives. A data center proposal can now encounter meaningful resistance before a full application is filed, before utility service terms are settled, and before environmental review is complete. Walla Walla residents organized against an Amazon-linked site while officials noted that key power and water details were not yet available. Superior acted preemptively. Warren County, Kentucky advanced rules despite having no active project under review. The week’s recurring lesson was that land control increasingly creates visibility before it creates certainty.
The most concrete shift came from Texas, where regulators finalized tougher ERCOT connection standards for data centers and other large loads. Projects will be reviewed in group studies, prioritized partly by development progress, and required to post $50,000 per MW to enter the first Batch Zero study expected in August. That moved the large-load debate from concern to mechanism. It also offered a glimpse of how other regions may handle speculative demand: not by rejecting load growth outright, but by forcing developers to prove maturity, financial commitment, and system readiness earlier.
Power and water also became harder to separate. The Imperial Valley dispute was the clearest example: a proposed 74-acre campus seeking 260 million gallons of Colorado River water annually was also described as a load of up to 330 MW, with Imperial Irrigation District warning that a sudden demand of that size could strain the grid during peak summer heat. Similar connections appeared elsewhere. Utah’s Stratos fight involved water rights and Great Salt Lake concerns; Project Jupiter in New Mexico faced scrutiny in a drought-affected region despite claims around purchased water rights and recycling; North Carolina’s debate moved toward limits on evaporative cooling. The broader point is that water is no longer only a sustainability metric. It is becoming part of entitlement, grid reliability, and local political legitimacy.
Developers are responding, but their workarounds are creating new scrutiny rather than eliminating risk. Reporting from Reuters highlighted Meta-linked development in Ohio paired with off-grid natural gas generation. The DOJ moved to halt or dismiss a Clean Air Act suit over xAI-linked gas turbines in Southaven, Mississippi, citing national security interests tied to AI development. In Florida’s DeSoto County, DCIP Group proposed converting a former natural gas power plant site into a hyperscale data center using behind-the-meter gas generation and closed-loop cooling. These approaches speak to a real constraint: grid access is slow and uncertain. But they also shift attention toward air permits, emissions, local health concerns, and whether self-supplied power is being disclosed and reviewed with enough public visibility.
The politics of the economic bargain also looked more fragile. Loudoun County’s projected nearly $1.3 billion in 2027 data center tax revenue showed why many localities still see the sector as fiscally powerful. But Oregon’s tax-break scrutiny, Hillsboro’s public conflict over data center incentives, Utah’s subsidy backlash, Kansas concerns around incentives and confidentiality, and California polling showing broad local opposition all pointed to the same tension: jobs and tax base are persuasive only when communities believe the public costs are bounded. Where residents fear higher bills, water stress, noise, pollution, or opaque infrastructure commitments, incentives can become evidence against a project rather than support for it.
It would be a mistake to read the week as proof that data center construction is broadly stopping. RMZ Infrastructure’s reported $35 billion plan to scale data center capacity in India to 2-3 GW, Florida’s former-power-plant proposal, and continuing U.S. project activity all showed that capital appetite remains strong. The better reading is more selective: projects are being forced to prove they belong earlier, and jurisdictions with clearer utility rules, existing industrial infrastructure, credible water plans, and predictable local processes may gain an advantage over places where approvals are fast but politically fragile.
What's New
Grid Access Became A More Formal Gate
Texas’s ERCOT rules made the week feel different from prior rounds of concern about load growth. The issue moved from whether data centers strain the grid to how utilities and regulators will ration planning attention, require deposits, and distinguish mature projects from speculative load requests.
Preemptive Local Action Became More Visible
Several jurisdictions acted before projects were fully defined, fully filed, or even pending. Superior’s moratorium without an active proposal, Walla Walla’s early organizing, and Red Bank’s ban all showed local governments trying to set terms before developers lock in momentum.
Water Became More Legal And Operational
The Imperial Valley fight moved water from general concern into litigation and utility planning. Combined with Utah, New Mexico, North Carolina, Texas, and Florida developments, the week showed cooling and water rights becoming front-end entitlement questions.
Outright Exclusion Became Harder To Treat As Fringe
Temporary study pauses remained common, but San Marcos, Red Bank, and Monterey Park showed that some communities are willing to exclude data centers entirely when they see the land-use or infrastructure bargain as unacceptable.
The Buildout Narrative Became More Selective
The week weakened any simple story of either unstoppable expansion or broad shutdown. RMZ’s India plan and Florida’s DeSoto proposal showed continued appetite, while U.S. local actions showed that capacity will increasingly move through jurisdictions with clearer rules and better infrastructure fit.
What's Ongoing
Local Siting Control Remained The Most Persistent Thread
Moratoria, bans, zoning rewrites, petitions, recall efforts, court fights, and public meetings appeared across the week. The common concern was not just whether communities liked data centers, but whether they had enough authority and information to manage facilities with regional-scale resource demands.
Ratepayer Protection Kept Moving Into Formal Policy
California’s SB 886, New York’s proposed service classifications, Michigan customer-protection testimony, Oregon and Wisconsin rate-rule debates, and Texas’s finalized large-load process all reflected a shared question: how to prevent ordinary customers from absorbing grid costs created by hyperscale loads.
Water And Cooling Stayed At The Center Of Siting Risk
From Imperial Valley and Utah to New Mexico, North Carolina, Texas, Nashville, and Florida, water concerns recurred in different forms: rights, withdrawals, wastewater reuse, drought exposure, cooling technology, and whether developer claims can be verified.
Tax Incentives Remained Politically Fragile
Oregon, Utah, Kansas, California, Virginia, and local meetings kept returning to the economic bargain. Data centers can deliver large tax revenue, but those benefits were repeatedly weighed against energy demand, water use, infrastructure costs, and modest permanent employment.
Developers Continued To Offer Technical Mitigation
Closed-loop cooling, wastewater reuse, lower-water systems, scale reductions, former power-plant sites, behind-the-meter generation, and interruptible power all appeared as ways to keep projects viable. The week showed that mitigation helps, but only when communities and utilities see it as enforceable.
Hot Topics
Texas Turned Large-Load Concern Into Operating Rules
The Public Utility Commission of Texas finalized tougher ERCOT connection standards for data centers and other large loads, including group studies, project-maturity prioritization, and a $50,000-per-MW security requirement for early study entry.
Why it mattered
This was the week’s strongest concrete change because it transformed grid anxiety into a screening system. Large AI loads are no longer simply waiting in line; in Texas, they now have to demonstrate seriousness and financial commitment before occupying scarce planning capacity.
Moratoria And Bans Became Normal Planning Tools
Seattle approved a one-year moratorium, San Marcos adopted a citywide ban, Superior approved a preemptive moratorium, Red Bank banned new data centers, Coachella adopted a temporary pause, and Nashville moved toward a pause around the DC BLOX proposal near the zoo.
Why it mattered
The importance was not any one pause. It was the spread of the tactic across different markets and different project stages. Local governments are using blunt tools when they conclude that zoning, utility, and environmental rules are not yet ready for hyperscale demand.
Imperial Valley Linked Water Rights To Grid Stress
A proposed California campus seeking 260 million gallons of Colorado River water annually also raised concerns about a potential 330 MW power load, with Imperial Irrigation District warning of strain during peak summer heat and possible interruptible service.
Why it mattered
The dispute condensed several long-running concerns into one project: water rights, cooling demand, grid reliability, local authority, and the operating assumptions behind AI campuses in arid regions. It showed how water can become a legal and operational threshold, not just a reputational issue.
Dedicated Gas Power Became More Visible
The DOJ’s intervention in the xAI-linked Clean Air Act litigation, Reuters reporting on Meta-linked off-grid gas generation in Ohio, and the DeSoto County proposal using behind-the-meter gas all pointed to dedicated generation as a growing response to constrained grid access.
Why it mattered
Self-supplied power can help developers move around interconnection delays, but the week showed that it also opens another front of conflict. Power workarounds are becoming air-permit, emissions, transparency, and local health questions.
Opposition Routes Were Tested, Not Always Expanded
A Frederick County judge blocked a proposed referendum on a 2,615-acre data center zoning area near Adamstown, while opponents said they would appeal. The ruling came amid broader use of petitions, recalls, public hearings, and voter bans elsewhere.
Why it mattered
The decision was a useful counterweight to the week’s backlash narrative. Local opposition is gaining procedural tools in many places, but not every tactic will survive charter limits, court review, or statutory constraints.
Burning Issues
The week’s issue landscape was unusually coherent. Local authority, power costs, electricity demand, water constraints, and the community-benefit bargain all pointed toward the same larger development: data center approvals are becoming less about whether capacity is desired and more about whether public systems can absorb it on acceptable terms.
Local siting control
Local governments used or considered moratoria, bans, zoning changes, service pauses, and court-tested procedural tools across the week. Seattle, San Marcos, Superior, Red Bank, Coachella, Nashville, Clay, Walla Walla, Manchester Township, and Frederick County all illustrated different versions of the same question: who gets to decide when hyperscale infrastructure fits a community?
Why we noticed
The issue mattered because siting control is now moving before formal approvals mature. Developers face risk not only from permit denials, but from local governments rewriting the rules before applications are complete.
Power cost allocation
The week strengthened the view that data centers will increasingly face special treatment as large-load customers. Texas finalized ERCOT screening rules, California and New York advanced cost-allocation proposals, Michigan’s attorney general sought safeguards in a DTE-Google arrangement, and local meetings repeatedly raised possible bill impacts.
Why we noticed
This issue is moving from public concern into enforceable mechanisms. Deposits, batch studies, special rate classes, customer-funded upgrades, and self-supply expectations can materially alter project economics and site selection.
Water supply constraints
Water concerns became more concrete through the Imperial Valley Colorado River dispute, Utah’s Stratos backlash, New Mexico’s Project Jupiter scrutiny, North Carolina’s cooling legislation, Texas wastewater and cooling debates, and Florida’s closed-loop cooling pitch.
Why we noticed
The week showed water becoming a threshold condition for project credibility. Communities are asking not only how much water a facility uses, but what rights it relies on, how peak cooling works, whether wastewater can be reused, and whether claims are enforceable.
Electricity demand pressure
Electricity demand pressure was visible in Seattle’s utility-driven moratorium, ERCOT’s large-load rules, Avista’s pause on a proposed 500 MW Spokane service request, Imperial Valley’s 330 MW warning, Texas guidance around generation and grid costs, and PJM’s approval to fast-track a limited number of large generation interconnection requests.
Why we noticed
The issue matters because power availability is becoming an approval constraint rather than a back-end service detail. A site can be attractive on land and tax terms yet still fail if the local grid cannot absorb the load without cost, reliability, or political consequences.
Community benefit bargains
The fiscal case for data centers remained powerful but contested. Loudoun County’s projected tax revenue showed the upside, while Oregon’s tax-break scrutiny, Hillsboro’s council conflict, Utah subsidy backlash, Kansas incentive concerns, and California local opposition showed how incentives can become politically vulnerable.
Why we noticed
The week reinforced that the community bargain is no longer settled by capital investment alone. Local acceptance increasingly depends on whether residents believe benefits are durable, local, and large enough to offset power, water, land-use, and infrastructure burdens.
What to Watch
Watch
California’s June 24 Assembly hearing on SB 886 and SB 887, especially whether cost-allocation and CEQA review proposals advance beyond the current backlash moment.
Watch
Governor Kathy Hochul’s decision on New York’s proposed one-year pause on state environmental permits for large data centers.
Watch
Whether Nashville adopts a pause quickly enough to affect the DC BLOX proposal near the Nashville Zoo.
Watch
How the Imperial Valley water-rights dispute develops, and whether Imperial Irrigation District or state officials impose conditions tied to water use, interruptible service, or the proposed 330 MW load.
Watch
Which projects prepare to enter ERCOT’s Batch Zero process, and whether the $50,000-per-MW requirement begins filtering speculative data center load requests.
Final Thought
The week’s evidence points less to a slowdown than to a sorting process. The projects most likely to advance are the ones that can make power, water, cost, and local legitimacy visible before communities decide the risks are being hidden.