Local voters put a brake on the AI buildout
On November 3, 2026, voters decided 47 local measures tied to data centers. According to WBAL-TV, citing Ballotpedia and Redbud Consulting’s datacentersontheballot.com, 45 were classified as votes to restrict the projects, one fell in the site’s “allow” category, and one was still undecided. Those labels are not 45 identical bans. The legal tools differed, and the lone “allow” was not a clean yes to construction.
Where WBAL cited margins, the results were not a handful of squeakers dressed up as a trend. Morgan County, Illinois posted the strongest share in that account: 88.3 percent of 10, 663 votes cast went to restricting data centers. That was the high end, not the typical case. The average pro-restriction share sat above 70 percent, and the closest race WBAL cited, Sprigg Township in Adams County, Ohio, still cleared 52.6 percent. About 50 related measures appeared over the year, piled up rather than spread evenly: 21 in Ohio, eight in Maine.
This is the unglamorous layer of AI for business walking into a zoning hearing. Models, AI agents, and automation programs all assume someone, somewhere, will keep pouring concrete, power, and water into buildings most customers never see. A stack of local ballots just made that assumption a permitting problem, even though nobody has shown it was why the broader election broke the way it did.
These were brakes, not a rejected fast track
One early telling treated the ballots as failed attempts to speed construction. That version does not match the measures. Voters largely approved restrictions.
WBAL’s account of the winning language includes outright bans, a 180-day moratorium, retroactive moratoriums, technical caps on electricity or water, and the rejection of a development agreement. A retroactive moratorium can freeze projects already in process, not only applications that have yet to be filed. Maine voters approved “An Ordinance to Establish a Retroactive Moratorium on Data Centers.” Ohio voters rejected approval of a development and supply agreement with EdgeConneX. A Florida measure to prohibit new data centers in the city passed.
Redbud’s site, as WBAL describes it, sorts messy legal text into “Restrict” or “Allow.” The lone “allow” result shows why the tally needs a footnote. Harwood, North Dakota passed with 75.6 percent, but WBAL notes the language concerned extra review of certain developments and a lengthy Home Rule Charter amendment, not a straightforward authorization to build a data center. Treat 45-1 as a classification, not a single legal outcome.
The anger is about how the projects were pursued
WBAL set these votes inside what it called the Democratic Party’s historic blue wave, and read them as a rebuke of President Donald Trump and a Republican agenda the outlet described as broadly friendly to AI and data centers. That is one newsroom’s frame, not a count of why every ballot was cast.
On TechCrunch’s Equity podcast, Anthony Ha called anti-data-center sentiment “a big part” of Democratic success and “a pretty potent political force.” Kirsten Korosec disagreed that it was what brought people to the polls.
I don’t think that the data center issue is what brought everyone to the polls and led to the quote-unquote ‘blue wave.’
She did call data centers “an increasingly grassroots issue.” No analysis in the reporting measures how many people showed up because of a server hall. Both readings can sit on the table until someone counts that.
Korosec’s account of the anger is specific enough to use. She pointed to secretive approvals, nondisclosure agreements imposed on elected or appointed officials, thin disclosure of how big a project really is, and siting in sensitive places, including the Southwest, where water scarcity is already the fight. Republicans, independents, and Democrats, she said, could look at that conduct and call it wrong, even if data centers were not a singular voting issue.
Trump had already taken a public side. In an end-of-August Truth Social post, as reported by WBAL, he wrote that “The only reason that communities throughout the U.S.A. should not want Data Centers is if they want to end up being backwards and poor, ” then added “let data reign” and warned, “If we kill the Golden Goose, you will only have yourselves to blame.” A presidential post is context. It is not evidence that every local ballot was a referendum on him.
Electricity and water are not abstract externalities here. A large AI campus can ask a utility for the load of a small city and, depending on the cooling design, a serious claim on local water. The pattern Korosec described is the one that travels: an NDA on a public official, then neighbors learning the scale late.
OpenAI answered with a compact, not a euphemism
OpenAI published two documents, a National Community Compact and a Compute Campus Policy Blueprint, under the heading of setting a new standard for responsible AI infrastructure. Ha heard the phrasing first: “they’re not data centers anymore, they are compute campuses.” Sean O’Kane called the rename ridiculous and said it would not change anything.
The documents are thicker than a new noun. For future campuses it owns and operates, OpenAI says it will not use NDAs with public officials, except for narrow protections around legitimate security information, trade secrets, or proprietary and competitively sensitive material. It says those campuses will pay the full cost of electricity and related infrastructure, with financial assurances before major spending. It also promises a water plan, priority for closed-loop or low-water cooling, publication of site-level water and electricity use, and independent noise studies, alongside a local contact and annual public reporting.
OpenAI says the announcement builds on Stargate Community commitments made in January, an earlier pledge to pay its own energy costs and shape plans around local priorities, plus later commitments in Effingham County, Georgia, and Pike County, Ohio. The formal compact is new. The underlying promises did not appear from nowhere the week after Election Day. Korosec is still right about the incentive: “when you put up either a regulatory certainty in the marketplace, or at least signals of going in that direction, then corporations will respond.”
Two community figures are company-reported, not independently audited. OpenAI says Effingham residents helped shape a $4.8 million grant for free school meals for all 14, 000 students in the county, and that a childcare focus in Pike County led to a joint $6 million commitment from OpenAI and SB Energy.
Scope is the line not to blur. These operating commitments apply to future compute campuses OpenAI owns and operates. The blueprint then asks federal, state, and local governments to push broader rules, including public reporting, public tax-incentive terms, clawbacks if commitments are missed, and ways to steer construction and supplier work locally. A voluntary compact and a proposed statute are not the same thing. Whether any of it softens opposition is unproven. A new name will not do that work by itself.
Put the hearing on the critical path
Whether investors have also lost patience with heavy compute spending is a separate claim. This reporting names no firm, date, or canceled project to prove a market turn. The planning assumption that does follow from the ballots is narrower. A company can have a strong model and still miss a deployment quarter because a township imposed a retroactive moratorium or capped the water. Treat a hearing that ends with restriction support above 70 percent (WBAL’s average for these votes, not a forecast for the next county) as a delivery risk, not a law of the market.
Before a compute contract or a site deal, the useful questions are ordinary and specific.
- Disclosure. What is the real load, footprint, and water draw, and has anyone asked a public official to sign an NDA before neighbors see those numbers?
- Power. Who pays for interconnection and the grid upgrades the project adds? Can the utility curtail delivery when demand spikes? OpenAI says its agreement with Georgia Power lets the utility cut the planned Effingham campus by up to 1, 000 megawatts in those hours. Ask what happens to cost if the project is delayed, reduced, or canceled. The blueprint urges utility commissions to put added grid costs on the large customer, and to protect other customers if a project shrinks or dies.
- Water and noise. Is cooling closed-loop or low-water, or is the plan a large draw in a dry region? Is there an independent noise study, and will site-level use be published?
- Local law. Is there a ban, a technical cap, or a moratorium, including a retroactive one that can freeze work already underway?
- Whose promise applies. If the campus is leased, colocated, or owned by someone else, OpenAI’s compact does not cover it. A vendor’s community policy is not your permit.
On that same podcast, O’Kane argued that Elon Musk “got basically nothing” from donating “half a billion dollars, maybe even more, by the time we see the final count” to Republicans, and that Musk’s businesses now sit in a state that “turned about as blue as it could possibly turn.” That is an on-air thesis. A final total, a donor ranking, and the name of that state are not established here, and none of it changes a site decision.
Existing contracts, and jurisdictions that never put this on a ballot, still matter. This is a screen for the next site, not a claim that every server hall just lost its lease. The buildings behind AI automation still need a permit, a substation, and a water plan. A growing number of local voters are willing to write the conditions, and they are not waiting for a national ban to do it.
Questions worth asking before the next site plan
-
Did voters ban data centers nationwide?
No. On November 3, 2026, voters decided 47 local measures, and WBAL’s account of Redbud’s classification shows 45 restriction results, one “allow, ” and one undecided. That mix covers bans, moratoriums, and technical limits. It is not a national prohibition, and it is not a set of failed fast-track votes.
-
Did data centers cause the Democratic wave?
Nobody has shown that. Korosec says they were not what brought people to the polls. Ha says anti-data-center sentiment was still a potent part of the result. WBAL links the local votes to what it called a historic blue wave without measuring voter motivation.
-
Will renaming them “compute campuses” calm opposition?
There is no evidence that it will, and O’Kane’s prediction is that it will not. The commitments that might matter more (limits on NDAs with public officials, paying for power and grid costs, water and noise disclosure) apply to future campuses OpenAI owns and operates, and even those are unproven as a political fix.
-
What should a leadership team require before signing a compute or site contract?
Disclosure of scale, a written split of who pays for power and grid upgrades if the project slips or shrinks, a water and cooling plan, and a check for moratoriums that can freeze work already underway. Then confirm whether any vendor compact applies at all. OpenAI’s does not cover a leased or third-party site, and plenty of jurisdictions have not voted.