Urgent.News

What's breaking now, across thousands of outlets.

AI

What are the AI lab compute commitments?

What are the AI lab compute commitments?

AI lab compute commitments could result in $614 billion in infrastructure spending through 2030, according to Bernstein analyst Mark Moerdler. This figure is lower than the $750 billion often cited, as construction delays, cancellations, and flexible hardware purchases could delay or reduce payments. Annual infrastructure spending may peak at $184 billion in 2031, with costs rising gradually as data centers become operational.

OpenAI reportedly achieved $50 billion in annualized revenue in September, with growth at 77% year-over-year. This revenue growth could help cover the expanding infrastructure needs, though projections remain uncertain. Oracle's relationship with OpenAI involves about $300 billion in contracted capacity, spread over five to six-year agreements.

OpenAI represents less than half of Oracle's remaining performance obligations, limiting the concentration of risk. Microsoft has a separate $250 billion Azure services commitment from OpenAI, with capacity delivered in six-year stages. Microsoft's diversified cloud operations may provide better cushioning against delays compared to smaller infrastructure specialists.

Amazon has commitments totaling $138 billion across seven- and eight-year terms, including its Trainium processors. CoreWeave's OpenAI agreements amount to up to $22.4 billion, but these are contract ceilings rather than guaranteed revenue. The bigger industry risk may surface when computing shortages ease, exposing speculative construction projects and providers reliant on expensive financing.

Existing contracts with established cloud companies seem more resilient than future demand for specialized computing rentals.

Written by urgent.news from Investing.com's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at investing.com →

More in AI

Rewrite or refactor? How I decide

Rewrites are tempting because old code is annoying. You open a file, wince, and a quiet voice says "I'd do this so much better from scratch." Sometimes that voice is right. Often it isn't.

  • Rewrites are seductive but risky, often stalling at the last 20%.
  • Refactor recommended when code works, issues concentrated, and small steps possible.
  • Rewrite suggested when core design blocks new features or improvement is significant.

More from Sunday 8 November →