OpenAI Just Promised to Pay Its Own Power Bill and Drop the NDAs. The Pledge Skips the 10 Gigawatts It Only Leases in Ohio.

In Ozaukee County, Wisconsin, voters did more than say no to one data center. On November 3rd they passed a referendum, 66% to 34%, that gives residents a standing veto over any future data center project that takes a tax incentive — not just the one that prompted the vote, the next one too. They weren't alone. Across ten states, voters decided roughly forty-one data center ballot measures that same day, and by Ballotpedia's own count, cited by Reuters, every measure but one broke against the industry. Ohio alone had 21 of them on local ballots, more than any other state, and nearly all of them passed restrictive. Of the measures with results in hand, 28 drew support of 70% or higher for banning or pausing new development outright. This wasn't a close election. It read, across ten electorates that never coordinated with each other, like a verdict.

Two days later, on November 5th, OpenAI tried to answer it directly. The company published two documents at once: a National Community Compact, a set of promises binding its own future projects, and a Compute Campus Policy Blueprint, a set of asks aimed at the same state and local lawmakers who had just written those ballot measures into law. "We will pay the full cost of powering our compute campuses and ensure local residents do not foot the bill for our energy needs," the compact says. Alongside that, OpenAI pledged to publish water and electricity use at every site it owns and operates, and to stop signing non-disclosure agreements with the public officials who approve its projects.

What the pledge actually says

The policy blueprint goes further than the compact's own promises, at least on paper. It asks lawmakers to require large power users to pay the grid costs they actually cause instead of spreading them across every other ratepayer, to make incentive terms public instead of negotiated behind closed doors, and to let a community claw back benefits if a developer misses the commitments that got its project approved. OpenAI also says it will offer financial assurances meant to shield other utility customers from the cost of a project that gets delayed, shrunk, or canceled after a utility has already built for it — a specific answer to a complaint this blog has tracked for a year: the utility that builds a substation for a data center that never fully shows up, and the ratepayers stuck covering it. None of this needs a vote from OpenAI's own board. All of it needs a legislature or a commission to actually adopt it. The company is, in effect, asking regulators to turn a voluntary promise into a mandatory rule — one that would also bind every competitor who never offered the promise voluntarily.

There's already a live test case for what the compact looks like applied to an actual place. In Pike County, Ohio, where OpenAI and its infrastructure partner SB Energy are building toward a 10-gigawatt campus, families raised concerns earlier this year about strain on local childcare capacity as construction workers and new hires moved into the area. OpenAI and SB Energy responded with a joint $6 million commitment, and the company says it will keep meeting with residents, officials, schools, businesses, and labor groups there to shape what it calls an Ohio Community Compact specific to that site, rather than importing the national document wholesale. That's a real number, tied to a real complaint, in a real county — the kind of specific, negotiated commitment the national document is mostly asking other developers, and OpenAI's own future projects, to match going forward.

The gap: what OpenAI owns, and what it only leases

Here's the catch, and it isn't small. OpenAI's compact covers campuses the company owns and operates. The Pike County project, and the wider 10-gigawatt Ohio buildout it belongs to, isn't one of those: SB Energy builds the facilities, owns them, and runs them, under a 20-year lease to OpenAI, with Nvidia providing credit support for the arrangement and SB Energy separately handing OpenAI $5.5 billion in warrants ahead of SB Energy's own planned IPO. Nothing OpenAI has published says the compact's power-cost or no-NDA pledges automatically reach a site it leases rather than runs. The same question hangs over Oracle, which builds and owns a large share of the infrastructure OpenAI relies on elsewhere, under its own separate deals. A pledge that may not reach some of the company's largest buildouts is still worth something. It just isn't the blanket promise the headline implies.

The second catch is enforcement. The compact names no penalty for falling short of it, no outside body that checks the water and electricity figures OpenAI says it will publish, and no process for a community that disputes a number it doesn't believe. It is a promise OpenAI is making to itself, graded by OpenAI. Chris Lehane, the company's chief global affairs officer, has separately acknowledged that some of its projects could slow down as the politics around data centers get harder — a useful admission, but not one written into the compact as an enforceable term, and not the kind of thing a company says unless the pressure behind it is real. On GridPermit's evidence ladder, a voluntary corporate pledge with no verification sits well below a signed interconnection agreement or a tariff a utility actually files with a state commission for a regulator to approve or reject. One is a promise about the future. The other is a document someone with authority can hold a company to today.

This is also the second time in five weeks a major AI compute buyer has made almost exactly this promise. Amazon's own "Built Together" pledge, announced October 2nd, ended its NDA practice with local governments and promised communities their bills wouldn't rise because of its data centers — the same week reporters pointed to a West Texas gas plant Amazon is financing, permitted to emit more carbon dioxide annually than any other power plant in the country. A pattern is forming: when the backlash gets loud enough, the industry's answer is a voluntary compact, not a change a court or a commission can force on it. That doesn't make either compact worthless. Ending NDAs is a real, checkable change — you'll know within a filing cycle whether a new county agreement has one or doesn't, the same way you'll eventually know whether OpenAI's next lease structure quietly keeps a project outside the compact's reach. It just means the compact, for now, is the floor of what communities are owed, not the ceiling.

I think OpenAI picked the right week to make this announcement, and mostly the right things to promise. Paying your own power bill and publishing your own water use aren't radical asks — they're close to terms GridPermit already sees written into large-load tariffs that utilities negotiate with developers every month, with nobody holding a press conference about it. What the compact doesn't settle is the harder question Tuesday's results actually raised: whether a voluntary industry standard, set by the industry itself, can survive contact with forty-one separate, locally elected answers to the same question, each with its own teeth and its own enforcement. The real test isn't this press release. It's whether a state regulator writing a large-load tariff next year treats OpenAI's compact as a floor to build past with real penalties attached — or lets it quietly become the ceiling instead, exactly as written, with nothing underneath it.