Pennsylvania data center order: compute needs a local yes

Texas gated its data center queue with an audit two weeks ago. Pennsylvania just went further. On August 18, Governor Josh Shapiro signed Executive Order 2026-05, directing state agencies to require every data center proposal to meet binding Responsible Infrastructure Development (GRID) requirements — and to secure local approval before the Department of Environmental Protection will even review a permit. The Pennsylvania data center order doesn't slow projects down. It changes who gets to say no.

What actually happened

The order attaches conditions to the permit itself. DEP is directed to fold the GRID requirements into permit review, to require a legally binding Consent Order and Agreement from the developer, and to withhold permits from projects that haven't cleared local approval.

The GRID requirements themselves are four buckets: developers cover the full cost of new electricity infrastructure rather than pushing it onto households and other ratepayers; they run documented community outreach and public meetings; they hire locally and sign community benefit agreements; and they meet the state's highest environmental standards, including water conservation.

Two procedural changes matter more than the buckets. Nondisclosure agreements are prohibited on data center projects — the mechanism that has kept municipalities negotiating with an unnamed hyperscaler is gone. And every AI data center proposal is removed from the Permit Fast Track program, with no future project eligible. The Department of Revenue is separately directed to condition the Computer Data Center Equipment Exemption on GRID compliance, which puts the sales tax break behind the same gate.

The scale is the reason. The Governor's office counts more than 100 data center projects in public databases, of which 58 have engaged DEP, 15 have applied for at least one permit, and 5 have received all permits needed for a first phase. Shapiro's framing was blunt: if you can't meet the requirements and get a community to agree, you don't get Commonwealth support.

Why grid policy matters for your business

You don't build data centers. You buy their output on contracts priced against capacity someone assumed would exist by 2028.

Read the funnel again: 100 proposals, 5 fully permitted. That gap was already large before this order. Adding a binding consent agreement, a local approval gate, and a killed fast-track lane doesn't close it — it widens it and pushes the closing date right. That's a second state, in a month, converting announced capacity into conditional capacity.

The pattern to internalize: compute is being repriced from a commodity into a permitted industrial asset, subject to water rights, township votes, and a commission's calendar. Vendors will keep quoting it like bandwidth. Budget like it's real estate.

Three operator moves, same as they were in Texas and more true now. Don't sign multi-year AI commitments against unbuilt capacity — take the shorter term and the worse rate over a discount that depends on a 2028 groundbreaking. Keep your model layer abstracted so a regional crunch is a routing change instead of a migration. And price your automations at today's token cost with real headroom, not the promotional rate that assumes all 100 projects get built.

Sources: Commonwealth of Pennsylvania, Executive Order 2026-05 (PDF).