ResourcesGuide

Backlog, RPO and ARR: How to Read AI Cloud Contract Numbers

AI cloud companies announce contract numbers in the tens or hundreds of billions. Here is what remaining performance obligations, backlog, ARR and contract value each count, which ones are audited, and how a signed contract does or does not become cash for shareholders.

Published Updated 10 min readHow we research

Key takeaways

  • RPO (remaining performance obligations) is the contracted revenue not yet recognized under US accounting rules (ASC 606) and is disclosed in financial-statement notes (annual statements are audited, while quarterly statements are generally unaudited); backlog is a company-defined measure that can include more; ARR is an annualized run rate, a speed rather than a total. None of them is cash.
  • CoreWeave reported $103.7 billion of RPO and about $104 billion of revenue backlog at June 30, 2026; it expects 41% of the RPO to be recognized in the 24 months to June 2028 and the rest over months 25 to 78.
  • ARR is defined differently by each company: Nebius multiplies the last month’s AI cloud revenue by 12 ($3.0 billion at June 30, 2026); IREN multiplies contracted GPU-hour prices by 8,760 hours ($1 billion operating, $4 billion contracted for 2026 capacity).
  • Headline contract values often include options: TeraWulf’s Anthropic lease is about $19 billion over the base term and up to about $33 billion only if both extensions are exercised.
  • Between a signed contract and cash for shareholders sit delivery, customer acceptance, capex, lenders paid first, interest and possible dilution. In the hypothetical below, moving the loan rate from 9% to 15% turns a $21.5 million five-year surplus into a $71.2 million shortfall.

Market risk reading, cross‑asset context and an events calendar: see Exent Market intel →

What is the difference between backlog, RPO and ARR?

RPO is a stock of contracted future revenue defined by accounting rules; backlog is the company’s own, usually wider, version of that stock; ARR is how fast revenue is coming in today, multiplied up to a year. If a number appears in the financial-statement notes under “remaining performance obligations”, it follows ASC 606; if it is called backlog, contracted revenue or ARR, read the company’s footnote, because each one is defined differently.

Scope: this guide covers how AI cloud companies (neoclouds), hyperscalers and data-center landlords report contracts, using their 2026 filings. It does not cover lease accounting in depth or software-company bookings. It is education, not a view on any stock; for the companies themselves start at what is a neocloud.

MeasureWho defines itWhat it countsAudited?Example (dated)
Total contract value (TCV)The companyEverything a contract could pay over its life, sometimes including optionsNoMeta–Nebius: up to ~$27B (Mar 16, 2026)
Remaining performance obligations (RPO)ASC 606 (US accounting standard)Contracted revenue not yet recognized, billed or unbilled, adjusted for expected creditsAnnual statements: audited; cited quarterly statements: unauditedCoreWeave $103.7B; Oracle $664B
Revenue backlogThe companyRPO plus other amounts the company estimates it will earn under committed contractsNoCoreWeave ~$104B (Jun 30, 2026)
Annualized run rate (ARR)The companyCurrent revenue speed x 12 months or x 8,760 hoursNoNebius $3.0B; IREN $1B operating
Contracted ARR / contracted lease revenueThe companyRun rate or lease value of capacity signed but not yet deliveredNoIREN $4B for 2026 capacity; Applied Digital ~$36B
Deferred revenueAccounting (balance sheet)Cash already received for service not yet delivered, a liabilityAnnual statements: audited; cited quarterly statements: unauditedCoreWeave $9.7B (Jun 30, 2026)
Active vs contracted power (MW)The companyCapacity running today vs capacity signed for; definitions of MW differNoCoreWeave 1.5 GW active, ~3.7 GW contracted
  • Total contract value (TCV)
    Who defines it
    The company
    What it counts
    Everything a contract could pay over its life, sometimes including options
    Audited?
    No
    Example (dated)
    Meta–Nebius: up to ~$27B (Mar 16, 2026)
  • Remaining performance obligations (RPO)
    Who defines it
    ASC 606 (US accounting standard)
    What it counts
    Contracted revenue not yet recognized, billed or unbilled, adjusted for expected credits
    Audited?
    Annual statements: audited; cited quarterly statements: unaudited
    Example (dated)
    CoreWeave $103.7B; Oracle $664B
  • Revenue backlog
    Who defines it
    The company
    What it counts
    RPO plus other amounts the company estimates it will earn under committed contracts
    Audited?
    No
    Example (dated)
    CoreWeave ~$104B (Jun 30, 2026)
  • Annualized run rate (ARR)
    Who defines it
    The company
    What it counts
    Current revenue speed x 12 months or x 8,760 hours
    Audited?
    No
    Example (dated)
    Nebius $3.0B; IREN $1B operating
  • Contracted ARR / contracted lease revenue
    Who defines it
    The company
    What it counts
    Run rate or lease value of capacity signed but not yet delivered
    Audited?
    No
    Example (dated)
    IREN $4B for 2026 capacity; Applied Digital ~$36B
  • Deferred revenue
    Who defines it
    Accounting (balance sheet)
    What it counts
    Cash already received for service not yet delivered, a liability
    Audited?
    Annual statements: audited; cited quarterly statements: unaudited
    Example (dated)
    CoreWeave $9.7B (Jun 30, 2026)
  • Active vs contracted power (MW)
    Who defines it
    The company
    What it counts
    Capacity running today vs capacity signed for; definitions of MW differ
    Audited?
    No
    Example (dated)
    CoreWeave 1.5 GW active, ~3.7 GW contracted

What is RPO in finance, and what does it leave out?

RPO is the revenue a company has a contract for but has not yet earned, as it must disclose under ASC 606, together with an estimate of when it will be recognized. CoreWeave’s 10-Q for the quarter ended June 30, 2026 reports $103.7 billion of unsatisfied RPO, including billed and unbilled amounts, and gives the timing: 41% over the 24 months to June 30, 2028, 39% in months 25 to 48 and the rest in months 49 to 78. It also says the figure is net of variable consideration such as expected credits under service-level terms, amounts that may not be recognized because of delivery delays, and capacity the customer has the right to resell.

A quick sense check, our arithmetic: 41% of $103.7 billion is about $42.5 billion over two years, or about $21 billion a year, against Q2 2026 revenue of $2.575 billion (about $10.3 billion a year at that pace). That only happens if CoreWeave turns much more of its roughly 3.7 GW of contracted power into running capacity; at June 30 it had 1.5 GW active. RPO tells you demand is signed; it does not tell you the capacity, financing and delivery are in place. Oracle reports the same measure at a far larger size, $664 billion at August 31, 2026, up $209 billion in a year, while its free cash flow was negative $5 billion in that quarter.

Why can backlog be bigger than RPO?

Because backlog is whatever the company defines it to be, and it usually adds estimates that the accounting standard does not allow in RPO. CoreWeave’s footnote says revenue backlog “includes remaining performance obligations, plus other amounts we estimate will be recognized as revenue in future periods under committed customer contracts,” subject to delivery and availability of service. At June 30, 2026 the two were almost the same (about $104 billion vs $103.7 billion). The release also says backlog excludes more than $25 billion of net new commitments signed in early Q3, Those commitments may increase the next reported backlog, alongside revenue recognition and other adjustments.

Landlords report a third kind of number: lease value. Applied Digital says its leases for about 1.41 GW of critical IT load represent about $36 billion of contracted revenue over the initial base terms, or about $86 billion if all renewal options are exercised (8-K, Oct 7, 2026). The $36 billion is the committed figure; the $86 billion depends on tenants choosing to stay. How these contract numbers line up across companies is in neocloud stocks compared.

How is ARR calculated, and why do companies’ ARR differ?

ARR multiplies a current revenue speed up to a year, and each company chooses the speed. Nebius uses the last month of the quarter: AI cloud revenue for June 2026 times 12 gave $3.0 billion, against $582.3 million of revenue for the whole quarter (about $2.3 billion a year at the quarter’s average pace, because revenue grew during the quarter). IREN uses contracted GPU-hour prices times 8,760 hours, and its release warns that recognized revenue “may be materially lower”.

CompanyHow ARR is definedARR figureGAAP revenue for comparison
NebiusLast month’s AI cloud revenue x 12$3.0B (Jun 30, 2026)$582.3M in Q2 2026
IRENGPU-hour price of commissioned, contracted GPUs x 8,760$1B operating (Aug 26, 2026); $4B contracted for 2026 capacity$707.0M in FY26, of which $128.8M AI cloud

IREN’s $4 billion of contracted ARR is a target for capacity to be operating by December 31, 2026, subject to commissioning, testing and customer acceptance. Treat contracted ARR as a plan with signatures, and operating ARR as the speed actually reached.

What do “up to” and “with extensions” contract values mean?

They mean part of the headline number is optional. Read the release for three things: the firm base term, what the customer may choose to add, and what the provider may resell to someone else. Three dated examples:

DealFirm partHeadline maximumWhat is optional
TeraWulf–Anthropic, 20-year lease (Aug 5, 2026)~$19B over the initial term~$33BTwo five-year extensions, at Anthropic’s choice
Applied Digital leases, ~1.41 GW (Aug 31, 2026)~$36B over base terms~$86BAll renewal options exercised
Nebius–Meta, five years (Mar 16, 2026)$12B of dedicated capacity from early 2027Up to ~$27BUp to $15B of further capacity, which Nebius intends to sell to other customers first, with Meta buying what remains

How does contracted backlog become cash available to shareholders?

Only after the capacity is built, delivered and accepted, the lenders who financed it are paid, and the costs of running it are covered; what is left belongs to shareholders, and new shares or convertibles can dilute it. The order matters because in a GPU-backed loan the customer’s payments go to the lender first: CoreWeave’s 10-Q describes its delayed-draw loans as secured by the financed assets and the pledged contractual cash flows, amortizing as those cash flows arrive, with the excess released to the company.

From signed contract to shareholder cash
1. Sign
  • Take-or-pay contractcounted in RPO and backlog
  • PrepaymentCoreWeave 15–25% of TCV
  • Take-or-pay contract → GPU-backed loan · contract pledged as collateral
  • Prepayment → GPUs, servers, data center · pays part of the build
2. Build
  • GPUs, servers, data centerCoreWeave H1 2026 capex $14.1B
  • GPU-backed loansecured on the contract
  • GPU-backed loan → Delivery and acceptance · capacity built with borrowed money
3. Deliver
  • Delivery and acceptancerevenue starts; delays push it out
  • Delivery and acceptance → Lender paid first · customer payments go here first
  • Delivery and acceptance → Power, rent, staff · running costs
  • Delivery and acceptance → Shareholders · excess cash released
4. Collect and pay out
  • Lender paid firstinterest and amortization
  • Power, rent, staff
  • Shareholderswhat is left, after dilution
Simplified sequence for a GPU cloud. A landlord follows the same order with a building instead of GPUs.

Worked example (hypothetical, not any company’s contract): a five-year, $1,000 million take-or-pay contract ($200 million a year), a 15% prepayment ($150 million, inside CoreWeave’s disclosed 15–25% range), $600 million of capex, a $450 million five-year amortizing loan for the rest, and running costs of 25% of revenue. Cash for shareholders is customer cash minus capex plus the loan minus loan payments minus running costs, before tax, undiscounted and with no value left in the GPUs.

Step ($ millions, 5 years)Base: loan at 9%Loan at 15%9%, but 10% of revenue lost to delays and credits
Customer cash, incl. the prepayment1,000.01,000.0900.0
Capex−600.0−600.0−600.0
Loan received+450.0+450.0+450.0
Loan payments: 450 x r / (1 − (1 + r)^−5), x 5 years−578.5 (115.7 a year)−671.2 (134.2 a year)−578.5
Running costs (25% of $1,000M contract)−250.0−250.0−250.0
Left for shareholders over five years+21.5−71.2−78.5

The lesson is the sensitivity, not the totals: on these assumptions most of a $1 billion contract goes to the build, the lender and the running costs, and a higher loan rate or a delivery slip can wipe out the shareholders’ share. The surplus improves sharply if the GPUs can be re-rented after the contract (CoreWeave depreciates them over six years) or if prepayments are larger: Nebius says prepayments covered 50–60% of the capex on its Q2 2026 deals and estimates a payback of 1 year 10 months, a company estimate based on forecast costs. CoreWeave’s actual interest bill was $640 million in Q2 2026; why it pays what it pays is in CoreWeave’s debt explained. Dilution is the last step: convertible notes can become shares (see stock dilution).

When are contract numbers misleading, and when are they solid?

They mislead when one customer dominates, when options are counted as if firm, and when the capacity to serve them does not exist yet. CoreWeave’s three largest customers were 36%, 26% and 10% of Q2 2026 revenue, so a large part of the backlog depends on a few counterparties (see who are CoreWeave’s customers). Counterexample, when they are solid: a take-or-pay contract with an investment-grade customer and a prepayment is strong enough for lenders to finance on investment-grade terms: IREN raised $3.6 billion of investment-grade GPU financing for its Microsoft contract at a weighted 6.0%, and CoreWeave’s own contract-backed loans range from an effective 7% (the 2026 facility) to 15% (the 2023 one). Lenders, in other words, price backlog by the customer and the contract behind it.

  • Limitations: all figures are as reported in filings and releases dated Mar 16 to Oct 7, 2026; RPO and backlog change every quarter and will be restated in Q3 2026 reports (November 2026).
  • Backlog, ARR, contracted ARR and lease values are company-defined and not audited; compare them only within one company over time.
  • The worked example is a hypothetical illustration with round assumptions; it ignores taxes, the time value of money, residual GPU value and refinancing.
  • Payback and per-megawatt figures are company estimates, not reported results.

Add market context with Exent Market intel

Market intel provides market context, cross-asset analysis, an events calendar and regular written notes. These can inform your review of an existing plan; they do not reliably predict crashes or guarantee better outcomes.

  1. An events calendar with earnings dates, Fed meetings and macro releases, so you know when the next RPO and backlog figures arrive.
  2. Regular written notes that read cross-asset ratios such as stocks vs bonds and high-beta vs low-volatility stocks, the backdrop that decides how much the market pays for distant contract revenue.
  3. A reading of US market risk (Risk ON, Neutral or Risk OFF) built on four pillars, with an email when the reading changes.

Exent is our product. Educational content, not investment advice.

Frequently asked questions

RPO, or remaining performance obligations, is the contracted revenue a company has not yet recognized, disclosed under the US accounting standard ASC 606 with an estimate of when it will be earned. CoreWeave reported $103.7 billion at June 30, 2026.

Not exactly. Backlog is a company-defined estimate of revenue under signed contracts, subject to delivering the capacity; it can shrink through credits, delays or customer resale rights, and it is not cash.

RPO follows accounting rules and appears in the financial-statement notes (audited annually, generally unaudited in quarterly reports); backlog is the company’s own measure and can add estimates RPO excludes. At CoreWeave they were almost equal at June 30, 2026: $103.7 billion of RPO and about $104 billion of backlog.

It is the annual revenue speed of capacity that is signed but not yet running. IREN reported $4 billion of contracted ARR for 2026 capacity against $1 billion of operating ARR on August 26, 2026.

CoreWeave expects 41% of its $103.7 billion of RPO to be recognized in the 24 months to June 30, 2028, 39% in months 25 to 48 and the rest in months 49 to 78 (10-Q, June 30, 2026).

No. It is contracted revenue not yet recognized, before the cost of building and running the capacity. Oracle reported negative free cash flow of $5 billion in the same quarter to August 31, 2026.

Nebius multiplies only the last month of the quarter by 12. Because revenue grew during Q2 2026, that gave $3.0 billion of ARR, while four times the quarter’s $582.3 million revenue is about $2.3 billion.

A contract in which the customer pays for reserved capacity whether or not it uses it. CoreWeave says such committed contracts made up 98% of its Q2 2026 revenue and typically include a prepayment.

Sources

Add market context to your plan.

Market intel provides a Risk ON / Neutral / Risk OFF reading from four pillars, cross-asset analysis, an events calendar and regular written notes. Context for reviewing a plan, not a crash forecast.

See what Market intel includesLimited offer67% off your first month

Educational content, not investment advice. Examples are illustrative; past performance does not guarantee future results.

DISCLAIMER: Exent AI is an informational research platform and does not provide investment advice, financial advice, or act as an investment adviser, broker-dealer, or fiduciary. All content, analytics, and model outputs are provided for educational and informational purposes only and should not be relied upon as a recommendation to buy, sell, or hold any financial instrument. Investing involves risk, including the possible loss of principal. Exent AI does not execute trades, hold customer funds, or provide brokerage services. Past performance and hypothetical results are not indicative of future results. Third-party data and AI-generated outputs may be incomplete or inaccurate.