A county commissioner who votes to approve a data center in 2026 is making a career decision, and increasingly the wrong one.
That is a new fact. For most of the last two decades, approving a large industrial project with a tax base attached was politically routine and frequently popular. Then in April 2026, voters in Port Washington, Wisconsin approved by sixty-six percent a measure requiring voter approval before data center tax incentives can be granted. Voters in Missouri removed city council members who had approved a facility. In Michigan, candidates from both parties who campaigned on data center restrictions won their primaries. Polling has found roughly seven in ten Americans opposing construction in their own area, nearly half strongly, against about a quarter in favor.
Data center politics has become a domestic electoral variable in under two years, and it is one of three separate forces pressing on the same buildout from different directions. The second is geopolitical: export controls, sovereign compute programs, and a supply chain concentrated in a place with a strategic problem. The third is technological, and it is the one the other two cannot see coming, because it consists of the possibility that the hardware being fought over turns out not to have been necessary in the quantity ordered.
Each vector operates on a different timescale, each has its own mechanism, and the interesting question is not which one is most dangerous. It is that a project has to survive all three, and they do not arrive in a convenient sequence.
Vector one: data center politics turned local
The reversal happened fast and the reason is legible in the mechanism rather than in anybody’s rhetoric.
A data center brings a large assessed value and a small workforce. A multi-billion-dollar campus may employ a few dozen to a few hundred people in steady state, which is a capital-to-labor ratio no traditional manufacturing plant produces and which sits at the opposite end of the spectrum from the extractive and processing industries that historically anchored rural tax bases, and which means the standard economic development pitch is doing less work than it appears to.
Against that, the visible costs arrive quickly. Capacity prices rise across a whole zone when a large load tightens supply, which puts the cost on bills belonging to people who never saw a permit application. Water withdrawals are local and measurable, and the evaporative cooling that drives them is most efficient in exactly the arid climates where water is most contested. Construction traffic, generator testing, and the low-frequency noise of a large cooling plant are experienced by neighbours rather than by the county at large. And the tax abatements that secured the project in the first place mean the assessed value is not producing the revenue the pitch implied for the first decade.
The legislative response has been rapid and it runs in both directions, which is what makes it interesting rather than a simple wave. New Jersey enacted a Data Center Fair Share Act requiring facilities over fifty megawatts to commit to paying at least eighty-five percent of projected power costs for a decade, one entry in a running tally of state moratoria, tax changes, and ballot measures that has become the closest thing to a scoreboard for this fight. Virginia retained its sales tax exemption while adding an energy consumption tax of roughly a cent per kilowatt-hour capped at six hundred million dollars annually. Arizona and Illinois paused data center tax incentives. South Dakota passed a law allowing local governments to regulate or ban rather than imposing a statewide prohibition. New Hampshire moved the opposite way with an off-grid electricity providers law easing self-supplied power.
The restriction efforts also fail regularly, which the coverage tends to underreport. Maine’s governor vetoed a state moratorium. Ohio’s proposed constitutional amendment banning facilities over twenty-five megawatts gathered roughly seventy thousand of the four hundred thirteen thousand signatures required and missed the 2026 ballot. Pennsylvania’s statewide hyperscale moratorium was rejected in committee two to nine on constitutional and local-authority grounds. Sangamon County, Illinois voted down a six-month moratorium and approved a five-hundred-million-dollar campus the same evening.
So the accurate description is not that communities are blocking data centers. It is that approval has stopped being free, that the terms are being renegotiated in public, and that the venue has moved from a county board to a ballot. That shift matters procedurally as much as substantively, because a county board can be lobbied, briefed, and negotiated with, and an electorate cannot.
The information asymmetry that makes it bitter
One structural feature turns an ordinary siting dispute into a trust problem, and it is worth isolating because it is fixable and mostly has not been fixed.
Project water and power figures are frequently confidential during negotiation, sometimes under non-disclosure agreements signed by local officials. A community is asked to approve a withdrawal and a load whose magnitude it cannot verify, by representatives who have seen the numbers and cannot repeat them.
Pennsylvania considered legislation prohibiting local elected officials from signing non-disclosure agreements with developers. It had bipartisan sponsorship, passed a Senate committee, and stalled on a tie in House Judiciary after opposition from business groups arguing that confidentiality is necessary for economic development competition.
Both positions are defensible on their own terms. A developer negotiating simultaneously with several jurisdictions has a real commercial interest in not publishing its requirements. A resident asked to accept an unnamed quantity of groundwater withdrawal has a real interest in knowing the number. There is no clever resolution, and the absence of one is why the same argument recurs in every county.
The long history of large extractive facilities arriving in rural jurisdictions supplies the pattern, and the pattern is that the terms get renegotiated after the community discovers what it agreed to, usually from a weaker position. The company towns built around a single employer with a resource requirement are the long-run version, and the resemblance is close enough that several county boards have started citing it explicitly.
Affordability, which is the vector’s real fuel
Data center politics attached itself to an existing grievance rather than creating a new one, and that is why it moves votes.
Electricity prices rose materially in several regions, and capacity market outcomes are the transmission mechanism. When an auction clears short of its reliability target, prices rise for every customer in the zone. Data centers contributed substantially to the demand that tightened those auctions. They were not the only contributor, since generation retirements, transmission costs, fuel prices, and weather all matter, and the attribution question is genuinely contested.
The scale of the political reaction has been documented across primary season, with reporting on how the issue reshaped 2026 races finding candidates in both parties winning on data center restrictions and at least one state authority official losing a seat he had previously held comfortably after backing a project.
What is not contested is the political arithmetic. A voter receiving a higher bill and reading about a facility that consumes as much electricity as a small city does not require a causal econometric analysis to form a view, and no candidate has an incentive to supply one. That is not a criticism of voters. It is a description of what happens when a diffuse cost meets a visible cause, and it is the same dynamic that has attached to every large industrial facility with a legible footprint.
Which produces a policy proposal that keeps surfacing across party lines: require large new loads to bring their own new generation. The Nevada governor’s race featured a candidate promising legislation to that effect. PJM’s market monitor has argued for it. The logic is sound, since a load that adds its own supply does not tighten the market and therefore does not raise anybody’s price.
The objection is equally sound. No other class of customer faces that obligation, thresholds are arbitrary, and an aluminium smelter or a large industrial extraction operation with comparable draw would either face the same rule or receive an exemption somebody has to justify. That is the shape of the argument and it is not going to resolve cleanly.
Vector two, and the export control regime
The geopolitical vector operates on a different clock and through a completely different instrument, which is a licence.
The regime has become more granular rather than simply tighter. In July 2026 the Bureau of Industry and Security moved the United Arab Emirates into Country Group A:5, the most favourable export tier, and created a supplement naming entities permitted to receive advanced computing items without a licence at all. Saudi Arabia is not in that group and has no equivalent listing. What it has instead is a November 2025 authorisation permitting its national AI champion, alongside the UAE’s G42, to purchase up to the equivalent of thirty-five thousand GB300-class accelerators each, subject to security requirements, reporting, and compliance monitoring.
A rule and a licence are different instruments. A rule is durable and predictable and can be relied on for capital planning. A licence is discretionary, revocable, and creates a permanent relationship with the issuing agency. Two states with similar ambitions and similar capital are operating under structurally different regimes, and that difference is a policy instrument rather than an accident.
Enforcement has changed character as well. The Department of Justice’s national security enforcement policy has moved export violations out of the quiet civil settlement category, and individual prosecutions have followed. Compliance, audit, and legal review are becoming recurring operating costs rather than transaction expenses.
The consequence for anyone building is that jurisdiction is now an architecture decision. Which chips can be deployed where, which models can run on them, and which data can cross which border are questions with multi-year lock-in and refactoring costs that can exceed the original deployment budget. That is the same material and regulatory fragmentation that reshaped critical minerals, arriving in a different industry with the same mechanics.
Sovereign compute, and the queue behind the queue
Every major economy has now announced a national compute program, and the collective effect is competition for the same scarce hardware.
The European Union unveiled a two-hundred-billion-euro AI Continent Action Plan with thirteen AI Factories established across seventeen member states. Saudi Arabia announced over fifteen billion dollars in new investments including a partnership with Google Cloud and plans to deploy five hundred megawatts each of AMD and NVIDIA capacity. The UAE is developing a twenty-six square kilometre campus in Abu Dhabi with five gigawatts of planned capacity, with Stargate UAE targeting an initial two hundred megawatts. India, Japan, and France have their own programs.
The physical problem is that export-cleared, high-bandwidth-memory-heavy accelerators are supply constrained, and every sovereign program is bidding for the same units. A licence that is theoretically approvable still queues behind allocation, which means the binding constraint on national AI ambition is frequently manufacturing capacity rather than policy. High-bandwidth memory is the specific chokepoint, produced by a small number of suppliers, and it sits alongside the specialty gases, substrates, and minor metals that gate advanced packaging regardless of how many licences get issued.
Underneath that sits the concentration nobody has solved. Advanced logic manufacturing remains overwhelmingly concentrated in Taiwan, fab construction elsewhere is proceeding slowly, and the semiconductor supply chain has a single point of geographic failure that a decade of policy has not meaningfully diversified. The materials underneath it are concentrated separately and add their own chokepoints, which is the structural reason chip policy keeps discovering new dependencies after it has addressed the previous one. Any serious disruption there stops the buildout everywhere, on a timescale measured in quarters rather than weeks.
There is also a physical security dimension that the sovereignty debate largely skipped until recently. Concentrating enormous compute capacity in a region with an active missile threat is a different risk profile from concentrating it in Iowa, and the February 2026 strikes in the Gulf made that concrete rather than theoretical.
Vector three, and the efficiency problem
The third vector is the one that does not announce itself, and it is the reason the first two might not matter.
The buildout is premised on compute demand scaling with capability. If capability improvements come increasingly from algorithmic efficiency, architectural changes, and inference optimization rather than from raw floating-point operations, the relationship between capability and capital expenditure loosens, and a great deal of hardware gets bought for a curve that bent.
The demonstration event was DeepSeek’s R1 release in January 2025, which showed competitive model performance achieved on constrained hardware, though several of the cost claims circulated at the time were misleading and the comparison was less clean than the coverage suggested. The more consequential follow-on was a model released in April 2026 serving queries on Huawei’s Ascend architecture, which established that a frontier-class model can be built around non-American silicon.
The strategic implication for the export control regime is uncomfortable and has been argued at length: controls restrict computational resources without preventing capable models, because laboratories adapt around hardware constraints through efficiency work rather than being stopped by them. That is a criticism of the instrument rather than of the objective, and it is contested, since restricting compute plausibly slows an adversary even if it does not stop one. The historical record on export restriction as an instrument is mixed in exactly this way: controls reliably impose cost and reliably accelerate domestic substitution in the restricted country, and which effect dominates depends on how long the restriction holds and how substitutable the input is.
The implication for the buildout is more direct. Every efficiency gain reduces the compute required per unit of capability. Whether that reduces total compute demand depends entirely on whether cheaper inference expands usage faster than it reduces cost per query, which is the standard rebound question, and the honest answer is that nobody knows. The investors underwriting five-year debt against hardware are taking a position on that question whether or not they have articulated it.
Where the three vectors of data center politics interact
The vectors are usually analysed separately and their interactions are what determine outcomes.
Politics and geopolitics reinforce each other in one specific way: national security framing is the strongest available argument against local opposition. A project characterised as strategic infrastructure in a competition with China is politically harder to block than a project characterised as a warehouse full of computers owned by a company with a market capitalisation larger than the state’s budget. Federal preemption arguments and expedited permitting proposals both run through that framing.
They also work against each other. Export restrictions and sovereign programs push capacity offshore, and capacity built in the Gulf or Europe is capacity not built in a county that would have fought it. Domestic opposition is, in that sense, an offshoring pressure, which is an outcome nobody in the domestic argument is optimising for.
Efficiency interacts with both. If the compute requirement per unit of capability falls, the political fight gets smaller because the load gets smaller, and the geopolitical fight gets harder because controls become less effective. A world with abundant cheap inference is a world with less local opposition and less leverage over adversaries, which is not the combination either camp is planning for. The efficiency-versus-demand-growth question has the same structure in every materials-intensive industry, and the historical answer has usually been that cheaper inputs expand consumption rather than reducing it.
And the timing mismatch is the structural problem. Local political cycles run two to four years. Export control regimes change with administrations. Model architecture shifts on a horizon of months. Data center capital commitments run fifteen to thirty years on the building, five to twenty on the power contract, and five or six on the silicon inside, assuming the depreciation schedule holds. Every clock in the political and technological environment is faster than the clock on the asset.
What the operators are doing about it
The industry response is legible and worth cataloguing without endorsement, because it is the practical content of this vector.
Community benefit agreements have become standard, with commitments on water recycling, noise mitigation, workforce training, and direct payments to school districts. Some are substantive and some are public relations, and the distinction is usually visible in whether the commitment is enforceable.
Rate structures are being negotiated that shift cost risk onto the facility. New Jersey’s minimum-take requirement and the special large-load tariffs several utilities have constructed are the visible examples, covering contract duration, exit fees, and collateral, and they amount to an attempt to make a data center behave like a creditworthy long-term industrial customer rather than a load that might leave.
Bring-your-own-generation is the technical response to both the affordability argument and the queue, and it is also the response that produces on-site gas turbines, which is a different local fight with a different set of objections. Air permits, emissions monitoring, and turbine noise replace capacity prices and interconnection studies, and the firm generation alternatives that would avoid combustion are either slower, smaller, or geographically limited.
Geographic diversification is the response to concentration, and it is why capacity is moving toward jurisdictions with available power, permissive permitting, and cool climates, which is a search for the same combination of inputs that has always determined where energy-intensive industry locates, which is the same logic that governs any siting decision where the physical inputs dominate, and which has historically produced industrial geographies that outlast the reason they were created.
Vertical integration is the strategy nobody calls one. An operator that owns its generation, its water rights, and its interconnection has removed three negotiations from the schedule, which is expensive up front and is why the largest players are increasingly buying power assets outright rather than contracting for output. The same logic drove twentieth-century industrial firms to buy mines rather than sign supply agreements.
And silence is a strategy. Projects announced late, structured through shell entities, and negotiated under confidentiality reduce opposition until permits are issued, at a cost in trust that the next project in the same county pays.
What a project actually has to clear
Setting the three vectors against a single hypothetical project makes the compression concrete, and it explains why announced capacity and built capacity have diverged.
Land and zoning come first, and this is where the ballot measures bite. A conditional use permit, a rezoning, or an incentive package can now trigger a referendum in jurisdictions that allow citizen initiatives, and twenty-three states do. A project that would have been a routine county board item in 2020 can now become a ballot question, which adds an election cycle to the schedule regardless of the outcome.
Power comes second and is the longest pole. An interconnection position, a utility contract, and increasingly a special large-load tariff with minimum-take obligations and exit fees. Bring-your-own-generation shortens the schedule and substitutes an air permit fight for a rate case.
Water comes third and is jurisdiction-specific to a degree that surprises developers. A withdrawal permit in a prior-appropriation state is a different instrument from one in a riparian state, and in some places it means purchasing a senior right from an agricultural holder, which is legal, orderly, and locally understood as a data center buying a farm’s water. The aquifer drawdown question is separate again and turns on recharge rates rather than on permits.
Hardware comes fourth and is where the geopolitical vector applies, through export classification, end-user screening, and in some jurisdictions location verification requirements. The minor metals and specialty materials inside the equipment carry their own origin and content rules that most procurement teams discover late.
And the financing sits across all four, because a lender is underwriting the whole sequence rather than any single approval. A project with power and no permit is worth nothing, and so is a project with a permit and no interconnection date. The long record of infrastructure projects that failed at one stage of a multi-stage approval is the relevant base rate, and the base rate is not encouraging.
The claims that do not hold up
An audit, because this subject generates confident assertions from every direction.
Communities are blocking data centers overstates it. Approvals continue at scale, moratoria fail regularly, and the accurate description is that terms are being renegotiated rather than that projects are being stopped.
Data centers caused your electricity bill to rise is directionally supported and routinely overstated. They contributed to demand that tightened capacity markets, alongside retirements, transmission costs, fuel prices, and weather.
Export controls have failed is a stronger claim than the evidence supports. They demonstrably restricted computational resources available to constrained laboratories. Whether restricting resources achieves the strategic objective is a different question with a genuinely unresolved answer.
Export controls are working is equally overstated, for the mirror reason.
DeepSeek proved compute does not matter misreads the finding. It demonstrated that capability is not a pure function of compute, which is a much narrower and still significant claim.
Sovereign AI means technological independence overstates what any current program achieves, since essentially all of them remain dependent on a small number of American-designed accelerators and a single fabrication geography, and buying capacity is not the same as controlling a supply chain.
Data centers create jobs is true and small. Construction employment is substantial and temporary; operational employment is modest and permanent. The electrical and mechanical trades that build them are genuinely constrained, which is a separate labour story from the one in the economic development brochure.
Data center politics is simply NIMBYism dismisses the specific and checkable objections about water, capacity prices, and abatement terms by assigning a motive rather than answering the point.
The federal government will preempt local control assumes an outcome that has been proposed and not enacted, and that runs into state authority over siting and retail rates.
What the squeeze is actually telling us
Assemble the three vectors and what they share is that none of them is about data centers.
The political vector is about electricity affordability and about who captures the benefit of a tax abatement, which are old questions with a new object. The geopolitical vector is about whether technological leadership can be maintained through export restriction, which is a question with a long and mixed record predating semiconductors. The technological vector is about whether capability scales with capital, which is the oldest question in industrial investment.
Data center politics is where those three arguments happen to be colliding right now, which means the outcome will be determined substantially by how those arguments resolve rather than by anything specific to the facilities. Data center politics is a venue rather than a subject.
The practical consequence for anybody reading a project announcement is a checklist. Ask whether the load is bringing its own generation or drawing from a constrained market, because that determines the local political trajectory. Ask which jurisdiction the hardware sits in and under which instrument, because a rule and a licence carry different risk. Ask who signed a non-disclosure agreement and what it covers, because that predicts how the trust breaks. And ask what the capital commitment assumes about compute intensity per unit of capability, because that assumption is being tested continuously by people with no interest in whether the buildings get paid for.
The ten-lecture briefing on how AI data centers work runs the physics, the money, and the politics in sequence because they resolve in that order: the thermodynamics set the load, the load set the financing, and the financing arrives in a county that gets a vote.
A commissioner in Wisconsin, a licensing officer at Commerce, and a researcher publishing an efficiency result have nothing to do with each other and no knowledge of each other’s schedules. All three are, this year, in a position to determine whether a particular building gets built and whether it earns back what it cost.
Leave a Reply