The electricity bill arrives

The AI infrastructure buildout has reached the phase where it shows up on other people's bills, and the resulting political process is now a more important constraint on compute supply than anything happening in a fab.

the mechanism#

A datacenter campus needs a lot of power at one point on the grid. Delivering it requires transmission upgrades, substation construction, and often new generation. Those cost billions and take years.

Who pays is decided by state public utility commissions in rate cases. The options:

• The datacenter pays, through special contracts with minimum-take provisions and upfront infrastructure contributions.
• All ratepayers pay, spread across the customer base, which is how transmission has traditionally been socialized.
• Some blend, which is what actually happens.

Utilities generally prefer the blend, because socialized costs are easier to recover and because they earn a regulated return on capital investment — which means building more infrastructure is directly profitable for them regardless of who uses it.

Consumer advocates object. Datacenter operators object to bearing the full cost. Commissions split the difference, differently in every state.

why this is now the binding constraint#

Chips are available. Capital is available. What is not available is a grid interconnection on a useful timeline.

Interconnection queues in most US markets run years. Transformer lead times remain long. Transmission line construction requires siting approval, which requires public process, which is where projects die.

So the sequence for new capacity is: secure a site with grid access, sign a power agreement, wait. The waiting is the schedule. Everything else can be compressed with money; this cannot.

what it means for compute prices#

Two effects pulling in opposite directions.

Regional differentiation increases. Regions with available power and cooperative regulators get capacity. Regions without do not. That produces real price differences between cloud regions for the same instance type, larger than the historical spread.

Off-peak becomes genuinely cheaper. Grid economics are about peak demand. Workloads that can shift to off-peak hours are worth real money to operators, and that value will get passed through as pricing. Batch inference, training runs, and anything asynchronous is a candidate.

what to actually do#

Check regional pricing before you pick a region by habit. The default region in your organization was chosen years ago for reasons that may no longer hold. For a large workload the difference is material.

Make batch work time-flexible. If your nightly job can run in a four-hour window instead of at a fixed time, you can take spot capacity and off-peak pricing. This is a small engineering change with a large cost effect and almost nobody does it.

Measure your actual utilization. The cheapest watt is the one you do not use. A very large fraction of provisioned cloud compute runs at low utilization, and in an environment where power is the constraint, that waste is now expensive rather than merely inelegant.

Watch your provider's regional capacity announcements if you are planning anything large. Capacity comes online in steps tied to substation energization dates, and knowing the schedule is worth something.

the part that is not about your bill#

There is a legitimate public policy question here that the industry mostly does not want to engage with: whether the cost of connecting datacenters should be borne by households whose electricity bills are rising.

The industry's answer is usually that datacenters bring jobs and tax revenue, which is true and is a smaller number than the capital involved. The honest version is that the buildout is happening faster than the institutions that allocate its costs can deliberate, and the allocations being made now will be argued about for a decade.

Engineers do not decide this. Engineers do decide how much power their systems consume, and that has stopped being an abstract concern.