RPO Tracker · CRWV · Updated 2026-05-07

CoreWeave: Contracted Revenue

CoreWeave reported $99.4B of Revenue backlog at Q1 2026, which is 15.9x the trailing twelve months of the revenue it converts into. The median across all 11 disclosures tracked is 3.34x.

Contracted

$99.4B

Q1 2026, Whole company

Coverage

15.9x

against $6.2B of trailing revenue

Due within 12 months

Not disclosed

no near-term split published

Weighted duration

Not disclosed

the company published none

Q1 2026

Period ended 2026-03-31 · reported 2026-05-07

Metric
Revenue backlog · Whole company
Contracted balance
$99.4B, +284% year over year
Denominator
Full year 2025 revenue of $5.13bn, plus Q1 2026 revenue of $2.08bn, less Q1 2025 revenue of $0.972bn.
Coverage
15.9x (scopes match)
Duration
CoreWeave publishes contracted power rather than contract duration: over 1 GW active against 3.5 GW contracted at this disclosure. That says when capacity arrives, not when revenue is recognised.
Concentration · largest customer Microsoft and OpenAI
No ex largest customer figure. CoreWeave's backlog is built on a small number of very large counterparties: three OpenAI agreements, Microsoft, a Meta expansion to about $35bn of total commitments and an Anthropic agreement signed in April 2026.
Notes
Revenue backlog, not RPO. CoreWeave defines backlog as its remaining performance obligations plus committed contracts that do not yet meet the RPO recognition test, so it is a broader number than the ASC 606 figure and is not directly comparable with Microsoft's or Oracle's. More than $40bn of new commitments were signed in this single quarter, and management called 2026 capacity largely sold out. This row is one quarter behind the rest of the table: Q2 2026 results are due on August 11, 2026 and this row updates then.

Sources: company filing or release · tier-1 report · company filing or release

Our Coverage

Part of the free RPO and Backlog Coverage Tracker, CC BY 4.0. Cite as: RPO and Backlog Coverage Tracker, Regards of Wallstreet, https://www.regardsofwallstreet.com/data/rpo/entity/coreweave. The methodology explains how coverage is calculated and why the scope of both halves matters.