Weekly Recap: PJM's Bring-Your-Own-Power Rule and Nvidia's $105B Bet

Today on Concrete Compute, this is our weekly recap — the week the AI buildout's politics caught up with its checkbook. On one side, Nvidia backed a single Ohio data center campus with a guarantee capped above one hundred billion dollars. On the other, governors, grid operators, and even a developer or two spent the week converging on one blunt rule: bring your own power, or pay your own way. So what actually happened, and does any of it hold up? Welcome back to Concrete Compute, your daily brief on the AI infrastructure buildout. It's Saturday, August 22, 2026. Here's the week that was. Pennsylvania signed an executive order, PJM published a five-year strategy nobody's fully sold on, California advanced ratepayer bills, and the political backlash against data centers kept getting louder. Let's start where the week's biggest structural shift happened — inside PJM.

We covered this one earlier in the week, so here's the short version. PJM — the grid operator running the mid-Atlantic — finalized a framework that lets big new loads, like data centers, connect to the grid before there's enough matching power capacity built to serve them. The catch: if there's an emergency, those unsupported loads get curtailed first, cut off before anyone else. It's the formal codification of what's been an informal warning all year — bring your own power, or accept you're first in line when things get tight. This was the single biggest structural story of the week, and it's the backdrop for almost everything else we're about to run through: Pennsylvania's order, Amazon's own-grid campus, EdgeCore volunteering to pay its own way. PJM also put out its own five-year strategy the same week, laying out the bigger picture — we'll get to how one power-market consultant graded that, and it's not a great grade. For now, the headline is simple: PJM just told the industry, in writing, who's on the hook when the grid gets stressed.

Now, the number that stopped a lot of people this week: Nvidia disclosed a guarantee capped at one hundred five billion dollars, backing the initial four-point-two-five gigawatts of what's ultimately planned as an eight-gigawatt OpenAI campus at SB Energy's PORTS-Pike site in Pike County, Ohio. Before you spend that number in your head, know what it actually is — a capped, conditional residual-value guarantee tied to a twenty-year SB Energy lease, not cash Nvidia is writing a check for today. Here's what ties it to the week's bigger theme, though: SB Energy says it'll fund four-point-two-billion dollars of regional grid infrastructure itself, plus an eighty-million-dollar community benefits fund, explicitly trying to dodge the costs-dumped-on-ratepayers complaint driving protests everywhere else. My read: that's the industry's biggest spender doing something close to what I think the biggest spenders should be doing — but the guarantee-versus-cash distinction matters, and any headline calling this a hundred-billion-dollar investment is overstating what actually got committed.

Pennsylvania's Governor Josh Shapiro signed an executive order on August eighteenth that conditions favorable permitting and tax treatment for big data centers on meeting new energy, environmental, workforce and community requirements — binding guardrails in exchange for a faster yes. That same order also builds in a carrot: faster permitting for projects that bring their own power, stick and carrot in one document, not two separate moves days apart. When we looked at this one earlier in the week, my read was that Shapiro's framing it as anti-speculation, not anti-data-center: too many developers were parking proposals in the interconnection pipeline with no real intention of building, clogging a system meant for projects that'll actually go up. Nothing in this week's coverage moves me off that read, but here's the honest caveat: this is an executive order, not legislation, so a future governor could unwind it, and how binding those GRID requirements prove in practice depends on implementing regulations that haven't been written yet. Putting the guardrails and the incentive in the same order, Pennsylvania's trying to keep the jobs without handing residents the bill increase — the same balance its peers in New South Wales and Ontario are reaching for too.

This is the story that ties the whole week together, and it's more about politics than power lines. This week's flashpoints, which are separately reported: death threats tied to a proposed site in Marshall, Michigan; a developer withdrawing from Calvert County; and Chicago considering a pause on new projects. On the other side of the aisle, Axios reports Republican strategists warning that data centers are becoming what they call, quote, politically radioactive, end quote, for incumbents facing reelection. Here's the both-sides version, because neither party is actually arguing to stop the buildout: the Republicans Axios quoted frame the risk as higher bills and land-use fights costing them their seats, so their fix is political distance. Democratic governors like Shapiro are betting the fix is regulatory conditions — keep the projects, add the guardrails. Both camps assume the buildout keeps going; the fight is over who manages the political fallout and who pays for it.

Here's one that flew a little under the radar this week, even though it's arguably the bigger document. PJM released its own five-year strategy on August nineteenth, separate from the bring-your-own-power framework we just walked through. This is PJM's board-approved roadmap for the data center wave, and the number that should stop you is this: PJM projects peak demand rising nearly sixty-six gigawatts over the next decade, mostly driven by data centers. The strategy calls for faster planning, stronger alignment with the states in its footprint, and more efficient decision-making — and in the document itself, PJM admits its old stakeholder process, quote, was built for a different era, end quote. What the strategy does not do is settle the two questions everyone actually wants answered: how the capacity market gets reformed, and who governs the tradeoffs when interconnection queues and state policy collide. Both get punted to separate FERC proceedings. A power-market consultant quoted in the coverage put it bluntly, dismissing the plan's headline items — slashing the interconnection queue, improving forecast accuracy, capacity market reform — as a to-do list rather than a strategy. I think that's fair — writing down what needs fixing isn't the same as fixing it, and PJM is asking for patience across a five-year runway while sixty-six gigawatts of demand doesn't wait around for a FERC docket to clear. Remember, this is the same grid operator that just told data centers they could connect early and get curtailed first without their own power. The curtailment rule handles today's traffic jam at the substation. The five-year strategy is supposed to prevent the next one — and right now, that part is still mostly a plan to make a plan.

Over in California, two bills passed a key committee as the state's legislative session heads toward its close, according to Canary Media — Senate Bill 886 and Senate Bill 887. SB 886 would create a dedicated tariff, a separate billing category, specifically so data center costs don't get spread onto everyone else's power bill. SB 887 offers relief from California's environmental review law for projects that pay the full cost of their own infrastructure and use recycled water instead of drinking water. What makes California interesting is the timing: this is a state with relatively few data centers compared to the PJM footprint, and lawmakers are building ratepayer guardrails in before the projects show up, rather than scrambling to write them after the fact, which is the reactive posture Ohio, Pennsylvania and PJM all find themselves in this week. That's worth noting on its own. But it's not unanimous — PG&E opposes SB 886, even though utility worker unions are backing it. And a ratepayer advocate quoted in the coverage makes an argument I think is underrated: as long as utilities earn a guaranteed return on their capital investments, they have very little built-in incentive to actually control the costs these bills are trying to target. That's the tension sitting underneath basically every ratepayer-protection bill this year — writing the rule is one thing, but the entity implementing it might be structurally motivated to spend more, not less. This is a state most people don't associate with the AI buildout at all, and that's exactly why it matters: if California can build in protection before it has a data center boom, that's a template other states could copy before they need it.

Quick one on Amazon, which we touched on this week: Data Center Knowledge reports the company is exploring a traditional grid connection for its eight-thousand-acre AI campus, even though the whole pitch for that site was private, on-site power generation — we haven't independently confirmed that detail ourselves. Sit with that for a second — if it holds up, that's the real-world test of the bring-your-own-power framework PJM and Pennsylvania spent the week formalizing: even a company building its own generation still wants a grid tie-in as backup, and going off-grid isn't always the clean, self-contained solution it sounds like in a press release — the same lesson SpaceX's Terafab project has run into. The project has also drawn national scrutiny this week over potential emissions from that private generation complex, which sits awkwardly next to the clean-power framing a lot of these bring-your-own-power deals use to win over local communities. So here's the question I keep coming back to on every one of these: does an eight-thousand-acre campus mean permanent local jobs and tax base for the people who live there, or mostly construction-phase work and a generation complex nobody nearby actually wanted? This week's reporting doesn't answer that yet, and that's worth saying plainly rather than guessing.

EdgeCore's news didn't get much attention this week, and it deserves fuller airtime, because it's a genuine good-news item in a week full of fights. The developer and operator says it will fund the power infrastructure its own campuses need rather than push those costs onto utility ratepayers. That's the exact concession Pennsylvania and PJM spent this week trying to mandate through orders and frameworks, and EdgeCore is volunteering it. That's worth celebrating in plain language — a developer choosing to pay its own way before anyone forced it to is a real win, and it's the shape of deal I'd want to see more of. But here's the caveat that makes it credible instead of just a press release: EdgeCore itself acknowledges that the definition of full cost depends heavily on how the local utility allocates broader grid investments. If a data center pays for the wires and transformers running directly to its own site, but the utility spreads the cost of upgrading shared regional transmission across everybody's bill, ratepayers can still end up covering a chunk of the tab even when the developer believes it paid in full. My read: EdgeCore taking this position publicly, unprompted, earns real credit — I just want to see the actual cost-allocation filing before I call the ratepayer question closed, because full cost is doing a lot of work in that sentence, and it's the utility, not EdgeCore, that decides how the shared costs get sliced. What I want to see next is a company making this same commitment without needing the asterisk — full cost, defined plainly, no caveat required.

So if there's one thing to take from this week, it's this: the next time you see a data center headline with a big dollar figure attached, ask which side of the ledger it's actually on — guaranteed cash, or a guarantee like Nvidia's that only pays out if something goes wrong. And ask who's writing the check for the power lines. Those two questions will tell you more than the megawatt number ever will. If this recap was useful, follow Concrete Compute wherever you're listening, so next week's episode lands automatically. This has been Concrete Compute, an AI-voiced podcast, created and built by a real human using today's cutting-edge technology. Nothing you heard on this show is financial advice. I'm Brian Lampert, and I'll catch you all tomorrow — take care!