The Associated Press reports that governors’ races across the United States are being increasingly buffeted by what it calls the toxic politics of data centers. The facilities that power the AI and cloud economy — and the electricity, water, and land they consume — have moved from zoning-board obscurity to the center stage of statewide campaigns.
Executive Summary
According to AP’s reporting, data centers have crossed a political threshold: they are no longer a local land-use question decided quietly by county boards, but a statewide campaign issue that candidates for governor are being forced to answer for. The word choice matters — ‘toxic’ signals that the issue now carries more downside than upside for politicians, regardless of party.
For the infrastructure industry, this is a material shift in the operating environment. Governors appoint utility commissioners, sign or veto tax-incentive legislation, and set the tone for state permitting agencies. When the people seeking that office campaign against — or hedge on — data center growth, the political risk premium on every new site goes up. Siting risk, long treated as a paperwork problem, is becoming an electoral one.
From Zoning Boards to the Ballot Box
For most of the industry’s history, data center approvals were decided in county planning meetings that almost nobody attended. The AI build-out changed the scale of the ask: modern campuses draw utility-grade electricity, meaningful volumes of water for cooling, and large tracts of land, often near residential areas. That scale made the facilities visible, and visibility made them political. AP’s framing — governors’ races ‘buffeted’ by the issue — captures the escalation: the debate has jumped two levels of government, from town hall to statehouse.
The mechanism is straightforward. Residents connect rising electricity bills, strained grids, and changed landscapes to the server farms appearing nearby, and they take that frustration to the most visible official on the ballot. Candidates then face a bad trade: embrace data centers and own the utility-bill anger, or oppose them and own the lost jobs and tax revenue. That no-win structure is what makes an issue ‘toxic’ in campaign terms.
Why Governors Matter More Than Mayors
A hostile county board can kill one project; a hostile governor can reshape an entire state’s pipeline. Governors influence public utility commissions that decide who pays for grid upgrades, sign the tax-abatement packages that make site economics work, and direct the environmental agencies that issue water and air permits. If campaigning against data centers proves to be a winning message, the policy consequences will outlast any single election cycle.
The economics compound the risk. Data centers are decade-scale capital commitments made against assumptions about power pricing, tax treatment, and permitting timelines. An election that flips a state from courting the industry to constraining it can strand those assumptions mid-project. Operators and their investors now have to underwrite political volatility the way they underwrite grid interconnection queues.
Winners, Losers, and the Flight to Friendly Ground
The likely near-term effect is sorting. Capital will tilt toward jurisdictions where the political climate is settled — states, and increasingly specific utility territories, where community benefit agreements, transparent power-cost allocation, and water-efficient designs have kept the backlash manageable. States where data centers become a campaign punching bag risk watching projects, and the associated construction jobs and tax base, route around them.
The industry’s own conduct will help decide which column each state lands in. Secretive land assemblies, non-disclosure agreements around utility deals, and cost-shifting onto residential ratepayers are the fuel of the backlash. Operators that show up early, disclose resource demands, pay their full share of grid costs, and design for minimal water draw are effectively buying political insurance. In an environment where a governor’s race can reprice a state’s entire pipeline, that insurance is no longer optional.
Background
Data centers are the physical backbone of the internet, cloud computing, and artificial intelligence — warehouse-scale buildings full of servers that require enormous amounts of electricity and, in many designs, water for cooling. For two decades states actively courted them with tax incentives, prizing their construction jobs and property-tax revenue while their modest visibility kept public attention low.
The generative-AI boom broke that equilibrium. Facilities grew from tens of megawatts to campus-scale power draws rivaling heavy industry, land acquisitions became front-page news in host communities, and questions about who pays for grid expansion landed on residential utility bills. The AP’s report marks the point at which that accumulated friction became statewide electoral politics.
MIT News reported on June 9, 2026, that a startup spun out of the university is commercializing a data-center cooling system inspired by the passive heat-removal designs used in nuclear reactors, with the stated goal of making data centers more sustainable by reducing the energy — and, per the editorial framing, the water — that cooling consumes.
The syndicated release available to us carried the headline and framing but few technical or commercial specifics; we analyze the concept on its merits and flag what remains unsubstantiated below.
Executive Summary
The announcement matters because cooling is one of the largest costs — in electricity, in water, and increasingly in permitting friction — of operating a data center. A system that borrows from nuclear engineering’s passive-safety playbook, where heat is removed by natural physical forces rather than powered machinery, is aimed squarely at that cost. In a reactor, passive cooling means hot fluid rises and cooler fluid sinks, circulating heat away without pumps; the appeal for data centers is the same: fewer energy-hungry moving parts between the hot chip and the outside air.
The timing is not accidental. AI training and inference hardware has pushed per-rack power to levels that conventional air cooling struggles to handle, and communities hosting data centers are scrutinizing water withdrawals from evaporative cooling systems. Any credible technology that reduces both the electric and water bills of heat rejection will get a hearing from operators.
What the source material does not yet establish is whether this particular system works at commercial scale: no performance figures, customer deployments, funding details, or timelines were available in the release we reviewed. The physics pedigree is real; the commercial case is, for now, a thesis.
From Reactor Safety to Server Racks
Nuclear plants pioneered passive cooling for a stark reason: a reactor must shed heat even when the power fails. Designs built on natural circulation exploit the fact that heated fluid becomes less dense and rises while cooled fluid sinks, creating a self-sustaining loop that moves heat with no pumps, no fans, and no operator action. Decades of licensing scrutiny have made these principles among the most carefully validated in thermal engineering.
A data center’s problem is gentler — servers fail safely when they overheat, reactors do not — but structurally similar: concentrated heat that must move continuously to the outdoors. Today that journey is powered at nearly every step, by server fans, chilled-water pumps, compressors, and cooling towers. A passive or semi-passive loop that lets buoyancy or phase change do part of that work attacks the electricity bill directly, and if it rejects heat without evaporating water, it attacks the water bill too. The startup’s bet, as framed by MIT News, is that reactor-grade thermal design can be repackaged at data-center price points.
Why Cooling Is the Data Center’s Second Power Bill
For a typical facility, the electricity that does computing is only part of the meter; a meaningful share of total load goes to moving heat, which is why the industry obsesses over power usage effectiveness (PUE) — the ratio of total facility power to IT power. Every point of cooling overhead removed either cuts operating cost or frees grid capacity for more servers, and grid capacity is currently the scarcest input in the AI buildout.
Water is becoming the second constraint. Many large facilities cool cheaply by evaporating water, and withdrawals have become a flashpoint in drought-prone regions, slowing permits and souring community relations. A technology that credibly reduces both energy and water use would not just trim costs — it would widen the map of places a data center can be built. That is the strategic prize behind this announcement, and it explains why a cooling story from a university lab merits industry attention.
A Crowded Race, and a Conservative Customer
The spinout is not entering an empty field. Direct-to-chip liquid cooling is already shipping at scale from established vendors, immersion cooling has committed adopters, and rear-door heat exchangers are a common retrofit. Most of these still depend on pumped loops and mechanical chillers, so a passive approach is differentiated in principle — but it must prove it can handle the extreme heat density of modern AI racks, where natural circulation alone has historically been hardest to apply.
The harder obstacle may be cultural. Data-center operators are deeply conservative buyers: uptime is the product, and unproven thermal systems are among the last things they will gamble on. The path for a startup here almost always runs through small pilot deployments, published performance data, and partnerships with equipment incumbents or colocation providers willing to host a proving ground. None of those milestones is evidenced in the material released so far, which is normal for a lab-to-market story at this stage — but it defines exactly what to watch for next.
Background
Data-center cooling has been through several generations: raised-floor air cooling, hot/cold aisle containment, evaporative economization, and most recently liquid cooling driven by AI accelerators whose heat output overwhelms air. Each generation traded capital cost against energy and water consumption, and the AI era has sharpened that trade-off — power and water availability now routinely determine where facilities can be built at all.
Nuclear engineering, meanwhile, spent decades perfecting passive heat removal for safety reasons, producing some of the most rigorously validated thermal designs in existence. The MIT spinout profiled here sits at the intersection of those two histories, part of a broader wave of university-born startups applying energy-sector engineering to computing infrastructure.
Microsoft’s chief executive said the company’s newest AI data centers consume as little water annually as a typical restaurant, crediting a closed-loop cooling design that recirculates the same fluid indefinitely rather than evaporating fresh water to reject heat. The claim, reported June 3, 2026, positions the design as a step-change from conventional facilities that can draw millions of gallons per year.
Executive Summary
The comparison is striking by design: restaurants are among the most water-intensive small businesses people intuitively understand, and equating a hyperscale AI facility to one reframes the water debate around data centers. The engineering behind the claim is real and well understood — closed-loop (or liquid-to-chip, sealed-circuit) cooling fills the system once and rejects heat to the outside air through dry coolers or chillers, eliminating the continuous evaporation that makes traditional cooling towers thirsty.
Why it matters: water has become a genuine siting constraint for AI infrastructure. Communities from the American Southwest to drought-prone regions abroad have pushed back on data center projects over aquifer draw, and utilities increasingly ask about consumptive water use before power. If Microsoft can credibly demonstrate restaurant-scale water budgets at gigawatt-scale campuses, it changes the permitting conversation for the whole industry.
The caveat: the claim as reported applies to new facilities built to the closed-loop design, not Microsoft’s existing fleet, and the reported remarks do not specify how many sites qualify, how the restaurant benchmark is defined, or whether the figure counts the water embedded in the extra electricity that dry heat rejection typically requires.
The Engineering Is Credible — the Accounting Is the Question
Closed-loop cooling is not a moonshot; it is a design choice with known trade-offs. In a conventional data center, cooling towers chill water by evaporating a portion of it — that evaporation is the “consumption” that shows up in the millions-of-gallons figures. A sealed circuit avoids this entirely: coolant is filled at commissioning, circulates across cold plates or heat exchangers at the servers, and dumps heat to ambient air. On-site water use then falls to domestic needs — restrooms, humidification, kitchens — which is plausibly restaurant-scale.
The honest question is boundary-drawing. Site water use is only one ledger. Dry heat rejection generally consumes more electricity than evaporative cooling, especially in hot climates, and most grid electricity has its own water footprint at the power plant. A facility that saves water on site but draws more thermally generated power may shift consumption upstream rather than eliminate it. The reported remarks, as relayed, do not say whether Microsoft’s restaurant comparison is site-only or includes that indirect water. Neither answer would be wrong — but they are very different claims.
Water Is Becoming the Second Currency of AI Siting
For years, the binding constraint on data center development was power: megawatts available, interconnection queue position, substation timelines. Water has quietly become the second gate. Local opposition to AI campuses increasingly centers on aquifer and municipal-supply impacts, and several jurisdictions now require consumptive-use disclosures in permitting. A hyperscaler that can walk into a county hearing with a restaurant-equivalent water budget has a materially easier approval path — and that is worth real money in schedule terms, since permitting delay is often costlier than construction premium.
This creates competitive dynamics beyond Microsoft. If closed-loop designs become the de facto community expectation, operators running evaporative plants may face pressure to retrofit or to defend designs that were unremarkable five years ago. Cooling vendors, dry-cooler manufacturers, and liquid-cooling integrators stand to gain; regions that marketed abundant water as a siting advantage lose a differentiator.
Marketing Benchmarks Deserve the Same Scrutiny as Critics’ Numbers
The water debate around AI has featured loose numbers on all sides — viral estimates of water “per chatbot query” have often rested on contested assumptions, and industry rebuttals have sometimes cherry-picked their best sites. A restaurant comparison is vivid but imprecise: restaurant water use varies enormously by size and type, and the reported claim does not state which benchmark Microsoft used. The fair posture is symmetrical skepticism. Critics’ worst-case figures should be tested against actual metered data; Microsoft’s best-case figure should be tested against fleet-wide averages, third-party verification, and the full indirect footprint. Until per-site water data is published, both the alarm and the reassurance rest partly on trust.
Background
Microsoft is one of the largest builders of AI infrastructure in the world, expanding data center capacity at historic pace to serve AI training and cloud workloads. The company has long publicized environmental commitments — including goals around water stewardship — and in recent years began promoting data center designs that minimize or eliminate evaporative water use, as rising rack densities pushed the industry from air cooling toward liquid cooling.
The water question grew alongside the AI boom: as hyperscale campuses multiplied in water-stressed regions, consumptive use became a flashpoint in local permitting battles and media coverage. The June 2026 remarks land in that context — an industry seeking to prove that AI growth and water stewardship are compatible, before regulators decide the question for it.
Utah’s governor has tightened the rules that apply to a giant AI data center project backed by investor Kevin O’Leary, according to a Business Insider report published May 30, 2026. The action places state-level conditions on one of the highest-profile celebrity-backed entries into the AI infrastructure race.
Details of the specific requirements were not spelled out in the available source material, but the reported move fits a broader pattern: states courting AI data center investment are simultaneously attaching guardrails around the resources those campuses consume — chiefly water and electric power.
Executive Summary
According to Business Insider, Utah’s governor moved to tighten the rules governing Kevin O’Leary’s planned large-scale AI data center in the state. O’Leary, the investor best known from Shark Tank, has spent the past two years positioning O’Leary Ventures as a developer of very large AI computing campuses, most prominently the multibillion-dollar ‘Wonder Valley’ concept announced in Alberta, Canada, in late 2024. A Utah project extends that ambition into one of the fastest-growing — and driest — states in the American West.
Why it matters: AI data centers are among the most resource-intensive facilities ever built at commercial scale. A single hyperscale campus can demand hundreds of megawatts of electricity — comparable to a small city — and, depending on cooling design, substantial water. Utah is an arid state where water politics are already charged, notably around the shrinking Great Salt Lake. When a governor personally intervenes to condition a marquee project, it tells the industry that resource guardrails are moving from county zoning boards up to the statehouse.
For developers, the message is that incentives and permits increasingly come bundled with obligations. For AI tenants and investors, it means project timelines and economics now carry a regulatory variable that did not meaningfully exist three years ago.
Guardrails Are Becoming the Price of Admission
Through 2023 and 2024, states competed for data centers almost purely with carrots: tax abatements, fast-track permitting, cheap land. The reported Utah action reflects the next phase. Legislatures and governors in Georgia, Virginia, Texas, and elsewhere have begun asking who pays for the grid upgrades a gigawatt-class campus requires, and whether existing ratepayers end up subsidizing a private tenant’s load. Utah itself passed legislation in 2024 creating a framework for ‘large load’ customers to be served under separate terms, precisely so that massive new consumers do not shift costs onto households. Tightening rules on a flagship AI project is consistent with that trajectory: welcome the investment, but ring-fence its externalities.
For laypeople, the key concept is that electricity and water are shared systems. A data center does not simply buy power the way a household does; at hundreds of megawatts it reshapes the utility’s entire planning horizon — what plants get built, what transmission lines get strung, and who bears the cost if the promised load never materializes.
Water Is the West’s Hard Constraint
Power can, eventually, be built. Water in the Great Basin largely cannot. Utah is one of the driest states in the country, and the decline of the Great Salt Lake has made every large new water commitment politically visible. Data centers vary enormously here: evaporative cooling designs can consume millions of gallons a day, while closed-loop and air-cooled designs use a small fraction of that — at the cost of higher electricity draw. Any state-imposed water condition effectively forces a design decision, pushing developers toward dry cooling and shifting the burden back onto the power system. That trade-off — water versus watts — is now a central engineering and political negotiation in every arid-state siting, and Utah’s reported action puts it on the record at the gubernatorial level.
The Celebrity-Capital Model Meets Institutional Reality
Kevin O’Leary’s data center ventures have been announced with characteristic showmanship — Wonder Valley in Alberta was unveiled with a headline figure of roughly $70 billion over its life. Announcements at that scale invite fair scrutiny: mega-campuses require anchor tenants, firm power agreements, water rights, transmission interconnection, and tens of billions in project finance, most of which is rarely secured at announcement time. A governor tightening the rules is, in one reading, simply the institutional system doing its job — converting a promotional vision into enforceable commitments. That is not necessarily adversarial. Projects that survive rigorous conditioning tend to be more bankable, because lenders and hyperscale tenants prefer sites where the regulatory ground has already been tested.
Winners, Losers, and the Signal to the Market
If the guardrails are well designed, the winners are Utah ratepayers, competing water users, and — perhaps counterintuitively — disciplined developers, who gain a clearer rulebook than rivals face in states still improvising. The risk side: conditions that are vague or shifting can chill investment, and Utah competes with Texas, Wyoming, and the Midwest for AI capital. AI tenants watching this will price in regulatory friction when choosing between states. The market signal is unmistakable either way: the era of announcing a gigawatt campus first and settling the resource questions later is closing.
Background
The AI boom that followed ChatGPT’s 2022 debut triggered a global race to build computing campuses of unprecedented scale, drawing in hyperscalers, private equity, sovereign funds — and celebrity investors. Kevin O’Leary entered the field through O’Leary Ventures, announcing the ‘Wonder Valley’ mega-campus in Alberta in December 2024 with a stated long-term vision of roughly $70 billion, and subsequently pursuing sites in the United States, including Utah.
Utah, meanwhile, has courted technology infrastructure — Meta and others operate large facilities there — while wrestling with the American West’s defining constraint: water. In 2024 the state established a legal framework for serving very large new electricity loads without shifting costs to ordinary ratepayers. The reported tightening of rules on the O’Leary project sits at the intersection of those two currents: aggressive AI-infrastructure recruitment and hardening resource guardrails.
Pennsylvania Governor Josh Shapiro launched new GRID standards for data center accountability on May 26, 2026, as first reported by Harrisburg-area broadcaster FOX43. Based on the initial announcement coverage, the standards are aimed at how data centers affect three things residents feel directly: electric power demand, water consumption, and the utility bills paid by ordinary ratepayers.
Executive Summary
The Shapiro administration’s GRID standards position Pennsylvania as one of the first states to put a governor’s name on a formal accountability framework for data centers — the large, power-hungry facilities that house cloud computing and artificial intelligence workloads. Rather than leaving oversight entirely to utility-by-utility negotiations or federal regulators, the announcement signals that the state itself intends to set expectations for how these projects account for their draw on the grid, their water use for cooling, and the costs they may shift onto other electricity customers.
The timing matters. Pennsylvania sits inside PJM Interconnection, the largest wholesale electricity market in the United States, where capacity prices — the payments that keep power plants available — have risen sharply in recent auctions, driven in part by surging projected demand from data centers. Shapiro has already fought one public battle with PJM over those costs. The GRID standards extend that posture from the wholesale market to the facilities themselves. The initial coverage, however, is light on specifics: the announcement’s legal mechanics, thresholds, and enforcement provisions are not detailed in the source, and we flag those open questions below.
Why Pennsylvania, and Why Now
Pennsylvania is a natural early mover. It is one of the nation’s largest electricity producers and a net exporter of power, it has abundant natural gas, and it has been courting exactly the kind of large data center investment this framework addresses — including high-profile campus projects announced across the commonwealth over the past two years. At the same time, households in PJM territory have watched bills climb as capacity auction prices surged, and data center demand growth is one of the most frequently cited drivers. A governor who wants both the investment and re-electable utility bills has a strong incentive to formalize the rules of the road.
Shapiro also has a track record here. His administration publicly challenged PJM over capacity auction costs, a dispute that ended with the grid operator agreeing to limit price outcomes in subsequent auctions. The GRID standards read as the demand-side complement to that supply-side fight: having pressed the market operator on prices, the state is now pressing the largest new source of demand on accountability.
What “Accountability” Could Mean in Practice
The announcement’s three named concerns — power, water, and ratepayer impact — map onto the three live policy debates around hyperscale computing. On power, the core issue is interconnection: when a facility requests hundreds of megawatts, who pays for the substations and transmission upgrades it triggers? On water, evaporative cooling systems can consume significant volumes, and disclosure of consumption is inconsistent across the industry. On ratepayer impact, the emerging tool nationally is the “large-load tariff” — a special rate class requiring very large customers to make long-term financial commitments so that, if a project shrinks or cancels, the stranded infrastructure costs don’t land on households.
Which of these mechanisms Pennsylvania’s GRID standards actually employ is not specified in the initial coverage. The announcement could range from a binding framework with real teeth to a set of voluntary expectations and reporting norms. That distinction — mandatory versus aspirational — is the single most important thing to watch as details emerge, because it determines whether the standards change project economics or primarily change the political conversation.
Guardrails as a Competitive Strategy
The conventional worry is that regulation deters investment, and data center developers do compare states on speed and cost. But there is a credible counter-argument: clear, uniform standards can actually attract capital by replacing unpredictable, project-by-project fights — zoning battles, rate cases, water permit disputes — with a known checklist. Developers price uncertainty; a state that tells them upfront what accountability looks like may be easier to build in than one where every project becomes a referendum.
The likely winners under a well-designed framework are utilities (clearer cost-allocation rules), communities (visibility into water and grid impacts), and large, well-capitalized operators who can meet the standards easily. The parties squeezed would be speculative projects — interconnection requests filed to reserve grid capacity without firm plans — which inflate demand forecasts and, indirectly, everyone’s bills. If the GRID standards help separate real projects from paper ones, that alone would be a meaningful service to the market.
An Early Entry in a Coming Wave of State Rules
Pennsylvania is not acting in a vacuum. Utility regulators in other states have been moving in the same direction through rate cases — approving special terms for very large customers so that data center growth pays its own way. What distinguishes this announcement is that it comes packaged as a governor-led, state-level framework rather than a utility-specific tariff proceeding, which gives it broader scope and higher political visibility.
That makes it a template other governors will study. If Pennsylvania can pair accountability standards with continued project announcements, it strengthens the case that guardrails and growth are compatible. If investment visibly slows, critics will attribute it to the standards — fairly or not. Either way, the experiment will generate the evidence the rest of the country currently lacks, and the industry should engage with it on that basis rather than treating any state framework as inherently hostile.
Background
Pennsylvania is one of the largest electricity-producing states in the country and a longtime net exporter of power, with deep natural gas resources and a legacy nuclear fleet. That energy abundance, together with available land and fiber routes between East Coast metros, has made it a serious contender for hyperscale data center campuses as the artificial intelligence buildout accelerated through 2024–2026, including multibillion-dollar projects announced across the commonwealth.
The same period strained the region’s electricity economics. Capacity prices in PJM Interconnection — the wholesale market serving Pennsylvania and much of the eastern U.S. — rose sharply in successive auctions as demand forecasts swelled, and Governor Shapiro emerged as one of the most vocal state-level critics of those outcomes, pressing PJM to limit costs borne by consumers. The GRID standards announced May 26, 2026 are the next step in that arc: moving from contesting wholesale market prices to setting state-level expectations for the facilities driving demand.
