Datacenters & Digital Infrastructure — Frontier

The picks-and-shovels of the AI buildout. The founding thesis was: compute is bottlenecked by power, power is bottlenecked by grid + equipment, and the whole stack gets financed through capex no generalist is modelling end-to-end. The 2026-07-22 compile made the first clause plural; the 2026-07-23 compile put a quantified backbone under the third — capex now has primary Q2 prints, and the master unit (capex/MW), the queue, the rack, and the packaging gap all have numbers.

Evidence quality — read this first

Eighteen sources, zero papers — but now five company filings. The 2026-07-23 compile added the topic's first primary filings: three Q2 2026 8-Ks (GOOGL, TSLA, TXN) and CoreWeave's Q1 2026 IR release, joining the Fed MPR and NVIDIA (7 technical-reports, 11 analysis). Practical consequence:

• The strongest evidence is now the Q2 capex/FCF prints (first-party 8-Ks) and the Fed MPR + ConstructConnect macro pair — strong to moderate.
• Several claims remain weak: CoWoS capacity (TrendForce, secondary — no TSMC filing), capex/MW (single-operator Crusoe pricing, as-of ~Apr 2025), Tesla's Cortex-specific detail (500 MW / Megapacks — blog-sourced; the print governs on conflict).
• The GB300 kW/rack figure (135 kW) is vendor-primary — authoritative for the spec, not independent.
• 2026 capex aggregates remain forecasts (no summed actual until the year closes) — but the quarterly Q2 prints for GOOGL/TSLA/TXN are actuals.

Active Frontiers (compiled 2026-07-23)

1. The constraint went plural — and is now quantified

Status: Rapid change · Key sources: Carbon Direct, Lenovo GB300, TrendForce, TSMC Q2, Samsung · Key concepts: Power · Advanced Packaging · Rack Power Density

Packaging, memory and power bind simultaneously — capital is the only abundant input. This compile put numbers on each: the grid queue is 3–4 years in DC load zones (>300 GW across ~1,500 projects), and the binding constraint there is queue throughput/deliverability, not raw MW (the queue holds enough "on paper" through 2030). CoWoS's gap narrows 20% → ~10% by end-2026 but does not close — packaging stays binding through year-end even as industry capacity quadruples toward ~200K wafers/mo. And the rack is 135 kW (GB300 NVL72, ~90% liquid), the physical unit everything upstream and downstream is denominated against. Power still has the strongest evidence base; what's new is that all three constraints now have sourced magnitudes rather than a qualitative "sold out."

Open problems: sequencing (which binds first, for whom); who holds the booked CoWoS queue; HBM allocation by supplier; whether behind-the-meter genuinely relieves the queue or just skips it for the well-capitalised.

2. The demand side has stopped self-funding

Status: Rapid change · Key sources: GOOGL Q2, TSLA Q2, TXN Q2, Futurum, Value Add VC · Key concept: Hyperscaler Capex Cycle

The first primary Q2 prints answer this page's central financing question for two buyers. Alphabet's Q2 capex ($44.9B, calendar-Q2 cash PP&E) outran operating cash flow ($39.1B) → free cash flow negative $(5.9)B, plugged from capital markets ($49.6B equity + $20.3B notes; LT debt doubled to $98.2B). Tesla did the same ($5.79B capex > $4.7B OCF → FCF $(1.1)B) but self-funded from a $1.2B cash drawdown. TXN is the supply-side mirror — a seller into the buildout whose own capex is falling as its fab wave crests, sending FCF +271%. The seam: buyers' funding gaps widen while the equipped, subsidised supplier harvests the cash. The aggregate is still a contested band ($610–725B, the whole gap being Microsoft's ~$70B), but two names now print actual quarterly capex — and both exceed internal cash generation. Alphabet's FY capex dollar guide and RPO are absent from the 8-K (call/10-Q items) — unresolved by the print, not invented.

Open problems: whether Amazon/Microsoft/Meta show the same signature when they print (late Jul); how long negative FCF can run before it constrains the buildout; resolving Microsoft's ~$70B aggregate discrepancy with a primary source.

3. Who pays the rent — backlog, now with a double-counting edge

Status: Rapid change · Key sources: CoreWeave Q1, Futurum, GOOGL Q2 · Key concept: Contracted Backlog & RPO · Key entities: CoreWeave · Oracle

The KB now holds a backlog figure at the neocloud layer: CoreWeave's $99.4B (Q1 2026), beside Oracle's $523B RPO and Alphabet's ~$462B cloud backlog. And it holds, for the first time, both ends of one double-counting edge: CoreWeave names a $21B Meta commitment inside its $99.4B backlog — and Meta is itself a tracked hyperscaler. The same end-demand books at two layers; the magnitude of overlap across the hyperscaler → neocloud → model-builder stack is not yet quantified by any source. The disclosure is thin at every layer — no duration, cancellability or customer concentration for any of these figures, including the CoreWeave primary. Alphabet's Q2 8-K carries no RPO line, so the $240B-vs-$462B conflict stays open.

Open problems: duration and counterparty quality of the $523B RPO and $99.4B CoreWeave backlog; the size of inter-layer double counts; reconciling Alphabet's $240B → ~$462B.

4. The buildout is a macro variable

Status: Steady · Key sources: Fed MPR July 2026, ConstructConnect · Key concept: Data-Center Construction as a Macro Variable

The best-evidenced thread. The Fed reports business fixed investment at +11% annualized in Q1 2026 vs 5.5% in 2025, attributing most of the strength to AI infrastructure; ConstructConnect independently measures data centers at >20% of all US nonresidential building starts and YTD spending of $58.1B, >4x the 2025 record pace. The buildout subtracts ~0.4pp from GDP via AI-related imports, and the productivity payoff has not arrived. As of mid-2026 the AI economy's macro footprint is the construction of capacity, not its use — the "who pays the rent" question restated in national accounts. The negative-FCF prints (Frontier 2) are the corporate-finance version of the same tension.

Open problems: sizing the GDP downside of a capex air-pocket; why five states capture ~60% of starts; when the productivity channel becomes visible.

5. A fourth ownership category — vertically-integrated compute (now printed in MW)

Status: Early stage · Key sources: TSLA Q2, Tesla Cortex 2 · Key concept: Vertically Integrated Compute · Key entity: Tesla

Beyond hyperscaler / neocloud / colo sits the first-party builder. Tesla's Q2 8-K makes its compute figures first-party and switches the unit to MW: Cortex 1 >90 MW, Cortex 2 >115 MW (both Production), >205 MW combined onsite ("more than doubled" in H1) — so the blog's 500 MW is a full-buildout envelope, not the printed figure. Cortex pairs GPU clusters with on-site Megapack storage, the live test of "who owns the power" — and Carbon Direct now supplies the why: on-site generation is attractive because it skips the 3–4-year grid queue. Tesla is also integrating deeper (an in-house Austin fab for its own logic/memory chips). xAI's Colossus 2 (500,000+ GPUs) may belong to this category but is still unclassified.

Open problems: grid-vs-behind-meter split at Cortex; Cortex-specific capex per MW; replicability without an in-house storage business.

6. The supply-chain re-rate — the rack finally has a number

Status: Steady · Key sources: Lenovo GB300, NVIDIA/DOE · Key concept: Rack Power Density · Key entity: Vertiv

GB300 NVL72 rack-scale density pushes air cooling toward liquid, re-rating the vendors NVIDIA names (Vertiv, Eaton, GE Vernova, Schneider, Tesla, Trane) and lifting the ~$85B networking/cooling capex slice. The topic's oldest gap is closed: the rack is 135 kW TDP / ~155 kW peak with a ~90% liquid / ~10% air split (Lenovo vendor spec, corroborated by HPE at 132–140 kW) — roughly 18–19× a legacy ~7 kW rack, and ~7.4 racks/MW, the sourced mechanism behind "liquid cooling becomes mandatory." NVL72 deployment is also supply-gated by CoWoS.

Open problems: GB200-vs-GB300 delta and sustained-vs-peak draw; whether supply-limited racks push operators toward even higher density per delivered rack.

Recent Developments

All 18 sources are now compiled into concept/entity pages (staleSources 0).

The tradable debates

1. Which constraint binds first — power, packaging, or memory? All three now have sourced magnitudes (queue 3–4 yr; CoWoS gap 20%→10%; rack 135 kW) but the sequencing for a given project is still unresolved.
2. Do neoclouds earn their cost of capital, or is it a depreciation mirage? CoreWeave is the test case — now with numbers on one side ($2.08B rev vs $7.70B capex, $(740)M net loss) but the answer hinges on the still-undisclosed GPU depreciation schedule.
3. Does liquid cooling become mandatory (Vertiv-et-al a secular winner) or stay niche? Sharpened: at 135 kW/rack with a 90/10 liquid split, mandatory is now the sourced default at NVL72 scale.
4. Will hyperscaler capex inflect down, and what is the leading indicator? The nearest tell just printed: Alphabet's Q2 FCF went negative while capex kept rising — the buildout is now balance-sheet-financed, so the leading indicator may be financing capacity, not demand.
5. Who owns the power? Utilities, IPPs, or buyers building behind the meter. Tesla Cortex (now >205 MW, MW-disclosed) is the live case; the queue's 3–4-yr wait is the reason behind-the-meter pays.
6. Is the backlog real — and is it double-counted? Advanced 2026-07-23: the KB now holds one concrete double-counting edge (Meta $21B ⊂ CoreWeave $99.4B), but duration/concentration are absent at every layer.

Knowledge Gaps

Areas where the KB needs more sources. These feed the next discovery cycle. The 2026-07-23 compile CLOSED six gaps (see "Filled" below) and opened/sharpened several others.

Still open (highest priority first)

• Backlog duration, cancellability and customer concentration for Oracle RPO ($523B), Google Cloud backlog (~$462B), Microsoft's unfulfilled Azure backlog, and CoreWeave's $99.4B — the most decision-relevant unknown in the topic, and still undisclosed even in the CoreWeave primary — suggested search: "Oracle remaining performance obligations duration disclosure 10-Q"
• Amazon, Microsoft and Meta Q2 2026 capex/FCF — do the other three big-four buyers show the same "stopped self-funding" signature GOOGL and TSLA printed? They report late July — suggested search: "Amazon Microsoft Meta Q2 2026 capital expenditures free cash flow 10-Q"
• The magnitude of backlog double-counting — the KB now holds one edge (Meta's $21B inside CoreWeave's $99.4B while Meta is a tracked hyperscaler) but no source quantifies the overlap across the hyperscaler → neocloud → model-builder stack, nor nets out capacity hyperscalers rent from neoclouds — suggested search: "AI cloud contract backlog double counting neocloud reseller GPU commitment"
• Microsoft 2026 capex, from a primary source — resolves the ~$70B conflict driving the aggregate dispersion; MSFT prints ~2026-07-29 — suggested search: "Microsoft FY2026 capital expenditures 10-Q quarterly report"
• Alphabet FY2026 capex dollar guide + RPO/cloud backlog — the Q2 8-K is compiled but both are call/10-Q items absent from the exhibit; needed to resolve the guide (watched $180–190B) and the $240B-vs-$462B backlog conflict — suggested search: "Alphabet Q2 2026 earnings call capex guidance remaining performance obligations"
• CoreWeave GPU depreciation schedule + customer concentration — the Q1 primary gives revenue/backlog/capex but not the depreciation life or the Microsoft/OpenAI share — the two inputs debate #2 turns on; Q2 2026 prints mid-Aug — suggested search: "CoreWeave 10-Q GPU useful life depreciation customer concentration 10-K"
• HBM bit supply, capacity and allocation by vendor — the KB has the price signal (Samsung's margin) and zero volume data — suggested search: "HBM3E HBM4 supply capacity allocation SK Hynix Samsung Micron 2026"
• SK Hynix — the largest HBM supplier has no source in this KB at all; reports 2026-07-29 — suggested search: "SK Hynix Q2 2026 results HBM capacity"
• A primary TSMC source on CoWoS — capacity trajectory is now sourced (TrendForce, secondary) but the sellout + wafer numbers want a TSMC filing/transcript — suggested search: "TSMC Q2 2026 earnings call transcript CoWoS advanced packaging capacity"
• US deliverable power-capacity shortfall (today vs 2028) — Carbon Direct says the queue holds "enough on paper through 2030," but the deliverable shortfall path is still unquantified — suggested search: "US data center power capacity shortfall gigawatts 2028 deliverable forecast"
• xAI Colossus 2 ownership classification — 500,000+ GPUs, uncategorised between neocloud and first-party — suggested search: "xAI Colossus 2 Memphis ownership power supply financing"
• GB200-vs-GB300 rack-power delta + sustained-vs-peak draw — the 135 kW figure is GB300-specific and vendor-primary; an NVIDIA/independent-lab number on sustained draw and the GB200 delta would deepen it — suggested search: "NVIDIA GB200 NVL72 rack power sustained draw datasheet"

Filled at the 2026-07-23 compile (now in the wiki)

• ✅ kW/rack for GB300 NVL72 — the topic's oldest gap, closed: 135 kW TDP / ~155 kW peak, ~90% liquid (Lenovo GB300) → rack-power-density. Vendor-primary.
• ✅ Grid-interconnect queue wait times — closed: 3–4 yr waits, >300 GW combined PJM+ERCOT queue, constraint is throughput not raw MW (Carbon Direct) → power-the-binding-constraint.
• ✅ Capex per MW — closed (analysis-tier): ~$59M/MW all-in, ~half IT (NextBigFuture/Crusoe) → capex.md. Single-operator, as-of ~Apr 2025.
• ✅ CoWoS wafers/month capacity & end-2026 gap — closed (secondary): ~120–140K TSMC + 50–60K OSAT; gap 20%→~10% (TrendForce) → advanced-packaging-bottleneck. TSMC-primary still wanted (kept open).
• ✅ Neocloud financials (CoreWeave) — closed with the first neocloud primary (CoreWeave Q1): rev $2.08B, $99.4B backlog, capex $7.70B, net loss $(740)M → CoreWeave dossier. Depreciation + concentration kept open.
• ✅ Q2 2026 buyer prints (GOOGL, TSLA) + supply-side (TXN) — closed: the demand side has stopped self-funding (capex > OCF → negative FCF) (GOOGL, TSLA, TXN) → hyperscaler-capex-cycle. Alphabet FY guide + RPO absent from the exhibit (kept open).

Still to compile

Entities: Microsoft (blocked on the capex conflict; prints ~Jul 29) · Amazon · Meta (Q2 prints late Jul) · Nebius (NBIS) · Crusoe · Lambda · Eaton (ETN) · nVent (NVT) · Schneider Electric · Super Micro (SMCI) · Dell · Equinix (EQIX) · Digital Realty (DLR) · Vistra (VST) · Constellation (CEG) · Talen (TLN) · GE Vernova (GEV) · SK Hynix · Micron · NVIDIA · xAI

Concepts: Power Usage Effectiveness (PUE) · Direct-to-chip vs air cooling · Grid interconnection queue (could graduate from a sub-section of power-the-binding-constraint to its own concept) · Capex per MW (currently in commercial/capex.md + benchmarks — could graduate to its own concept) · Power Purchase Agreements and behind-the-meter generation · The neocloud business model (GPU depreciation, contract duration, customer concentration — seeded via the CoreWeave dossier)

Tracking tier

Datacenters remains a tracking beat (frontier monitoring + fast-takes + entity pages), not yet in the daily /dispatch rotation. The 2026-07-23 compile is the first to add primary company filings (five: GOOGL/TSLA/TXN Q2, CoreWeave Q1) and to quantify the constraint stack end-to-end. Evidence quality genuinely improved this compile — the earlier "analysis-only" characterization no longer holds for the capex/FCF/backlog spine, though CoWoS and HBM volume data remain secondary. The first dossier target (CoreWeave) is now seeded with a Q1 primary; the deep-dive proper awaits the 10-Q (depreciation + concentration) and the mid-Aug Q2 print.