Financial research concept

Data Cloud Remaining Performance Obligations

Data cloud remaining performance obligations represent contracted revenue that has not yet been recognized and whose conversion can depend on future customer consumption.

By Lee BaileyPublished Sep 23, 2026
Research context

See what supports this page, how current it is, and where comparable or historical context is available.

Research date
Sep 23, 2026Use the dated article and cited sources for the definition, examples, and stated limitations.
Operating-model context
15 connected conceptsPart of the reviewed Data Cloud Consumption Economics; issuer definitions remain distinct where disclosed.
Company examples
1 reviewed companyRelationships reflect supported examples, not a normalized cross-company KPI ranking.
  1. Why it matters
  2. Investor caution
  3. Part of the Data Cloud Consumption Economics
  4. See It in Company Research
  5. Continue Research

Data Cloud Remaining Performance Obligations, or RPO, represent contracted revenue that has not yet been recognized.

Snowflake reported approximately $9.004 billion of RPO as of July 31, 2026, up from $6.932 billion a year earlier.

Why it matters

RPO gives investors a view of contracted demand that sits ahead of recognized revenue. For a consumption-based platform, however, the timing of that conversion can be less mechanical than in a ratable subscription model.

Snowflake says customers can vary the timing of consumption and may in some cases roll unused capacity into future periods when purchasing additional capacity at renewal.

Investor caution

RPO is not the same as revenue, bookings, cash collections, or a guaranteed near-term conversion schedule. Snowflake explicitly notes that revenue timing depends on future consumption and that historical consumption patterns may not predict future results.

Source:

Part of the Data Cloud Consumption Economics

Connect realized platform consumption, enterprise customer expansion, contracted demand, revenue mix, and gross-margin economics for consumption-based data-cloud platforms.

How the model fits together
  • Consumption, revenue mix, and delivery economics: Product revenue is recognized from actual platform consumption rather than contract duration. Product revenue mix separates that core consumption revenue from professional services, while product gross profit and margin show the direct economics of delivering the platform and professional-services margin remains economically distinct.
  • Existing-customer expansion and enterprise penetration: Net revenue retention tracks product-revenue change within a defined existing capacity-contract cohort, while million-dollar customer counts and Forbes Global 2000 penetration show how broadly the platform is scaling into large enterprise relationships. These measures use issuer-specific customer definitions and are not interchangeable.
  • Contracted demand and revenue conversion: Remaining performance obligations measure contracted revenue not yet recognized, while RPO growth, expected next-12-month recognition, and capacity-contract remaining life add growth and duration context. In a consumption model, these measures do not form a fixed revenue schedule because actual recognition depends on future customer usage.

See It in Company Research

These companies are examples of how the concept is reported or discussed in public filings. Definitions can differ by issuer; these links open company research rather than a normalized metric comparison.

Continue Research

Continue from the concept into the Grizzly Bulls research surface that best matches the next question. These links are research continuations, not recommendations or required steps.

Compare stocks

Compare cloud software stocks

Continue into stock comparison for consumption growth, customer expansion, contracted demand, revenue mix, and gross-margin economics.

Continue research

Explore more topics in the Financial Research Encyclopedia.