AI Governance
Data Centers
Drones
Climate
Privacy
2026 Maine Senate
Bob Dylan
Permits and Power Costs Tighten Data Center Growth
Yesterday made clearer that the next constraint on data-center growth is increasingly not land or announced capacity, but the conditions attached to approval. Pennsylvania’s new framework puts local consent, environmental review, power commitments, and potential grid-cost obligations into the development sequence for large projects. At the same time, local proceedings in Kentucky and New York showed communities moving from broad objections toward specific operating standards.
This extends a pattern visible in recent days across several jurisdictions: access to power is becoming only one part of the development case. Developers are being asked to show who bears infrastructure costs, how water and noise will be managed, and what a host community receives in return.
Pennsylvania’s Executive Order 2026-05 is now more clearly a practical gate on large projects, not simply a statement of concern. Data centers must secure local approvals before relevant state environmental review and are no longer eligible for the state’s Permit Fast Track Program. Facilities above 25 MW can pursue a rolling Department of Environmental Protection review if they enter GRID-linked commitments covering incremental power supply, affordability, water, environmental protection, workforce development, and community engagement. Projects outside that path face additional approvals and a complete application review before action. The order also directs the administration to seek Public Utility Commission measures on interconnection costs, reliability charges, and emergency curtailment. Those utility rules have not yet been adopted, but the changed sequence alone adds schedule and execution risk to Pennsylvania’s proposed pipeline.
Local resistance continued to acquire procedural force. Lexington, Kentucky, will hold another public hearing on October 6 while its data-center moratorium remains in place. As WEKU reported, planners are considering limits on facility size and power demand, large setbacks, a 30-decibel noise cap, stormwater and decommissioning requirements, and a ban on evaporation-based cooling. In New York, a listening session on the proposed STREAM US facility at the STAMP site brought water, noise, wildlife, energy-cost, and transparency concerns into a debate already sharpened by the state’s pause on new hyperscale construction. Neither process has produced a final rule or project rejection. But they show how quickly siting disputes can become design and operating requirements.
Ohio offered a more tangible, but limited, response to the affordability debate. AEP Ohio and Meta, QTS, Amazon, SoftBank Energy, and Google committed more than $18 million to the Neighbor to Neighbor bill-assistance program, including $17 million from the companies. Eligible low-income customers facing disconnection can receive one-time grants of up to $500. The gesture matters because it acknowledges that household bills have become part of data centers’ political license to operate. It does not, however, answer the larger regulatory question of how generation, transmission, and interconnection costs will be allocated; more than 200,000 households reportedly meet the program’s late-payment criteria.
Two new examples reinforced that apparently favorable resource conditions do not eliminate local constraints. In Bahia, Brazil, Mongabay reported that Serena is pursuing connections for as many as 12 containerized facilities that could absorb wind generation otherwise curtailed, with potential capacity of 270 MW. One facility is operating and two additions are authorized, but land clearing, consultation, local benefits, and cooling-water risks near Itaparica Lagoon remain contested. In Virginia, Cardinal News found statewide water withdrawals fell between 2019 and 2024 even as data-center use rose. Yet Google’s planned Botetourt County complex could become its utility’s largest customer, with an initial projection of 1.2 million gallons a day and a possible future request of up to 8 million. Statewide totals can be reassuring while the relevant service area faces a far more consequential demand decision.
Key Points
- The regulatory shift is becoming operational rather than rhetorical. Recent briefings tracked Texas connection restrictions, PJM’s proposed reliability conditions, and TVA’s large-load rate. Pennsylvania now adds a permitting model in which developers’ power, affordability, and community commitments influence how quickly a project can move through review. The approaches differ by jurisdiction, but the shared direction is clear: a large load must increasingly demonstrate a workable system arrangement, not merely request service.
- The most durable pressure point is local distribution of costs and impacts. Ohio’s bill-relief fund addresses household distress after the fact; Lexington’s proposed standards seek to contain noise, water, and land-use effects before construction; and the Virginia and Bahia cases show why water exposure must be assessed at the utility and community level. Developers can no longer rely on statewide averages or broad economic-development claims to settle these questions.
Implications
For developers and investors, permitting and power diligence are converging. A credible project case now needs more than an interconnection position or a renewable-power narrative: it may require local approvals, documented infrastructure funding, curtailment tolerance, resource-impact controls, and a community-benefits strategy. Pennsylvania’s framework does not determine its eventual PUC rules, but it makes those dependencies material earlier in project planning.
For utilities and policymakers, limited mitigation measures are unlikely to settle the ratepayer debate on their own. Ohio’s assistance funding may provide near-term relief for some households, yet it leaves the underlying tariff and cost-recovery choices unresolved. The next consequential decisions will be the rules that determine whether large-load customers fund dedicated and systemwide upgrades, and whether those commitments are enforceable.
Water risk should be treated as site-specific infrastructure risk, not as a statewide accounting exercise. Virginia’s declining aggregate withdrawals do not determine Botetourt County’s capacity to serve a very large new customer, just as surplus wind in Bahia does not resolve cooling, permitting, or social-license questions. Projects with strong power economics can still be delayed or redesigned by local resource constraints.
Watchpoints
Watch
Pennsylvania’s implementation guidance: watch how the Department of Environmental Protection applies the different review paths and whether the Public Utility Commission advances rules on interconnection costs, reliability charges, or emergency curtailment.
Watch
Lexington’s October 6 hearing and subsequent council action: the key question is whether proposed limits on size, power, setbacks, noise, stormwater, decommissioning, and cooling become binding zoning standards.
Watch
Ohio’s broader cost-allocation response: monitor whether bill-assistance funding is followed by utility, legislative, or regulatory measures that more directly assign grid-expansion costs to large loads.
Watch
Serena’s Bahia expansion: permitting outcomes, cooling configuration, water demand, and the quality of community consultation will determine whether surplus wind power translates into a larger operating data-center cluster.
Fallout
Yesterday’s developments reinforced a fragmented but persistent change in data-center development: projects are increasingly being judged on the terms of their power, environmental, and community arrangements. Pennsylvania supplied the clearest state-level example, while local proceedings and resource cases showed why those terms will vary sharply by site.
Pennsylvania Permitting and Grid Obligations
Pennsylvania is making large data-center development conditional on local approvals and wider commitments on power, affordability, water, environmental protection, and community engagement.
Fresh developments
Reporting clarified that Executive Order 2026-05 removes data centers from fast-track permitting, requires local approvals before relevant state environmental review, and creates different review paths for facilities above 25 MW depending on GRID-linked commitments.
Why we noticed
The order changes the practical sequence of project development in a state with a substantial proposed pipeline. It also opens the possibility of future interconnection-cost, reliability-charge, and curtailment obligations.
Watch for:
- Department of Environmental Protection guidance and actual review practice for projects above 25 MW.
- Public Utility Commission action on cost allocation, reliability charges, and emergency curtailment.
- Whether developers accept GRID commitments or adjust project schedules and designs.
Local Siting Rules and Community Consent
Moratoria, hearings, and proposed operating standards are turning community concern into direct siting and design risk.
Fresh developments
Lexington scheduled an additional October hearing during its moratorium and is considering restrictions on size, power demand, setbacks, noise, stormwater, decommissioning, and evaporative cooling. A New York listening session on the proposed STREAM US facility similarly focused attention on water, noise, energy costs, and transparency.
Why we noticed
The important change is procedural: concerns that may once have remained public opposition are increasingly entering formal zoning, review, and legislative processes that can delay projects or impose durable conditions.
Watch for:
- Whether Lexington adopts its proposed controls after the October hearing.
- Whether New York’s hyperscale pause produces statewide standards for public engagement, environmental protection, labor, and efficiency.
- Evidence that proposed facilities are redesigned, delayed, or withdrawn in response to local conditions.
Ratepayer and Water Exposure
Household affordability and water availability are increasingly evaluated at the level of individual utilities and communities rather than through broad regional averages.
Fresh developments
AEP Ohio and five major data-center firms committed more than $18 million to household bill assistance, while reporting from Virginia and Brazil highlighted concentrated local water exposure around proposed facilities despite more favorable statewide or regional resource conditions.
Why we noticed
The Ohio fund is a concrete response to political pressure but not a replacement for tariff and infrastructure-cost decisions. The Virginia and Bahia cases show that surplus power or declining statewide withdrawals do not resolve the local service and permitting questions that govern project viability.
Watch for:
- Whether Ohio adopts broader large-load cost-recovery or consumer-protection measures.
- Water-service approvals and future demand requests for Google’s Botetourt County complex.
- Cooling choices, permitting decisions, and community engagement for Serena’s proposed Bahia facilities.
Final Thought
The data-center buildout is not broadly stopping; it is becoming more conditional. Yesterday’s evidence suggests the central contest is moving from whether communities will host large facilities to the terms on which they will provide land, water, permits, and power—and who will carry the associated costs.