52/100

Moderate evidence

ProblemPublished recordBusinessProblem Space

Financing the AI Buildout

Truvace record
TRV-2026-2479raw data (JSON)
Version
v1Published
First published
Evidence type
Observational studyPreprint, not yet peer reviewed
Sources
1 sourcePeer-reviewed
sha256
9d77c0476533…check it

Artificial intelligence is driving a large expansion in data center capacity, power infrastructure, and specialized computing equipment. We estimate that a 1 GW AI campus costs about $41 billion. A 188 GW U.S. buildout completed by 2032 would require total investment of nearly$9 trillion and amount to annual investment of 3.2 percent of GDP over 2025–2032. As hyperscaler capital expenditures outgrow internal cash flow, financing is shifting toward leases, joint ventures, project debt, private credit, securitizat…

The problem

A working paper estimates a 188 GW US AI buildout by 2032 would cost nearly $9 trillion, and that leases, project debt and special-purpose vehicles raise asset-level leverage while hiding obligations from hyperscaler balance sheets.

What this doesn’t fix

The 188 GW figure is a scenario rather than a forecast, sensitive to large multiphase projects and projects without reported completion dates, and the author says it is premature to conclude AI infrastructure poses systemic risk.

Sources

1 on file
  1. NBER Working Paperdoi:10.3386/w35865
    Peer-reviewed2026-10-01

Cite this record

v1

Truvace Impact Record TRV-2026-2479, v1: “Financing the AI Buildout.” Truvace, 2026-11-12. /record/TRV-2026-2479 (accessed on the day you copy it). sha256 9d77c04765333611…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv19d77c0476533…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2479 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.