September 2026 · 8 min read
AI capex: the $300B obligation off the books

Key definitions
Off-balance-sheet exposure An obligation kept out of the consolidated balance sheet, such as guarantees, special purpose vehicle debt and lease commitments. It lives in the notes and commitment tables, not in the ratios.
Residual value guarantee A promise to cover the shortfall if an asset such as a data center is worth less than an agreed floor at term end. Debt stays in the SPV; the risk commitment stays with the parent.
SPV (special purpose vehicle) A separate legal entity created to hold one asset. The SPV owns the data center, investors fund it, the user leases it back, and the borrowing sits on the SPV books rather than the user books.
The table buyers use to size a vendor commitment no longer holds the fastest-growing obligation. According to FT reporting, Big Tech has moved roughly $300 billion of AI infrastructure exposure off balance sheet through residual value guarantees and special purpose vehicles: Alphabet data center lease guarantees rose from $16.9 billion to $43.8 billion in six months, with under 2 percent on the books. Our judgment: this is not an accounting compliance story, it is a measurement story. When the fastest-growing obligation lives in the notes, anyone underwriting a vendor on balance-sheet ratios is deciding with a number that no longer covers the exposure.
1. The facts: guarantees and SPVs move the obligation out of the statements
Per FT reporting, with secondary sources noting they could not independently verify the figures, Alphabet data center lease guarantees climbed from $16.9 billion to $43.8 billion in six months, with under 2 percent entering the balance sheet. It is the cleanest case on record: the obligation multiplied while the number read by every ratio, screen and covenant test barely moved.
Meta shows the mechanism end to end. Per FT reporting, the roughly $50 billion Hyperion project in Louisiana is held through the Delaware SPV Beignet Investor, funded 80 percent by Blue Owl and 20 percent by Meta. About $28 billion of residual value guarantees back roughly $27 billion of Pimco, BlackRock and Apollo debt. The SPV owns the data center and Meta leases it back, so the borrowing stays on the SPV books while Meta carries guarantees and lease commitments. Sources: AI Weekly coverage of the FT report and FourWeekMBA structural breakdown.
It is not a single-company pattern. Meta, xAI, Oracle and CoreWeave are reported to have moved more than $120 billion of data center financing debt to investors through such vehicles, without a company-level split. Broadcom, Nvidia through the SoftBank and OpenAI development arrangement, Oracle and Amazon are said to use variants of the same structure. Source: Business Post follow-up.
Two citation rules matter here. First, the roughly $300 billion is company-level off-balance-sheet exposure from guarantees and SPVs, while the roughly $3 trillion figure widely quoted in the industry is an industry-wide commitment total; FT does not merge them, so they cannot be added or swapped. Second, these structures are legal under current accounting rules and are disclosed in notes and commitment tables. Reading this as fraud is a misreading. The accurate statement is that the disclosure location distorts the metric. The original FT investigation sits behind a paywall (FT original, HTTP 403 on our check, anti-bot and paywall).
2. Our judgment: the question is not whether the obligation exists, but where it lives
We read this as an ordinary pattern. Wherever a structural gap opens between self-reported scope and verifiable fact, wrong metrics grow in it. In the model safety layer, vendor-claimed boundaries and measured overreach are two faces of the same problem. In the capital layer, vendor-claimed commitment scale and actual obligation are two faces of the same problem. The regularity holds: the fastest-growing obligations are the least verifiable ones.
For buyers the implication is concrete. What you are underwriting in AI infrastructure is not a technology stack but a balance sheet that keeps adding leverage. Once compute, racks and power are locked in multi-year commitments, supplier credit and concentration become your operating risk, and that risk has been moved into the notes.
Our call: moving AI vendor diligence from statement ratios to an obligation ledger is the cheapest upgrade available in enterprise AI procurement this year. It needs no new tooling, only a few lines in the review checklist.
3. The one decision this changes for each buyer
C-suite (strategy, ROI, governance)
Build, host or commit: the input moves from price per unit of compute to the deliverability of the vendor commitment. When obligations grow off statement, supplier credit and concentration must be assessed independently of the vendor price model.
Digital transformation lead (integration, scale, readiness)
Migration and hosting assumptions: lock-in period, leaseback terms and exit cost set the reversibility ceiling of your architecture. Betting on a multi-year vehicle means handing reversibility to someone else financing structure.
AI app lead (engineering, deployment, cost)
Sourcing and degradation paths: the financing structure of second-tier suppliers such as neoclouds and token-as-a-service providers determines how long they survive pressure. Multi-source is availability design, not preference.
AI compliance lead (policy, audit, explainability)
Disclosure location and audit trail: if an obligation only appears in notes and commitment tables, internal risk reporting has to cite it explicitly, or the risk framework fails exactly at the structural gap.
4. From ratios to an obligation ledger
Six items go straight into a vendor review checklist. All come from disclosures and contract text you can request today:
1. Guarantee and SPV detail
Amount, maturity, triggers and recourse. Guarantees typically grow far faster than the commitment figures on the statements.
2. Residual value guarantee size
The most commonly skipped line: it leaves asset value downside with the user while staying out of the user ratios.
3. Lease and leaseback terms
Lock-in period, repricing mechanism and early termination cost set the ceiling on how reversible your architecture can be.
4. Compute and power concentration
Single site, single grid, single rack vendor concentration is a more practical availability problem than multi-cloud branding.
5. Second-tier supplier financing
The debt structure of neoclouds and token-as-a-service providers determines survival time in a price war or a credit squeeze.
6. Reconcile the ledger quarterly
Align the last ledger against new disclosures each quarter and track the rate of change, not the absolute figure.
5. Conclusion and this month action
Our judgment: the real scale of AI infrastructure commitments is not on the statements, so vendor assessment built on statements has systematically understated how fast obligations grow. Buyers do not need more data. They need the right input location, which means pulling notes and commitment tables into the assessment.
The smallest useful move this month: at your next AI vendor review, make unfunded and off-statement obligations a standing agenda item, ask for guarantee and SPV detail, and put the request in the minutes. Then answer one question: if the obligation ledger holds a guarantee you have never seen, what exactly was your risk assessment built on?
OOMeta AI
OOMeta splits vendor assessment into two verifiable layers: how replaceable the stack is, and how deliverable the commitment structure is. Commitment scale that exists only in vendor materials is not an input we accept; ledgers, terms and exit cost are.
Book a diagnostic sessionReferences: FT investigation (original, paywalled, HTTP 403 on our check): ft.com/content/7f11afae-c4e3-4054-a65b-873f3647f563 | AI Weekly coverage (Alphabet $16.9B to $43.8B, Meta Hyperion and Beignet, $28B residual value guarantee): aiweekly.co alert | FourWeekMBA breakdown ($300B versus $3T scope split, $120B-plus of SPV debt): fourweekmba.com breakdown | Business Post follow-up: businesspost.ie report. All specific figures are attributed to FT reporting; the secondary sources state they could not independently verify them. This article does not merge the $300B off-balance-sheet exposure with the $3T industry commitment total.
Frequently asked questions
Is moving AI infrastructure exposure off balance sheet illegal?+
No. According to FT reporting, these guarantee and SPV structures are legal under current accounting rules and are disclosed by the companies in notes and commitment tables. The issue is not whether the structure exists but which table it sits on.
Are the roughly $300 billion and the $3 trillion figure the same number?+
No. The roughly $300 billion is company-level off-balance-sheet exposure from guarantees and SPVs. The roughly $3 trillion is an industry-wide commitment total. FT does not merge the two, and the secondary sources say the same, so they cannot be added or swapped.
What are Alphabet numbers?+
Per FT reporting, Alphabet data center lease guarantees rose from $16.9 billion to $43.8 billion in six months, with under 2 percent landing on the balance sheet. The obligation grew several times over while the number feeding ratios barely moved.
How does the Meta structure work?+
Per FT reporting, the roughly $50 billion Hyperion project in Louisiana is held through the Delaware SPV Beignet Investor, with Blue Owl at 80 percent and Meta at 20 percent. About $28 billion of residual value guarantees back roughly $27 billion of Pimco, BlackRock and Apollo debt, and Meta leases the data center back.
Why does this matter to a company buying AI infrastructure?+
When you choose between building, hosting and cloud commitments, you are underwriting supplier credit and concentration. If the fastest-growing obligations are not on the statements, the scale, lock-in period and exit cost of a vendor commitment cannot be read from public metrics.
What should be added to a diligence checklist?+
Replace ratios with an obligation ledger: guarantee and SPV details with amounts, maturities and triggers, residual value guarantee size, lease and leaseback terms, compute and power concentration, plus the financing structure of second-tier suppliers.
Related articles
Inference outspends training. Buy switching power
Gartner: 2026 inference spend ($23.3B) beats training ($19B); agentic costs more than 5x by 2028. Our judgment: the unit is configuration and placement, and switching power is the asset worth buying.
AI cost’s upstream is memory, not model pricing
TrendForce: Q2 2026 DRAM revenue rose 59.5 percent QoQ to $154.7B while supply keeps lagging demand. Our judgment: what sets 2027 unit cost is the silicon supply cycle, not the model price list.
Model buying is two markets: volume vs money
Vercel production index: open-weight models run 56 percent of tokens on 14 percent of spend. Our judgment: average token price is the wrong metric; the buying unit is the model tier per task.
Buy runtime evidence, not control planes
Once control planes commoditize, vendor evals remain in-stack self-report. Our judgment: what stays scarce is runtime evidence verifiable across stacks, which is the same diligence logic applied to vendors.