Historical operating KPI

CoreWeave Revenue Backlog History

Name: CoreWeave Revenue Backlog quarterly history
Creator: VizualStocks

Latest reported: $104.2B
Period: Q2 2026
QoQ: +4.8%
YoY: +246.2%

Metric ID: revenueBacklog
Frequency: quarterly
Status: active

About this KPI

Why it matters

Revenue backlog combines remaining performance obligations with other estimated revenue under committed customer contracts, giving a forward view of contracted demand.

Why investors follow it

The history helps investors compare bookings momentum with CoreWeave’s infrastructure expansion and the pace at which contracted demand becomes reported revenue.

What it does not tell you

Backlog is not current revenue and remains subject to delivery and service availability; it does not show recognition timing, concentration, cancellations, margins or financing needs.

Maintained history, without the manual work

Pull this maintained history through the VizualStocks API instead of rebuilding it from filings every quarter.

Use this in your productUse in your productView API documentationView API docs

GET/v1/companies/CRWV/metrics/revenueBacklog?order=asc

Understanding Revenue Backlog

How is CoreWeave revenue backlog different from RPO?

CoreWeave’s revenue backlog includes remaining performance obligations plus additional estimated revenue under committed customer contracts. It is therefore broader than RPO alone, with recognition tied to delivery and the availability of contracted services.

Issuer definition

How can I follow backlog conversion?

Compare the backlog balance with recognized revenue and the timing of new capacity coming online. Backlog represents a stock of contracted future business, so a change reflects both new commitments and revenue earned from existing contracts.