The Definitive Guide toAI Data Centers
Ask the GuideAboutAccount

Chapter 16.5

In this chapter · 6 sections
Term help
Terms in this chapter (52)

Scenarios for 2030

Supercycle, digestion or bubble; mega-campus or distributed inference; firm clean power on time or late. Your 2026 commitments are bets on which 2030 arrives, and a wrong bet is priced in stranded silicon, substations and balance sheets.

ThreadsPower-boundGoodputDensity ramp

What you'll decide here

  1. Which demand scenario you underwrite: supercycle, digestion or bubble. It sets your contracted-versus-merchant mix, debt capacity and optionality spend.
  2. A centralized gigawatt training campus or a distributed inference fleet: remote and power-first, or metro and latency-first, and whether it survives inference-dominant compute.
  3. Which industry structure to position for: neocloud, hyperscaler, or sovereign/enterprise, and so whose cost of capital, utilization risk and obsolescence exposure you inherit.
  4. Which power endgame you bet time-to-megawatt on: firm CFE or existing nuclear now, SMR or fusion from 2030, or gas and grid as the bridge.
  5. Which downside you survive: demand air-pocket, power slip, efficiency shock or density step that strands racks, alone or combined, and whether your flexibility hedges it.

Every chapter before this one decides something about a building you can draw. This one decides which world the building lives in. The same 200 MW campus is a brilliant asset in one 2030 and a stranded liability in another, depending on which of a few distinct futures arrives. The scenario is the largest uncontrolled variable in any AI-infrastructure thesis, and it usually enters as an unexamined assumption.

Three axes frame 2030, and they move semi-independently. The demand-and-capital regime is supercycle, digestion or bubble. Chapter 1.8 covers firm-level economics; here the regime is the sector-wide lens. The architectural shape is centralized mega-campus versus distributed inference, which decides where the megawatts go. The industry structure and geographic re-map decides who owns the capacity and where it lands. The chapter then turns to the power-supply endgame (CFE, SMR, fusion, and the demand-side wildcards that could invalidate the whole demand curve) and to the stranded-asset and systemic risk each scenario hides.

The three scenarios: supercycle, digestion, bubble

Start with the demand-and-capital regime, because it sets the boundary conditions for everything else. The three scenarios are not moods of optimism or pessimism. They are different beliefs about one mechanism: does AI revenue grow fast enough to service the capital being deployed before the assets depreciate? McKinsey's own framing spans a $3.7T-to-$7.9T range of AI-capable capex to 2030 against a ~$5.2T midline, wide enough that the constrained and accelerated cases describe different industries (McKinsey, 2025). Bain's September 2026 report has the buildout costing $5–6.5T and bringing about 150 GW or more online by 2030. In Bain's view power, chips, skilled labor and permitting all hold it back at the same time. In Q1 2026 alone, local opposition blocked or delayed at least 75 projects worth $130B, by Bain's count (29 September 2026). The two houses measure different scopes, so their ranges sit side by side and do not form one series.

Supercycle is the case where demand keeps outrunning supply. Reasoning and agentic workloads inflate tokens per task, inference compute compounds, and power, not chips or capital, stays the limit through 2030. The scarce asset is an energized megawatt, time-to-power outranks every other lever, and the operators who locked firm power and long-lead gear early win. Digestion is the soft-landing case. The extraordinary base is absorbed and capex growth decelerates sharply after 2026 without a crash. That makes 2026 the peak it falls from: the top four US hyperscalers' capex guidance for the year is up more than 60% over 2025 (→ Chapter 16.4). The operators who win are the disciplined ones that held back at the top of the cycle. Bubble is the case where the revenue gap wins. Spend behaves like a utility build-out while revenue still behaves like software subscriptions, and the mismatch forces write-downs, cancelled announcements and a depreciation reckoning.

Three estimates size the revenue the capex needs, or the shortfall against it, on different bases and horizons. David Cahn’s July 8, 2026 heuristic puts lifetime end-customer revenue at ~$1.5T for one annual capex cohort. Bain sized a ~$800B annual shortfall by 2030 even after AI-driven savings (Bain, 2025). Its September 2026 model, on a different horizon, puts the new revenue still needed in 2031 at ~$4.2T a year to reach a ~$6T annual AI market.

Nobody knows which scenario will arrive, so the decision is which one your balance sheet is structured to survive. A supercycle bet is contracted, levered and over-built on power. A bubble hedge is merchant-light, opex-flexible and short on irreversible commitments. You cannot be optimized for both, and pretending otherwise is how operators get caught.

The three 2030 scenarios: structural signatures and what survives
ScenarioCore mechanismBinding constraintCapex trajectory to 2030What winsWhat strands
SupercycleAI revenue compounds with reasoning and agentic demand; tokens per task explodePower and long-lead equipment (chips and capital ample)Sustained ~20%+ CAGR; midline-to-accelerated ($5-8T)Early firm-power lockers; time-to-megawatt leaders; contracted and leveredLatecomers stuck in the queue; under-provisioned cooling and power
DigestionExtraordinary base absorbed; growth decelerates without a crashUtilization and unit economics; filling what was builtSharp deceleration after the 2026 peak; flat-to-modestDisciplined operators that held back at the cycle top; high-utilization fleetsSpeculative greenfield; over-levered merchant capacity
BubbleRevenue gap wins; spend behaves like a utility, revenue like SaaSMonetization; willingness to pay per query, seat or API callSharp cuts; cancelled announcements; write-down waveOpex-flexible, merchant-light hedgers; those who kept optionality cheapLong-lived debt on short-lived silicon; under-depreciated fleets; idle substations
A decision lens, not a forecast. Probabilities are deliberately omitted: the point is which posture survives each world, not how likely each is. Capex and gap figures are 2025-2026 vintage and contested (McKinsey, Bain, Sequoia/Dell'Oro).

Centralized mega-campus vs distributed inference

The second axis is architectural, and it is orthogonal to the demand regime. Even a supercycle spans a workload continuum that pulls siting and design in different directions. A centralized mega-campus is the gigawatt-scale training factory: one tightly coupled supercomputer chasing the cheapest firm power and the coldest climate, indifferent to user proximity (→ Chapter 16.1). Inference splits by workload. Frontier, model-parallel and batch inference fit the same dense liquid-cooled campus as training. Latency- or residency-bound inference fits regional sites, and strict-locality inference fits edge or on-premises capacity.

The inference transition makes this fork decisive. Bain forecasts that by the end of the decade the majority of AI compute is inference, not training, even as frontier training concentrates into 1 GW-plus campuses that become standard (Bain, 2025). The crossover is not distant: Deloitte's November 2025 outlook already forecasts inference at about two-thirds of 2026 AI compute (Chapter 1.3). If you build only for centralized training, you cannot serve every latency or residency need. If you build only a small distributed fleet, you cannot host frontier training or model-parallel inference. Density, redundancy, fabric blocking and siting driver all vary across the continuum, so this is a fork to decide at scoping, not a dial to tune later. Reasoning and test-time compute raise the decode-heavy share but do not by themselves decide whether serving is centralized or distributed (→ Chapter 16.3).

Industry structure and the geographic re-map

Cascade: 2030s; wider X-energy ambition: 2039forecast
Amazon Cascade and wider X-energy targets, separately dated
an announced reactor program cannot release a phase that needs contracted power
Scope & caveats

Distinct project and program targets. Neither is the Google–Kairos 2030/2035 sequence or a firm delivery date.

Who owns the 2030 capacity is a third axis. Three operator archetypes are consolidating, each with a different cost of capital and obsolescence exposure. Hyperscalers self-fund the largest share from cash flow and carry the depreciation debate on their own books. The top four US hyperscalers have guided to roughly $735–760B of capex in 2026 (company guidance through the Q2 2026 prints). Amazon raised its guide to ~$220B on 2026-07-30, with CEO Jassy naming higher memory cost, not more megawatts, as a driver. The Oracle-inclusive top-five cluster is tracked at ~$750B+ (CreditSights). Neoclouds are the pure-play GPU landlords: capital-intensive, debt-financed and margin-pressured, and the most exposed to a utilization or residual-value shock because their entire asset is depreciating silicon. Sovereign and enterprise buyers are the fastest-broadening demand source and the one least governed by pure unit economics. They include nation-states pursuing compute independence and regulated industries pursuing data residency. SK Telecom's planned up-to-2 GW Vera Rubin DSX cloud in Korea (letters of intent with NVIDIA, July 2026; first AI factory targeted for 2027) is the APAC instance.

A fourth archetype is emerging in 2026: the energy/launch integrator selling time-to-megawatt. SemiAnalysis reads SpaceX's earnings-call plans as a path to ~10 GW of ground compute by year-end 2027, with Microsoft the logical largest offtaker. That structure is neither hyperscaler nor neocloud. Apply the announced-vs-under-construction test to every such figure before you underwrite it as energized.

The geographic re-map follows firm power and permissive policy. Power-first training campuses migrate to stranded-generation and cold-climate regions, while latency-first inference clusters stay in the metros (→ grid integration in Chapter 15.8). Sovereign demand and export controls redraw the map again: the (later rescinded) US AI-diffusion tiering, and Gulf-state build-outs converting energy wealth into compute. A review of 775 non-US data-center projects found US companies operate about 48% of them by investment value, so residency is not control: a local site does not guarantee sovereignty when a foreign operator runs it (arXiv 2508.00932, 2025). For a 2026 siting decision, the cheapest-power, fastest-permit jurisdiction may carry a geopolitical or export-control tail risk that a spreadsheet does not price. That tail is no longer hypothetical. In March 2026 drone strikes damaged AWS facilities in the UAE and Bahrain, and in September AWS said its Bahrain region cannot be restored (Chapter 11.2). Price physical-security and regional-concentration risk into Gulf and other contested-region capacity, and spread critical workloads across regions, not only availability zones.

Operator structures on fixed axes
AxisHyperscalerNeocloudSovereign / enterprise
Revenue protectionExternal and internal demand; know which cash flow pays for the capacityTenant acceptance, credit support and termination termsMission funding and approved operating budget
Funding sourceAvailable corporate cash plus committed debt and leasesEquity, drawable debt and customer supportBudget, procurement approvals and contracted funding
Hardware riskQualification, supply allocation and competing internal demandSupplier concentration, refinancing and resale routeSupportability, access restrictions and control of stack
Exit / reuseAlternative workloads must still pass service and cost testsDisposition or replacement contracts must be executableMission continuity and data/operational control must survive transition
Archetypes do not imply a universal cost of capital, utilization threshold or survival ranking.

The power-supply endgame

Every 2030 scenario eventually hits the same wall: where do the firm, clean megawatts come from, and when? The IEA projects global data-center electricity demand to roughly double from ~485 TWh in 2025 to ~950 TWh by 2030 (~3% of global electricity), with AI-specific load tripling (IEA, 2026). In the US, EPRI's scenarios move data centers from ~4-5% of electricity today toward 9-17% by 2030; LBNL's June 2026 update (192 TWh in 2024, a 649 TWh reference case for 2030) is in Chapter 16.1. The endgame is a ranking of supply options by the variable that actually gates a build: time-to-megawatt, not headline LCOE.

Ranked that way, the clean-and-firm options that look best on a carbon spreadsheet are the slowest to energize. Firm, clean supply available now includes operating nuclear, hydro and geothermal, where resource geography and uncontracted capacity permit. Restarts are project-specific future supply: Constellation targets a 2027 restart of the 835 MW Crane Clean Energy Center, which serves Microsoft. SMRs are real but late. Google–Kairos targets first deployment in 2030 and a fleet by 2035 (Kairos Power, 14 October 2024). Amazon’s Cascade targets operations in the 2030s and the wider X-energy ambition runs to 2039 (Amazon, 16 October 2025). The 2030 dates are widely judged optimistic.

Power-reactor construction permits have started to land. In March 2026 the NRC voted to award TerraPower a construction permit for its Natrium sodium-cooled fast reactor at Kemmerer, Wyoming, which TerraPower expects to complete in 2030 (TerraPower, 4 March 2026). The NRC issued TVA a construction permit for the Clinch River BWRX-300, a light-water SMR, on 28 September 2026, at the end of a 14-month review. TVA has not set a construction start and is still negotiating cost sharing. A construction permit is not an operating licence, and it is not delivered power.

Fusion is an option, not a plan. SPARC is the demonstration machine and ARC the generating plant, and Commonwealth Fusion targets grid electricity from its first ARC plant in Virginia in the early 2030s (CFS, Aug 2026). No one should underwrite a 2030 build on a fusion megawatt. That leaves gas-and-grid as the default bridge that carries the load this decade. It combines behind-the-meter generation (Cleanview tracks ~90 GW announced at 59 US data centers by mid-2026, largely gas turbines and engines, with about 2 GW operating and roughly 1 GW under construction) and host-utility grid service (project-specific tariff, studies, upgrades, agreements and milestones). Fuel emissions stay in the inventory: CFE procurement and any separate offset claim do not erase the gas combustion. → speed-to-power mechanics in Chapter 3.2.

Power-supply endgame, ranked by time-to-megawatt, not LCOE
Supply optionRealistic availabilityFirm?Clean?Role in a 2030 buildKey risk
Operating nuclearNow, if uncontracted capacity and transmission are availableYesYesAnchor firm-clean load; scarce and largely contractedFinite fleet; megadeals already taken
Grid interconnection (new)A specific utility’s signed service and upgrade milestonesYes (grid)Grid mixThe default firm supply; the queue is the real gateQueue length; substation-transformer lead times above 160 weeks in 2026 (Wood Mackenzie)
Behind-the-meter gasA specific turbine, permit, fuel and commissioning pathYesNoThe bridge that actually carries the decadeCarbon exposure; Cleanview: ~90 GW announced, ~2 GW operating mid-2026
SMRGoogle–Kairos targets 2030 and 2035; Amazon Cascade targets the 2030s; TVA holds a Sep 2026 construction permit for a Clinch River BWRX-300, with no build start setYesYesA 2030+ option; do not underwrite a build on it yetLicensing/NRC timeline; first-of-a-kind cost
Fusion2030s+ (uncertain)YesYesPure option value: a hedge, not a planUnproven at commercial scale; timeline risk
Decision lens for a 2026 siting or power commitment. Lead times and capacities are 2025-2026 practitioner ranges (IEA, EPRI, SemiAnalysis, SMR Intel, DCD). SMR and fusion dates are announced targets widely regarded as optimistic.
$5.2T central ($3.7T–$7.9T)forecast
forecast AI-capable data-center capex to 2030: ~$5.2T midline within a scenario range
Stress each investment phase; the scenario range does not supply probabilities.
Scope & caveats

McKinsey’s constrained/central/accelerated modeled demand cases: $3.7T/$5.2T/$7.9T. Includes energy and technology infrastructure; not annual expenditure or scenario probabilities.

~$800Bmodeled
Bain September 2025 scenario: annual monetization gap for anticipated 2030 demand
Bain’s scenario frames a monetization requirement; the project still needs its own cash test.
Scope & caveats

Bain’s stated scaling and monetization assumptions, including reinvested savings. Not an observed shortfall or the probability of the guide’s bubble scenario.

~$4.2Tmodeled
Bain September 2026 model: new annual AI revenue required in 2031 to reach a ~$6T market
a requirement on a new model and horizon; do not net it against the 2025 gap
Scope & caveats

Bain sizes the consumer and enterprise AI market at $1.2–1.8T and computes the gap to ~$6T from the top of that range, assuming capex near 25% of revenue. A model requirement on a 2031 horizon, not an observed shortfall; not comparable with Bain's 2025 ~$800B gap for 2030, which used a different model.

~485 → ~950 TWhforecast
global data center electricity demand 2025 → 2030 (~doubling; ~3% of global electricity)
The IEA April 2026 scenario roughly doubles annual data-center energy demand; if local firm supply misses that ramp, phase capacity waits.
Scope & caveats

The 2025 figure is an IEA estimate; the 2030 figure is an IEA projection. Same IEA series and boundary as the ~950 TWh figure in Chapter 16.1.

First deployment 2030; fleet by 2035forecast
Google–Kairos first deployment / fleet targets; not Amazon’s schedule
Google–Kairos targets 2030/2035 and Amazon’s Cascade targets the 2030s; a pre-2030 energization plan still needs another firm source.
Scope & caveats

Google–Kairos company targets, not an Amazon/X-energy timeline, operating capacity or a delivery guarantee.

Carry the combined shock through the power portfolio. Use the 100 MW announced / 40 MW financed / 20 MW energized phase example in Chapter 16.1, not another forecast of delivered capacity. Suppose power slips six months while useful-service demand drops to 50% and the assumed residual falls 25%. Then suspend the next fit-out release, re-price equipment commitments, and keep only the power rights whose holding cost clears the downside case. For each grid, gas, nuclear or storage option, record contracted MW, earliest deliverable date, duration, fuel or energy dependency, permits, counterparty, termination payment and carbon boundary. Announced generation is not firm supply, storage needs recharge, and a clean-energy certificate is not a dispatch right. Release the next phase only when the power milestone, funding and accepted customer workload all return together. The case’s 60% useful-service hurdle is one explicit management choice. An SMR or fusion target moving closer on a slide does not meet those gates. → operating flexibility offers in Chapter 15.8; financing consequences in Chapter 2.5.

Early 2030sforecast
CFS generating-plant target
SPARC is a demonstration machine; ARC’s announced date does not supply a firm near-term campus commitment.
Scope & caveats

Company target for the generating plant. SPARC is the demonstration machine; no firm 2030 data-center supply is established.

Demand-side wildcards

The entire demand curve rests on assumptions that a single shock could invalidate, and the wildcards cut both ways. On the downside sit three. One is an algorithmic-efficiency step (a DeepSeek-style collapse in training or inference cost) that deflates the compute needed per unit of value. Another is an enterprise-adoption air-pocket: the MIT NANDA study found ~95% of enterprise GenAI pilots produced no measurable P&L impact on $30-40B of spend. The third is a regulatory or energy backlash that caps siting. That one is no longer hypothetical. New York's Executive Order 62 (14 July 2026) holds DEC discretionary permits for new or expanded data centers able to draw 50 MW or more until the final statewide GEIS, with no fixed end date. Texas has told TCEQ to halt data-center permits pending ERCOT's audit (→ Chapter 3.9). On the upside, the same efficiency gains can increase total compute under the Jevons rebound condition: cheaper inference begets more inference. Reasoning and agentic workloads are a structural demand multiplier that could keep the supercycle alive longer than the bears expect (→ Chapter 16.3).

The decision consequence is asymmetric. A pure-play, single-generation, debt-financed asset is fragile to every downside wildcard and benefits from the upside ones only if it is already full. A flexible substrate is the cheapest insurance against the wildcard you cannot predict: over-provisioned floor loading and water, modal procurement, contracted rather than merchant revenue, and a power deal that flexes. What it buys is the right to be wrong about the forecast.

Deep dive: why the efficiency wildcard is the hardest to scenario-plan

The efficiency wildcard is hard because it is two-sided and the sign is unknowable in advance. The bear reading starts with a frontier algorithmic advance: sparser models, better quantization, a cheaper attention mechanism, or distillation that closes the gap to a frontier model at a fraction of the FLOPs. That collapses the compute needed per unit of delivered value, the demand curve undershoots, and capacity built against the old efficiency assumption strands. The DeepSeek release in January 2025 showed that a single release can re-price AI equities overnight, even though capex guidance kept rising afterwards.

The bull reading is the Jevons paradox: when a resource gets cheaper, total consumption can rise if demand expands enough to absorb the efficiency gain. Cheaper inference can make more applications economically viable and raise aggregate token demand if adoption absorbs the gain. Ramp’s effective token-price index fell 41%, from the March 2026 peak of $1.15 to $0.68 per million tokens on 9 September 2026. Both readings have empirical support, and they can be true in sequence. A sharp efficiency gain strands the operators positioned for the old curve while rewarding those who can absorb the new, higher-volume, lower-margin demand. The robust posture designs the asset to earn under both: high utilization, low unit cost, and a fleet that can pivot from training-shaped to inference-shaped as the mix shifts. Operators who planned only the bull case are exposed to the bear shock, and the reverse. The survivors planned the transition between them. → the efficiency-vs-demand treatment in Chapter 16.3.

Stranded assets, obsolescence and systemic constraints

Each scenario hides a different stranded-asset failure mode, and naming them is the point of the exercise. Stranded silicon is the obsolescence risk, and GPU life is disputed: a contested 2–3-year obsolescence bear case vs published 4–6-year useful-life estimates and 5–6-year book policies. If the bear case materializes, a generational density step can leave current-generation fleets uneconomic against newer parts and uncompetitive against grid power before they are depreciated. The step runs from ~132 kW NVL72 racks (HPE’s nominal for GB200 and GB300) to Vera Rubin NVL72, shipping since June 2026, where NVIDIA’s DSX reference design plans 330 kW per cabinet. Kyber-class racks at ~600 kW come next: NVIDIA targets H2 2027 and SemiAnalysis reports 2028 (→ Chapter 16.2). Stranded substations are the power-delivery mirror image: an interconnection slot energized for a campus whose demand never materializes, or a behind-the-meter gas plant carrying carbon liability for a load that digested. Stranded balance sheets are the financial endgame: long-lived debt underwritten against short-lived silicon, and an under-depreciation question that turns reported earnings into borrowed future write-downs (→ Chapter 1.8).

Systemic and societal constraints form the outer boundary on all three scenarios. Grid reliability has become a planning constraint. On 4 May 2026 NERC issued a rare Level 3 alert, after large-load loss events that included Virginia in July 2024. In that event about 1,500 MW of data-center demand left the grid over a six-fault, 82-second sequence, as facilities transferred to backup. Then came a larger one. When a single 230 kV fault near Ashburn cleared normally on 22 July 2026, about 3.8 GW still moved to backup. That is roughly 2.5 times the 2024 scale. The alert does not make its Essential Actions mandatory. One of them asks transmission owners to work with their customers, where possible, so facilities ride through as much as they can. So far, binding ride-through rules are regional. SPP applies large-load requirements to requests from January 2026, and ERCOT’s NOGRR282 covers new large computational loads from August 2026. PJM has proposed its own requirements (September 2026), and NERC’s computational-load standards passed final ballot in October 2026 but still need Board adoption and FERC approval (→ Chapter 4.10).

Water, community social license, and the concentration of load in a few jurisdictions are real ceilings that a demand curve cannot wish away. Virginia alone is projected at 39-57% of state electricity by 2030 (EPRI, Powering Intelligence 2026). The deepest systemic risk is correlation. Every scenario assumes the constraints relax independently, but a power slip, a residual-value shock and a demand air-pocket are correlated. They tend to arrive together in a downturn, which is exactly when a levered, single-generation, merchant-exposed asset has the least room to survive them. An attacker can also induce the failure modes that random faults trigger (→ Chapter 11.10).

Deep dive: how to build an asset that is robust across scenarios rather than optimal for one

Under uncertainty the instinct is to forecast harder and optimize for the most likely scenario. That is the wrong instinct. Being optimized for the scenario that does not arrive is catastrophic, and being merely robust across all three costs little. The robust posture has five concrete moves, each trading a little day-one efficiency for survival across worlds.

One: over-provision the irreversible substrate, defer the reversible fit-out. Floor loading, water availability, electrical headroom and pipe-rack space accommodate the density ramp toward 600 kW racks, while the IT fit-out stays matched to the current generation. You buy the option to ramp without committing the spend (→ Chapter 14.9). Two: keep procurement modal. A powered shell and colo/neocloud overflow preserve the option to exit that a full greenfield build forecloses, which is the difference between a digestion soft landing and a stranded-asset write-down. Three: contract revenue, don’t merchant it. Enforceable take-or-pay and credit-tenant leases can support debt capacity if the tenant and remedies survive the bubble. Merchant exposure is a leveraged bet on the supercycle. Four: make the power deal flex. Grid services, curtailable load and demand response turn a fixed power liability into a hedge that earns in digestion and survives in bubble (→ Chapter 15.8). Five: design the fleet to pivot from training-shaped to inference-shaped as the compute mix shifts toward inference, so the same asset can earn under either architecture where the workload, customer geography and network path allow it. None of these is free. All of them are cheaper than being precisely optimized for the 2030 that did not come.

This chapter sits atop Part 16 and pulls the threads together. Chapter 16.1 covers the power-bound framing that makes time-to-megawatt the deciding variable. Chapter 16.2 covers the subsystem roadmaps that drive the density ramp (415 VAC → 800 VDC, NVL72 → Kyber, HBM4). Chapter 16.3 covers the efficiency-vs-demand and Jevons dynamics behind the demand-side wildcards. Chapter 16.4 covers the macro economics of the build-out: capex wave, financing and the revenue-vs-capex gap. Related chapters: firm-level economics and the depreciation debate behind the bubble scenario in Chapter 1.8; the inference-distribution argument in Chapter 1.3; speed-to-power mechanics in Chapter 3.2; grid integration and flexibility in Chapter 15.8; the reliability rethink that keeps goodput up through failures in Chapter 12.2; refresh and decommissioning economics in Chapter 14.9; and the cyber-physical dual-use of every failure mode in Chapter 11.10.
Cite this chapter
Fehn, J. (2026). Scenarios for 2030 (Chapter 16.5). The Definitive Guide to AI Data Centers. https://aidatacenterguide.com/part-16-trends-roadmaps-and-the-future/16-5-scenarios-for-2030 (accessed 2026-10-25).
@misc{aidc-16-5,
  author       = {Fehn, Jacob},
  title        = {Scenarios for 2030 (Chapter 16.5)},
  howpublished = {The Definitive Guide to AI Data Centers},
  year         = {2026},
  url          = {https://aidatacenterguide.com/part-16-trends-roadmaps-and-the-future/16-5-scenarios-for-2030},
  note         = {Accessed 2026-10-25}
}
Spotted an error? Suggest an edit