Google paid roughly seventy-eight million dollars in property taxes to Caldwell County, North Carolina, and received about seventy-three million of it back under a rebate agreement. The county kept around five million.

That is not a scandal and it is not a secret. It is a negotiated economic development agreement, approved in public session, of a type that hundreds of jurisdictions have signed. What it illustrates is that the question of who pays for a data center has an answer, that the answer is written down in specific instruments, and that almost nobody reads them before forming a view.

Data center cost allocation is not one question. It is five, and they resolve through completely different mechanisms operating on completely different timescales. There is an electricity bill, a tax bill, a water bill, an infrastructure bill, and a bill that only arrives if the facility leaves early. Each has its own payer, its own paper, and its own failure mode, and conflating them is why the public argument produces so much heat and so little resolution.

Data center cost allocation bill one: electricity

The mechanism by which a data center raises somebody else’s electricity bill is indirect, which is why it took so long to become political.

A large new load tightens regional supply. Capacity auctions clear higher. Every customer in the zone pays the higher clearing price. No transfer from a residential customer to a data center appears anywhere in the accounting, because none occurs. What occurs is a price effect distributed across a market.

That indirectness is why data center cost allocation resisted regulation for as long as it did. A rate case is designed to allocate identifiable costs to identifiable customers, and a capacity price effect is neither. It took auctions clearing visibly short, and the resulting increases appearing on bills in the same news cycle as a project announcement, before commissions treated it as a rate design problem rather than a market outcome.

The regulatory response has been the fastest-moving development in American utility rate design in decades. As of mid-2026, roughly twenty-three states had approved at least one large load tariff, a dedicated rate class for very large customers designed to assign the costs of serving them directly rather than spreading those costs across the general rate base, with several more proposals pending.

The Database of Emerging Large-Load Tariffs, assembled by the Smart Electric Power Alliance and the North Carolina Clean Energy Technology Center, catalogs the resulting architecture, and a recognizable archetype has emerged from the filings. In the March 2026 public update, thirty-three of seventy-seven filings carried numeric minimum-bill requirements, averaging around eighty percent of contracted capacity, and thirty-seven included collateral requirements. That is a rate design archetype assembling itself in real time across dozens of jurisdictions, which is unusual, since utility rate structures normally change on a generational timescale and the regulatory apparatus was built for incremental load growth.

The analysis of what that archetype looks like across filings identifies the components clearly enough to list. Minimum billing, fixing monthly payment at a percentage of contracted load regardless of consumption. Extended contract terms aligned with the life of the infrastructure being built. Collateral, in letters of credit or cash. Exit fees. And provisions governing contract modification and capacity reassignment.

Virginia’s GS-5 rate class is the reference implementation, approved by the State Corporation Commission to take effect in January 2027. It applies to loads at or above twenty-five megawatts, requires fourteen-year contracts, and takes-or-pays a minimum of eighty-five percent of contracted transmission and distribution capacity and sixty percent of generation demand regardless of actual usage, with collateral reported at one and a half million dollars per megawatt. For a five-hundred-megawatt campus that is seven hundred and fifty million dollars posted before the first rack ships, which changes the capital structure of the project and pushes the financing question back onto the operator’s balance sheet.

What the tariff fight is actually about

The design parameters look technical and each one is a distributional decision, which is why proceedings that used to be uncontested now draw intervenors.

Minimum demand percentage is the central battleground. Oregon’s proceeding is representative: staff and a coalition supported a ninety percent minimum, the utility proposed eighty percent arguing that peer utilities sit near there and that setting it too high could deter siting, and the data center coalition agreed with the utility while noting that no other customer class faces such a requirement at all.

Every position in that dispute is defensible. A higher minimum shifts more risk onto the customer and protects other ratepayers. A lower minimum keeps the jurisdiction competitive and leaves more stranded asset exposure with the utility and therefore with everybody else. A higher minimum also has a second-order effect worth noting: it encourages customers to contract for less capacity than they might need, which improves the utility’s risk position and worsens its planning information, since the forecast it builds against becomes systematically conservative. And the observation that no other rate class faces a take-or-pay obligation is factually correct and is the strongest argument the industry has, though the response is that no other rate class arrives at five hundred megawatts requiring generation that would not otherwise be built.

The eligibility threshold is its own quiet fight. Utah legislated large loads at one hundred megawatts and above. Virginia’s GS-5 applies at twenty-five. Minnesota directed its commission to set a threshold. Where the line falls determines which facilities are covered and creates an obvious incentive to design just underneath it or to split a campus into separately metered parcels, which is the standard behaviour around any regulatory threshold in an industrial context.

Contract duration works the same way. Oregon staff recommended fifteen-year minimums for loads above twenty megawatts on the reasoning that stranded asset risk scales with load size. Longer contracts align customer commitment with the depreciation schedule of the assets built to serve them, which is precisely the point, and they also require a company to commit for three times the useful life of the hardware inside its building.

Pennsylvania’s Public Utility Commission adopted a model framework in April 2026 establishing that interconnection upgrade costs are recovered directly from large load customers rather than from the general rate base, with deposits and collateral sufficient to cover upgrade costs so that projects which do not proceed do not strand those costs on other customers.

Capacity reassignment provisions are the underrated innovation. Some tariffs permit a customer to reduce or reassign a portion of contracted capacity without penalty, require the utility to attempt reassignment beyond that threshold, and reduce or waive exit fees when the departing customer supplies a successor. That converts a binary default into a transferable position, which is a genuinely better instrument than either a hard lock-in or a free exit. One utility’s schedules permit reassigning or reducing up to twenty percent of contracted capacity without penalty under notice conditions, require the utility to attempt reassignment beyond that, and impose exit fees otherwise.

Bill two: taxes, and the instruments that hide the number

Property tax treatment is where the largest sums move and where the accounting is most opaque, and the opacity is structural rather than conspiratorial.

The straightforward instrument is an abatement, reducing the tax bill by some percentage for a set term. Arkansas law permits up to sixty-five percent abatement for as long as thirty years on projects financed through industrial development revenue bonds, and PILOT agreements reached for Google projects in the state carry the maximum sixty-five percent for thirty years on both real and personal property.

A payment in lieu of taxes agreement works differently and is easy to misread. The local government takes title to the property, which makes it public and therefore exempt, and leases it back to the company, which pays a negotiated fee instead of taxes. In one Ohio case a facility received a fifteen-year, seventy-five percent property tax abatement alongside a PILOT of five hundred thousand dollars annually.

Industrial revenue bonds are the third structure and produce the largest numbers. Dona Ana County, New Mexico approved approximately one hundred sixty-five billion dollars in industrial revenue bonds for a data center project, with associated abatements described as undisclosed and running as long as thirty years.

The aggregate figures where they exist are substantial. Virginia’s data center sales tax exemption reached roughly $1.6 billion annually. Georgia localities were estimated to lose $1.1 billion in 2026 and $1.4 billion in 2027 from state-awarded exemptions. Data centers owned by four large operators in Oregon received $616 million in property tax abatements between 2016 and 2025, with annual program costs rising several hundred percent across that period.

The measurement problem is the part that should trouble everybody regardless of position. Arkansas does not track the impact of PILOT agreements on property tax collections at the state level. In several states the cost estimates surfaced only because a legislator requested them or a records request produced them. Accounting standards require governments using generally accepted principles to disclose tax abatements in their financial reports, and compliance is uneven.

The case for the abatements, stated properly

The critique is easier to write than the defense, so the defense deserves its strongest form.

The counterfactual argument is the real one. If a facility would not have located in the jurisdiction without the abatement, then the abated revenue was never available to lose, and whatever the county collects, plus construction employment, plus utility revenue, plus any assessed value that does eventually appear, is a gain against a baseline of nothing. Virginia’s original exemption in 2008 carried a fiscal note estimating a forgone $2.8 million against a project the state was otherwise going to lose to North Carolina.

The service-demand argument is also legitimate. A data center generates minimal traffic, few emergency calls, no students, and no demand on the largest line items in a county budget. Bartow County, Georgia’s policy statement makes exactly this case: substantial revenue against comparatively little service demand, with an explicit intent to increase homestead exemptions as the revenue arrives. Whether that intent survives a change of commissioner is a different question, and the history of resource-revenue windfalls being absorbed rather than distributed is not encouraging on that point.

The depreciation point is the technical one that both sides underuse. Where equipment is assessed at a percentage of fair market value with statutory depreciation applied, the tax digest impact is a function of depreciated value rather than gross capital cost, which means the headline investment figure and the eventual assessment are very different numbers, and the assessment declines every year as the servers age. The equipment inside is also replaced on a cycle shorter than most abatement terms, which means the digest is a function of reinvestment as much as of the original build. That depreciation curve is also why the useful-life assumption fight in the financing layer has a fiscal consequence nobody discusses: a shorter economic life for the equipment means a faster-declining tax digest for the county that hosts it.

The honest counter is the timing. During an abatement period running ten to thirty years, the community provides road maintenance, emergency response capacity, and utility infrastructure to a facility that is not yet contributing proportionally, and the service demands arrive before the revenue does, which is the same sequencing problem that afflicts any large industrial facility with a long ramp. Whether that sequencing is a subsidy or an investment depends on what happens at the end of the term, which nobody in the room when it is signed will still be in office to see.

Bill three: water, and the rate structure underneath it

Water is the smallest of the five bills in dollar terms and frequently the largest politically, and the reason is that the rate structure makes the cost invisible.

Municipal water systems are largely fixed-cost businesses. Treatment plants, mains, and pumping stations cost what they cost regardless of throughput. A large new customer improves the utilization of that fixed base, which is genuinely good for the system’s economics and can lower unit costs for everybody on the network, and a volumetric rate that reflects average cost therefore undercharges relative to the capacity the customer requires at peak.

Where the withdrawal is from groundwater, the cost is not on any bill at all, because a permit to withdraw is not a purchase. An aquifer drawn down faster than it recharges is a stock being depleted, and the depletion shows up as a cost to future users rather than to the current one. Prior appropriation states add a market layer, since a new entrant holds a junior right and can only obtain seniority by purchasing it, generally from an agricultural holder, which converts a public resource question into a private transaction the county has no formal role in. The same structure governs mineral and extraction rights and produces the same local ambivalence.

Reclaimed water is the mitigation with the clearest economics, since it uses a resource that had no competing use and improves the utilization of treatment infrastructure. It also requires the distribution network to exist, which is a capital project somebody has to fund, and the funding question is a rate case. Purple pipe extensions are expensive per mile and only pencil where a large anchor customer justifies them, which means the data center is frequently the reason the reclaimed system exists at all, and that is a genuine public benefit that the water accounting rarely credits.

Bill four: infrastructure, and who owns what afterward

Substations, transmission upgrades, road improvements, and water main extensions are capital projects with thirty-to-forty-year cost recovery, built for a customer whose relationship may be much shorter.

The Pennsylvania framework’s answer, now increasingly standard, is that interconnection upgrade costs are recovered directly from the large load customer with deposits and collateral sufficient to cover them. That resolves the funding question and leaves the ownership question, because the utility owns the substation afterward regardless of who paid, and the asset either serves a successor or does not. Where it does, the community has acquired grid capacity it did not pay for, which is the best case and is real. Where it does not, the community has acquired a substation serving nothing, which is the stranded infrastructure pattern that has emptied out industrial towns before.

California’s proceeding surfaced the refund issue that follows. Where a customer funds infrastructure and the utility later serves others from it, some portion is conventionally refunded. The California commission provisionally found a maximum refund of seventy-five percent of total capital expenditure appropriate, reasoning that large load customers present unique stranded cost risks, already receive favourable energy rates, and require investment at a scale that justifies limiting refunds.

Underneath all of it sits the equipment lead time problem, which changes the economics of any upgrade because a transformer ordered for one customer and delivered four years later may arrive for a project that no longer exists.

Bill five: the stranded cost, and the one nobody has paid yet

This is the bill that has not arrived, and it is the reason every tariff proceeding in the country now contains the phrase stranded asset risk.

The structure is straightforward and uncomfortable. A utility builds generation, transmission, and substation capacity for a data center, financed over decades and recovered through rates. The customer signs for five, ten, or fourteen years. The silicon inside the building has an economic life of four to six. If the load leaves, reduces, or never fully materializes after the assets are built, the assets remain and somebody pays for them, and that somebody is the remaining ratepayers.

The protections regulators are assembling against exactly this scenario are extensive and recent, and the historical precedent is why they are treating this seriously rather than theoretically. Utility commissions have been through stranded cost episodes before, in the aftermath of nuclear construction programs and again during restructuring, and the resolutions were expensive and politically brutal. The institutional memory is real, and it is why commission staff in these proceedings are frequently more conservative than either the utility or the intervenors.

The protections now standard in tariffs are all addressed to this single risk. Minimum billing creates a revenue floor independent of consumption. Extended contract terms align commitment with asset life. Collateral covers unpaid obligations. Exit fees penalize early departure. Capacity reassignment creates an alternative to default. Each is an attempt to make a customer whose planning horizon is short behave like one whose horizon matches the infrastructure.

Whether they are sufficient is unknown, because none has been tested by an actual departure at scale. A fourteen-year contract with collateral at one and a half million dollars per megawatt looks robust against a five-hundred-megawatt facility walking away, and considerably less robust against a general repricing in which many facilities reduce simultaneously and the utility cannot reassign capacity because nobody wants it.

That is the tail risk in data center cost allocation, and it is correlated rather than idiosyncratic, which is exactly the property that makes collateral requirements less protective than they appear.

The verification problem

A structural difficulty runs underneath all five bills and deserves naming, because it limits what any of this analysis can establish.

Cost shifting is extremely difficult to verify. Utility cost allocation methodologies are complex, contested, and jurisdiction-specific. Whether a particular tariff fully assigns incremental costs depends on assumptions about how those costs are measured, which are precisely the assumptions being litigated. Harvard researchers examining the question have noted that in many markets verification is close to impossible with publicly available information.

The same applies to fiscal impact. Studies commissioned by industry find substantial net benefits, with one national assessment putting the sector’s contribution above two trillion dollars. Studies commissioned by opponents find substantial net costs. Both are typically methodologically defensible, because the result depends on the counterfactual assumed, and the counterfactual is unobservable.

Non-disclosure agreements compound it. In several documented cases, commissioners approved abatement agreements while under NDA and without accompanying economic impact assessments or cost-benefit analyses. The same confidentiality practice governs water and power figures, which means a single project can present three separate unverifiable numbers to the same board. A decision made on information the decision-maker could not share and the public could not review is not necessarily a bad decision, and it is one nobody can audit. Legislative efforts to prohibit officials from signing such agreements have been introduced in several states and have generally stalled against the argument that confidentiality is required to compete for projects, which is an argument with real force and no way to test it.

Which means the honest position on most specific claims in this area is that the number is contested and the methodology is where the argument actually lives. Anyone presenting a clean figure for what a data center costs or contributes is presenting a modeled result and usually not the assumptions. That is the same discipline the critical minerals literature requires of any demand forecast, and for the same reason: the number is downstream of a model, and the model is downstream of an interest.

What a resident can actually check

The information asymmetry is real and it is narrower than it looks, because most of these instruments generate a public record even when the negotiation did not.

The abatement agreement itself is usually a matter of record. If a deal required a vote by a city council, county board, or industrial development authority, that vote appears in minutes, agenda packets, and resolutions, typically published or available by request, and those documents frequently contain the executed terms.

Where the incentive was created by statute rather than negotiated case by case, the legislation and its fiscal note are public, and the agency administering it usually reports aggregate usage to the legislature.

State open records laws reach the rest. Every state has one, and the executed incentive agreement between an economic development agency and an operator is generally a public record even where the negotiation was confidential.

Utility filings are the most useful and least used source, and the technical constraints they document frequently explain project delays that get attributed to politics. A tariff proceeding is a public docket containing the utility’s cost justification, the intervenor testimony disputing it, and the commission’s reasoning, which together constitute a far more rigorous examination of the cost allocation question than any news coverage of it.

And accounting standards require governments using generally accepted principles to disclose forgone revenue from tax abatements in their annual financial reports. Compliance varies, and where it exists the number is in the notes.

None of that resolves the counterfactual problem. It does mean that the specific terms of a specific deal are usually knowable, and that most public argument about data center cost allocation proceeds without anybody having read them.

The claims that do not hold up

An audit, because the confident assertions run in both directions.

Data center cost allocation is a solved problem in states with large load tariffs overstates instruments that mostly take effect in 2027 and have never been tested by a departure.

Data centers pay nothing in taxes is false. Abatements are partial and time-limited in most jurisdictions, sales tax exemptions typically cover equipment rather than everything, and utility taxes and payroll taxes are unaffected.

Data centers pay their own way is equally unsupported as a general claim, since it depends entirely on the specific instrument, the abatement term, and the tariff in force, all of which vary enormously by jurisdiction.

Ratepayers are subsidizing data centers is the strongest form of a claim that is genuinely hard to verify, and the direction is plausible while the magnitude is contested.

Large load tariffs solve the problem overstates instruments that are two years old, mostly untested, and varying widely in how much risk they actually transfer.

Tax abatements are always a giveaway ignores the counterfactual question, which is the only question that matters and the one nobody can answer.

The jobs justify the incentives is difficult to sustain at the ratios involved, and most serious economic development arguments have shifted to the tax base and utility revenue rather than employment. Construction employment is genuinely substantial and genuinely temporary, and the specialized trades involved are in national shortage, which means a project frequently imports its workforce rather than hiring locally.

Data centers do not use public services understates road wear during construction, the heavy-haul permits required to move transformers and turbines, emergency response capability that must be maintained for a high-value facility, and the water and power infrastructure that is public in most jurisdictions.

Communities can just say no is true and incomplete, since state-level exemptions frequently bind localities that had no vote on them, which is the specific grievance driving several state legislative fights. A county that never voted on a state sales tax exemption still absorbs the service demand of the facility the exemption attracted, and that mismatch between who granted the incentive and who bears the cost is the structural complaint underneath a great deal of otherwise inarticulate local anger.

What data center cost allocation is actually telling us

Assemble the five bills and the pattern is that each one is a mechanism for deciding who bears a risk, and the risks are what actually differ.

The electricity bill allocates the risk that supply tightens. The tax bill allocates the risk that a facility does not deliver the promised base. The water bill allocates the risk that a resource depletes. The infrastructure bill allocates the risk that an asset built for one customer serves nobody. And the stranded cost bill allocates the risk that all of the above happen at once because the demand did not hold.

That last correlation is the thing most of the instruments handle poorly. Collateral, exit fees, and minimum billing all protect against an individual customer failing. None of them protects against a sector-wide repricing in which many customers reduce simultaneously, capacity cannot be reassigned because demand has fallen everywhere, and the utility holds assets built for a load that no longer exists. Financial instruments designed for idiosyncratic risk perform badly against correlated risk, which is precisely the failure mode the asset-backed lending against depreciating hardware exhibits one layer up the capital stack, which is a lesson that gets relearned expensively about once a decade, most recently in commodity markets where every producer hedged against their own idiosyncratic risk and none against the cycle.

Which suggests the useful question for anybody evaluating a specific project is not whether data centers pay their fair share, because that phrase does not designate anything checkable. It is: which instrument governs each of the five bills here, what does it assume, and what happens under it if the load reduces by half in year six.

The ten-lecture briefing on how AI data centers work runs the physics, the money, and the politics in sequence because the allocation question sits downstream of all of them. The thermal density set the load, the load required infrastructure, the infrastructure required financing over decades, and the financing has to be recovered from somebody across a period longer than anybody involved can forecast. Every instrument described here is an attempt to write down, in advance, who that somebody is under conditions nobody can specify.

A county kept five million dollars out of seventy-eight. Whether that was a good deal depends entirely on what the county would have collected from an empty field, and nobody in that room knew, and nobody knows now.

Electrical equipment is less than ten percent of what a data center costs to build, and roughly one hundred percent of the reason it does not get built.

That sentence is the whole lecture. The capital is available, the chips are shipping, the demand is contracted, and somewhere between a third and a half of the capacity announced for 2026 is not under construction, because a transformer ordered today may arrive in 2029 and there is nothing anybody can pay to change that.

Sightline Climate tracked twelve gigawatts of United States data center capacity announced across roughly a hundred and forty projects for 2026. About five gigawatts was actually under construction. Eleven gigawatts sat in the announced stage with no physical progress, against typical build times of twelve to eighteen months, and a quarter of those projects had disclosed no power strategy at all, which is a remarkable disclosure gap for a facility whose defining characteristic is electricity consumption. The semiconductor supply chain feeding those sites has been scrutinized far more closely than the electrical one, and the electrical one is what is binding.

Data center bottlenecks are therefore not a story about scarcity in the ordinary economic sense, where a price rise summons supply. They are a story about a synchronized demand surge meeting a manufacturing base that was sized, deliberately and rationally, for twenty years of flat load growth.

The distinction matters because it determines what relief looks like. A shortage caused by underinvestment resolves when capital arrives, and capital has arrived in quantities without modern precedent. A shortage caused by physical lead times resolves when the lead times elapse, and no amount of capital shortens the certification cycle for a transformer production line or the apprenticeship of an electrician. Data center bottlenecks are the second kind, which is why the most-funded projects in the world are slipping on the same schedule as everybody else.

What actually gates a build, and the order it binds in

The intuitive ordering is wrong, and correcting it is the useful part.

Capital is not the constraint. Alphabet, Amazon, Meta, and Microsoft collectively guided to more than $650 billion of AI infrastructure capital expenditure for 2026, and OpenAI’s Stargate carries a SoftBank loan commitment measured in tens of billions. Money is abundant and it does not build transformers faster.

Chips stopped being the constraint. GPU supply eased after 2023 primarily because TSMC expanded advanced packaging capacity, which had been the true bottleneck behind the shortages rather than wafer fabrication itself, doubling output in 2025 with a further doubling planned. Demand still outruns supply by an estimated factor of roughly one and a half through 2027, and hyperscalers have locked up much of the available allocation through multi-year commitments, which squeezes smaller providers and is a structural disadvantage for anybody without a decade-long vendor relationship. The minor metals, specialty gases, and substrate materials behind advanced packaging remain their own constraint, and hafnium and the other exotic inputs to the gate stack sit further upstream again. But a buyer with a signed power agreement and a finished data hall can now get accelerators on a materially shorter timeline than a grid connection.

What gates the build is the electrical chain: large power transformers, generator step-up units, medium-voltage switchgear, circuit breakers, protection equipment, and the substation work to install them. Under those sits the equipment to generate the power in the first place, and under that sits the labor to install and commission all of it.

Every one of those has a lead time now measured in years, and none of them responds to urgency in a way that helps a project scheduled for next year.

Worth naming the ordering explicitly, because it inverts the way these projects get discussed. Land is available. Capital is available. Chips are constrained but obtainable. Power contracts are negotiable. Interconnection is slow and at least has a queue position you can hold. Equipment is the wall, and labor is the wall behind the wall. A project plan that treats the accelerators as the long pole is a plan written in 2023.

Transformers, and the material underneath them

Large power transformers are the tightest constraint and the most instructive, because the shortage traces cleanly to a specific input.

Delivery windows for the largest units ran roughly twenty-four to thirty months before the surge. They now run three to five years, with average United States lead times near a hundred and twenty-eight weeks and the most constrained categories quoted into 2029 or 2030. Switchgear is effectively sold out through 2028 at some suppliers. Medium-voltage equipment and generator step-up units carry similar multi-year queues.

The manufacturing constraint underneath is grain-oriented electrical steel, the specialized silicon steel used in transformer cores. It is produced through a complex, capital-intensive process by a small number of global producers, and without it a transformer manufacturer cannot expand output regardless of order book. That upstream constraint is why the shortage cascades identically across large power transformers, generator step-up units, and distribution transformers, and why different sectors of the economy end up bidding against each other for the same steel.

The geographic concentration compounds it. China controls roughly sixty percent of global transformer production capacity, which places a critical input for American AI infrastructure inside a supply relationship that the export control regime has already disrupted in adjacent categories. Copper windings add a second commodity exposure, and the minor metals and specialty alloys in the rest of the electrical chain add several more, including the rare earth magnets in every motor and generator the buildout consumes.

Domestic expansion is proceeding and it is slow for a structural reason. Building transformer manufacturing capacity requires new production lines, certification, and a trained workforce, which is a multi-year industrial investment cycle. The lead time to fix a lead time problem is itself a lead time.

The physical characteristics explain why nothing about this compresses. A large power transformer weighs hundreds of tons, is built to a specification unique to its installation, requires precision core stacking and winding, and then has to pass a testing and commissioning cycle that cannot be shortened without accepting failure risk on a component whose failure takes a substation offline. It then has to be transported, which for the largest units means specialized rail cars or heavy-haul road moves that themselves require permits and route surveys. There is no version of this that arrives quickly.

Distribution transformers face a parallel squeeze from a different direction, since residential construction, electric vehicle charging, and grid replacement of aging stock all draw on the same production. A utility replacing storm-damaged equipment competes against a data center for the same factory slot, which is how a data center bottleneck becomes a visible local political grievance rather than an industry problem.

Turbines, and the backlog that reprices generation

If a project cannot get a grid connection, the workaround is self-generation, and that workaround has run into the same wall.

GE Vernova’s gas turbine backlog reached one hundred gigawatts in the first quarter of 2026, with the company expecting at least a hundred and ten gigawatts of orders and reserved slots, roughly three years of lead time, and about ten gigawatts of remaining availability across 2029 and 2030 combined. Wait times for the largest units have stretched as far as seven years, with the average around five, against a historical backlog of one to three.

The pricing response tells the story better than the queue does. Gas turbine prices are up roughly seventy-five percent for plants going online in 2030 or 2031. The estimated cost of a new gas-fired plant has more than tripled, from around eight hundred dollars per kilowatt in 2021 to something in the range of twenty-six hundred to twenty-eight hundred today.

That repricing has a consequence the discussion usually misses. Self-generation was the fast, cheap answer to the interconnection queue. It is now the slow, expensive answer to the interconnection queue, which narrows the gap between building your own power and waiting for the grid, and makes existing generation assets correspondingly more valuable.

The turbine manufacturers could reduce the backlog by adding capacity, and their reluctance is rational rather than obstructive. Between 2005 and 2020 United States power consumption grew by roughly a tenth of a percent annually. A manufacturer that builds factories for a demand curve that reverts to that baseline owns stranded plants. They are being asked to make a twenty-year bet on a four-year-old trend, by customers who cannot themselves agree on whether the trend holds.

That reluctance is the same calculation every supplier in this chain is making, and it is the reason the shortage persists against enormous demonstrated demand. A transformer manufacturer, a switchgear producer, a grain-oriented steel mill, and an electrical contractor all face the identical question: is this a permanent step change in load growth or a four-year surge that reverts. Each of them loses badly by guessing wrong in the expansionary direction, and each of them merely forgoes profit by guessing wrong in the conservative direction. Asymmetric downside produces conservative behaviour, which is exactly what the processing industries that consolidated through a long demand trough did for the same reason.

The labor constraint, which nobody can import

The bottleneck that gets least coverage and may matter most is that there are not enough electricians.

Microsoft’s president has publicly identified the shortage of electrical talent as the single largest obstacle to the company’s United States data center expansion, describing flying electricians in from seventy-five miles away or relocating them temporarily to keep projects moving. Oracle pushed completion timelines from 2027 to 2028 with labor shortages cited as a contributing factor.

The arithmetic is demographic and does not resolve quickly. Estimates put the additional electricians needed above three hundred thousand while roughly twenty thousand retire annually, and one commonly cited projection has one new entrant to the trade for every five retirements. Associated Builders and Contractors estimated construction needed roughly three hundred forty-nine thousand net new workers in 2026 alone, with other analyses putting the figure above four hundred thousand, and research on supply chain constraints curbing US development projecting a requirement rising toward 1.4 million by 2030.

The specificity is what makes it hard. A data center campus does not need generic construction labor. It needs licensed electricians with mission-critical experience, mechanical contractors familiar with high-density liquid cooling, controls engineers who can integrate power and thermal telemetry, commissioning agents who understand phased energization, and high-voltage substation crews. Construction costs reflect the scarcity, having risen from roughly $7.7 million per megawatt in 2020 to about $10.7 million in 2025, with further increases forecast, and a meaningful share of that escalation is labor rather than materials. Those are not interchangeable pools, and a market can post strong construction employment growth while lacking the specific teams a three-hundred-megawatt campus requires.

Unlike a transformer, this cannot be ordered early. An apprenticeship runs years, the instructors are drawn from the same shortage, and the wage premium the sector can pay pulls workers from residential and commercial construction rather than creating new ones. Data center projects with deeper budgets and harder deadlines are winning that competition, which is a redistribution rather than a solution.

The consolidation response has begun as well, with acquisitions in specialized electrical services aimed at securing crews rather than capabilities. When a firm buys another firm principally for its labor pool, the labor pool has become the scarce asset, and that is a reasonably reliable indicator of where a bottleneck actually sits.

Why the shortage was rational to create

The temptation is to read a five-year transformer queue as a planning failure, and the more accurate reading is that it is the correct response to twenty years of correct information.

United States electricity demand was essentially flat from roughly 2005 to 2020, growing around a tenth of a percent per year while efficiency gains offset economic growth. Every rational actor in the electrical supply chain sized capacity to that reality. Utilities bought just in time. Manufacturers ran lean. Nobody built speculative transformer capacity, because speculative transformer capacity would have been a decade of losses.

Then demand grew two percent in 2024 alone, and PJM’s load forecast attributed ninety-four percent of its projected thirty-two gigawatts of peak growth through 2030 to data centers, with data center growth outpacing new generation additions by roughly two to one. Dominion Energy in Virginia, the densest data center market in the world, has quoted waits beyond thirty-six months for new substation service and as long as seven years for a hundred-megawatt connection in its most constrained territory.

A supply chain optimized for flat demand cannot absorb that, and the optimization was not a mistake at the time it was made. This is the standard shape of an industrial bottleneck, and it recurs identically in critical minerals and in every processing industry that consolidated during a long demand trough: capacity gets rationalized during the lean period by firms behaving sensibly, and the rationalization is invisible until demand returns. The critical minerals sector spent two decades learning the same lesson and is still learning it.

The double-ordering problem

There is a measurement issue sitting underneath every number in this subject, and it is worth flagging because it cuts against the alarming version of the story.

Buyers facing multi-year lead times book capacity with several suppliers at once to guarantee delivery, then cancel the surplus. Utilities have begun placing speculative orders and paying to reserve factory slots before projects are approved, reversing decades of just-in-time procurement. Both behaviours inflate reported backlogs.

Which means the true depth of the shortage is genuinely hard to read. A hundred-gigawatt turbine backlog across ninety distinct customers in twenty-four countries is a real order book and it is not a reliable forecast of installed capacity, because some fraction of it is optionality rather than intent.

The same caution applies to the announced-versus-under-construction gap. Some of the eleven gigawatts sitting in announcement is genuinely blocked by equipment. Some is blocked by permits, some by financing, some by a customer contract that never closed, and some was never a real project. Announcements are cheap and they are a document with an author who wanted something.

The incentive to announce is real and worth stating. A gigawatt announcement supports a share price, secures a place in a state’s economic development pipeline, establishes a claim on utility attention, and costs nothing but a press release. There is no penalty for an announcement that quietly does not happen, and no register of the ones that did not. Any analysis built on announced capacity is therefore measuring intent plus marketing, and the same problem afflicts every forecast in a capital-intensive industry where announcing a project is orders of magnitude cheaper than building one.

Speed to power, and what it is worth

The scarcity has produced a repricing that is legible in real estate and worth naming, because it explains a great deal of transaction behaviour.

An asset with executed interconnection agreements, an energized substation, and documented electrical headroom commands a premium over an otherwise identical site without them. Proximity to substation corridors matters. Sites near transformer and switchgear supply nodes commission faster.

That premium is the market pricing time rather than capacity, and it explains why operators are buying powered land, retired industrial sites, and closed generating stations at valuations that make no sense on the real estate alone. What is being purchased is queue position, which is the same thing being purchased when an operator pays above market for an existing generating asset with an interconnection already attached.

It also explains the vertical integration. Crusoe has begun manufacturing its own switchgear to bypass conventional lead times. Operators are buying generation outright rather than contracting for output. Each of those removes a supplier from the critical path at considerable capital cost, and the calculation is straightforward when a sixty-megawatt facility delayed a month forgoes revenue in the millions.

The same logic drove twentieth-century industrial firms to buy their input suppliers rather than negotiate with them, and it produces the same result: capital intensity rises, flexibility falls, and the firm ends up owning assets it has no particular expertise in operating. It also concentrates risk, since a company that owns its switchgear factory has converted a supplier problem into an operational one, and the vertical integration that looked prudent during a shortage frequently looks like a distraction once the shortage clears.

The data center bottleneck cascade, and where it breaks

The bottlenecks interact, and the interaction determines which projects die.

A project needs land, a permit, an interconnection position, a transformer, switchgear, generation or a grid contract, cooling infrastructure, accelerators, and crews to install everything. Failing any one of those stops the project, and the failures are not independent, because the same electricians install the switchgear and commission the cooling, and the same substation work gates both the interconnection and the equipment installation.

That produces a specific failure mode. A project can hold a signed interconnection agreement, a completed study, financing, and hardware allocation, and still not exist, because roughly fifty-seven gigawatts of PJM projects have completed the study process and hold agreements while remaining stalled. Completing the queue turned out to be necessary and nowhere near sufficient.

It also produces a sequencing problem for anyone underwriting. The thermal design determines the electrical requirement, which determines the transformer specification, which has a three-to-five year lead time, which means the cooling architecture chosen in year one locks equipment orders that arrive in year four for hardware generations that do not exist yet.

And the workarounds have their own ceilings. Bypassing the grid entirely applies to only a small share of the current pipeline, on the order of a few percent. Behind-the-meter arrangements face regulatory constraints. Self-generation faces the turbine backlog. Every escape route is itself congested.

The cooling chain deserves a mention in the same breath, since the transition to liquid put a new set of components on the critical path. Coolant distribution units, cold plates, high-flow pumps, and the specialized manifolds that connect them are a young supply base scaling from small volumes, and the thermal architecture decisions that made those components necessary happened faster than the vendors could industrialize. Backup power adds another, with battery systems and uninterruptible supplies drawing on cell manufacturing capacity that the vehicle industry is also bidding for.

What breaks the bottleneck, and when

The relief timeline is knowable and it is not soon, which is the honest answer.

Manufacturing expansion is underway. GE Vernova, Siemens Energy, Eaton, Hitachi Energy, and others have announced capacity additions, and manufacturers of adjacent products have begun pivoting lines toward stationary power equipment. The consistent horizon for that relief is 2029 and beyond, because certification, workforce ramp, and line commissioning cannot be compressed.

Grain-oriented electrical steel capacity is the deeper fix and the slower one, involving the kind of heavy industrial investment that requires a decade-long demand thesis to justify.

The labor pipeline is the slowest of all, and it improves only through apprenticeship completions that started years ago, which means the 2029 electrician workforce is already substantially determined.

Which leaves demand-side adjustment as the fastest lever, and it is happening whether anybody likes it or not. Projects slip. Announcements quietly lapse. Capacity migrates to jurisdictions with available equipment and available crews, which is a siting logic driven by industrial inputs rather than by markets and which has historically produced durable industrial geographies. Design standards relax where redundancy can be traded for speed, with some operators accepting lower redundancy tiers or phased energization to get partial capacity earning while the rest waits. And a share of announced capacity turns out never to have been real, which resolves the shortage by reducing the demand rather than by increasing the supply.

That last mechanism is the one most likely to clear the data center bottleneck first, and it is the one nobody markets. Shortages of long-lead industrial equipment historically resolve through demand destruction more often than through capacity addition, because demand can fall in a quarter and capacity takes half a decade. Whether that happens here depends on questions being decided somewhere else entirely, in model architecture and inference efficiency, and on whether the contracted backlogs underwriting the buildout convert.

The claims that do not hold up

An audit, because this subject produces headline numbers with unstated denominators.

A five-year transformer backlog killed half of America’s 2026 data centers is the viral version and it overstates a real problem. Delays are real, the announced-to-construction gap is real, and attributing the entire gap to transformers ignores permitting, financing, and projects that were never funded.

GPUs are the bottleneck was true in 2023 and is not now. Advanced packaging capacity expanded, allocation is contracted, and the pacing item moved to the electrical chain.

The shortage is a planning failure misreads twenty years of rational behaviour under flat demand. The capacity that is missing was correctly not built.

Backlogs measure demand overstates order books inflated by double-ordering and speculative slot reservation.

Money will solve it is contradicted by the most-capitalized projects in the world slipping schedules. Stargate has essentially unlimited capital and cannot buy a transformer that has not been manufactured. As of April 2026 industry observers reported no significant physical progress on its data center buildouts, which is a data point about the limits of capital rather than about the project.

The bottleneck is temporary depends entirely on the timescale. Two years is not temporary for a five-year asset financed on three-year debt, and a delay of that length can consume the entire useful life advantage the project was underwritten on.

Onshoring will fix the supply chain understates how long building a transformer industry takes and ignores that the steel underneath it is the actual constraint. The same argument recurs in every critical materials reshoring proposal, and the answer is always that the upstream step is the one nobody wants to finance.

What the data center bottleneck is actually telling us

The reframing worth carrying is that the AI buildout is not a technology project encountering technology limits. It is a heavy industrial project encountering heavy industrial limits, and almost nobody involved in the software layer has any experience with those.

The constraint set is familiar to anyone who has built a refinery, a smelter, or a transmission line: long-lead custom equipment, a specialized labor pool that takes years to grow, an upstream material with a concentrated supply base, and a permitting environment with a political dimension. Anyone who has built a mine, a smelter, or a processing facility recognizes every item on that list. None of it is novel. What is novel is the speed at which capital arrived against it, and the inexperience of the people deploying it with the physical constraints they are deploying it into.

Which produces the specific asymmetry that defines the period. Software scales by copying, at near-zero marginal cost, on timescales of weeks. Everything the software now requires scales by manufacturing, at high marginal cost, on timescales of years. The buildout is the collision between those two clocks, and the slower one wins every time it is tested.

The ten-lecture briefing on how AI data centers work runs the sequence in the order the constraints actually bind, because that ordering is the analysis: the thermal density set the electrical requirement, the electrical requirement met a supply chain sized for a different world, and what got built is the intersection rather than the ambition.

The most sophisticated computing hardware ever manufactured is waiting on a steel mill. That relationship is the demand wall, and every data center bottleneck in this subject is a version of it.

A transformer is a steel core wrapped in copper wire, a technology essentially unchanged in principle since the nineteenth century, weighing several hundred tons and requiring a particular kind of silicon steel that a handful of mills produce. It is the least glamorous object in this entire industry, and in 2026 it is the thing that decides which announcements become buildings.

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.