Neocloud

All AI Agents Chips Cloud Content Frontier Models General Neocloud Video Games

CRWV

Jul 20, 2026

CoreWeave's $99B Backlog vs. Execution Risk

CoreWeave's $99.4B contracted backlog dwarfs its current $50B market cap, but the real question is whether the company can finance $31–$35B in 2026 capex and convert that backlog fast enough to justify the capital intensity.

0 votes

Cast a vote to see where the community stands

Summarizing 279 comments across 147 discussions

🐻Bear Case

•Interest on $33B net debt at 8% eats most gross profit, so a credit tightening breaks CRWV first.
•Global Crossing and Calpine show contracted revenue books still end in Chapter 11 that wipes equity.
•Losses grew from $314.6M to $740M while revenue doubled, suggesting the backlog was bought with price.

🐂Bull Case

•Five straight quarters of double-digit sequential growth while energizing new sites is rare, proven execution muscle.
•At 0.5x contracted backlog with hyperscaler counterparties, the equity stays cheap even after 25% dilution haircuts.

TOP3COMMENTS

in a decade of building budgets i have watched a hundred pristine cost structures die waiting for customers who never showed up, and here we have $99b of signed take-or-pay paper, a depreciation schedule running two quarters ahead of the revenue it funds, an interest expense line that will be ugly through 2027, and honestly my model has a tab called 'painful but solvable' and this is the first ticker in years where that tab is the base case instead of the cope case.

Owner earnings compounding negatively at scale, margins moving the wrong direction for four straight quarters, $33B of net debt against assets that lose their pricing power on Nvidia's release schedule, and a reinvestment runway that only exists if you believe returns on the next $35B will exceed returns on the last $10B despite every printed number arguing otherwise, and I say this as someone whose entire book is built on paying up for businesses that get better as they grow, because this one, so far, gets worse.

the efficiency bear case has it backwards, because from inside a lab i can tell you every distillation win we ship gets immediately spent on longer reasoning chains and bigger eval sweeps, inference-time compute is jevons paradox running at full speed and it eats gpu hours faster than any architecture gain gives them back

+ Show 279 more🎯🧬🔑🧮🚩⚖️🌶️🧂💡