Counting Real AI Capacity
Counting AI infrastructure by deployable capacity rather than by announced megawatts. Deployment is paced by the slowest synchronized layer of the stack.
This report is our first full constraint map for AI infrastructure.
We have been tracking a constraint stack that now runs much deeper than accelerator allocation. The map in this report pulls those constraints into one framework and asks a simple question: which layers determine when announced capacity becomes billable compute?
Capacity has to be counted by synchronized deployability. A purchase order becomes revenue only when every layer arrives at the same site in the same window. That means the accelerator and memory. It also means the transformer, cooling loop, networking fabric, power equipment, EPC capacity, and crew that commissions the rack. Chip allocation set the pace earlier in the cycle. The limiting layer has since moved deeper into the physical and operational stack and a timeline slip in any one of these deeper chokepoints could slow down many other parts of the cycle.
That is why announced megawatts, GPU orders, and hyperscaler capex need to be read through a deployment lens. Those announcements are helpful from the view that they measure intent. The work we maintain a focus on is determining how much of that intent becomes real capacity, which layer slows the conversion, and which suppliers control the scarce inputs the rest of the stack depends on.
Semiconductors remain the heart of the system. Advanced packaging, HBM, and the substrate and validation layers around them remain the critical silicon constraints. The map adds what decides whether that silicon ever becomes billable: power and cooling, construction and permitting, networking and commissioning. A campus can hold its GPUs, racks, transformers, and substation and still produce no revenue, because the cooling loop has not passed first-fill or the only crew that can certify the rack is on another job.
Central to much analysis is the tracking of GW or ones ability to monetize each unit of power. This is why we point out that announced megawatts can be misleading. A project can be announced, land-secured, and sitting in an interconnection queue while still years from billable compute. Some of these slip. Others get resized, repriced, or pushed into a later vintage. Treating the full announced pipeline as near-term supply overstates capacity, and it understates the operators who locked up power and equipment early.
We define and track capacity differently. A real megawatt is power-secured, equipment-procured, commissioned, AI-ready, and billable. Scored that way, the 2027 and 2028 deployable pool looks smaller and more concentrated than the public pipeline implies. Much of that advantage was set by procurement decisions made back in 2024 and 2025, before most investors were watching the full stack.
AI infrastructure is a synchronized systems problem, and a GPU order is one gate in a longer chain. We track fourteen gates between a GPU order and billable compute. Most of them sit in the physical and operational layers, with GPU and ASIC allocation near the end of the line rather than the front. Ranked by deployment severity, the hardest gates now sit outside the chip.
The full report separates constraints that delay deployment from constraints that mainly raise cost. A transformer shortage holds revenue offline; a copper-foil price increase only raises the cost of a board. A substrate shortage can stop accelerator shipments, while an MLCC spike can be real pricing power without blocking a single megawatt. Read every tight component as a capacity constraint and you end up with the wrong operator ranking and the wrong supplier map.
We map the stack by role: constraint owners, constraint-exposed companies, scarcity arbitrageurs, and deployment-risk reducers. The main question this cycle is who can convert announced capacity into real capacity, and who controls the scarce inputs the rest of the stack depends on.
What paid subscribers get in the full report
The Real MW framework: how we discount announced capacity into power-secured, equipment-procured, AI-ready, and billable capacity.
The fourteen-gate deployment map: the full chain between a GPU order and revenue-generating compute.
A ranked Top 10 deployment-gating constraint table: including interconnection, transformers, turbines, switchgear, UPS, substations, advanced packaging, HBM, liquid cooling, commissioning labor, and permitting.
The paper MW to real MW funnel: why the announced pipeline shrinks materially as projects move toward revenue.
The deployment dependency chain: how semiconductor and physical infrastructure constraints clear on different timelines.
The power stack broken into four separate bottlenecks: generation, transmission/interconnection, equipment, and regulation/politics.
The below-accelerator constraint layer: PCBs, CCL, glass fabric, copper foil, PMIC/BCD capacity, probe cards, sockets, bonding/debonding tools, metrology, and cooling interfaces.
A deployment-gate vs. cost-inflation classification: which constraints actually delay capacity and which mainly raise cost.
The constraint ownership map: constraint owners, constraint-exposed companies, scarcity arbitrageurs, and deployment-risk reducers.
A framework for where constraints become pricing power: the bridge into our next report on bottleneck leverage across the AI supply chain.
The monitoring dashboard: what to track next across transformer lead times, turbine orders, switchgear and UPS availability, substrate LTAs, HBM tool backlogs, cooling interfaces, commissioning labor, prepayments, slot reservations, and price floors.
Coming next in Part 2: where constraints become pricing leverage
This constraint map sets up the next layer of work. Once we know where the bottlenecks sit, the follow-up question is which constrained layers can convert scarcity into price, margin, prepayments, reservation fees, long-term agreements, mix uplift, or lower discounting.
The next report will separate true scarcity rents from input-cost pass-through, mix-driven ASP uplift, and temporary restocking. A transformer shortage, an HBM shortage, an ABF substrate shortage, a cooling-validation bottleneck, and an MLCC price spike should not be treated the same. Each has a different mechanism, duration, and margin implication.
The first report maps where capacity slips. The next report bridges who has leverage and price accordingly due to their constraints.