The Compute Ceiling Is Real — And Your Cloud Vendor Is Becoming Your Competitor
The Infrastructure You're Planning On May Not Arrive
Nearly half of US data centers planned for 2026 are now delayed or canceled — driven by power grid limitations, permitting challenges, and local opposition (including armed violence against data center advocates). This isn't a temporary blip. It's a physics problem masquerading as a business story. Every AI initiative on your roadmap that assumes elastic compute availability needs stress-testing against a scenario where you get 60% of planned capacity.
Set this against the demand side: Anthropic just expanded a deal for 3.5 gigawatts of Google TPU capacity through Broadcom that won't come online until 2027. Meta committed $135B in 2026 capex and still needs $21B from CoreWeave through 2032 because it can't build fast enough internally. OpenAI is measuring ambitions in gigawatts. The companies that secured capacity 18-24 months ago now hold a structural advantage that's nearly impossible to replicate.
Amazon Is Playing a Different Game
Andy Jassy's shareholder letter was a competitive declaration, not an earnings update. Three numbers matter: 98% of Amazon's top 1,000 EC2 customers now run on Graviton, the custom chip business hit $20B in revenue (doubled in ~2 months), and AWS AI reached $15B annualized — growing 260x faster than AWS itself at the same stage. Two unnamed customers tried to buy Amazon's entire Graviton supply for 2026.
The strategic implication: Amazon isn't just reducing its Nvidia dependency — it's becoming a chip vendor. Jassy openly contemplated selling Trainium racks to third parties. If AWS becomes a direct chip competitor while hosting your AI workloads, your vendor relationship has fundamentally changed. Google's commitment to future Intel data center chips signals even hyperscalers want supply chain diversification.
The era of assuming infinite elastic compute is ending — it's now subject to energy physics rather than software scaling.
The CoreWeave Concentration Risk No One's Pricing
CoreWeave's $87.8B revenue backlog sounds impressive until you see the concentration: 40.1% from Meta and 25.5% from OpenAI — 65.6% from two customers. The company lost $1.17B on $5.13B revenue in 2025 and just raised $1.75B in debt to keep building. If Meta builds more internal GPU capacity (which their $135B capex suggests), or OpenAI diversifies compute sourcing, CoreWeave's economics shift dramatically. That disruption cascades to every service running on their infrastructure.
Three competing compute strategies are emerging: Amazon is building ($200B capex, custom silicon), Meta is renting ($35B to CoreWeave, $27B to Nebius), and OpenAI is retreating from global infrastructure despite raising $122B. The right answer almost certainly varies by use case, but few companies can pursue all three paths. Your compute strategy needs a clear thesis on which model matches your workload profile — and a contingency plan for when the market shifts.
What to do
Audit all cloud AI capacity contracts and model 2027 roadmap at 60% of planned compute availability by end of Q2
Open parallel negotiations with AWS on Trainium/Graviton and Google on TPU pricing within 30 days to build multi-vendor optionality
Map your CoreWeave exposure (direct and indirect through vendors) and develop a multi-provider hedging strategy this quarter
Add energy and power procurement to your strategic risk register and evaluate direct power procurement options for any owned/leased data center capacity