Usage Run-Rate

Usage Run-Rate: On-demand consumption revenue over the trailing three months, annualised. Also called Usage ARR.

Formula

Usage Run-Rate = On-demand Consumption Revenue in the three months ending at period end × 4

Computable definition

The canonical formula in the GASP formula grammar. The MCP server compiles it to SQL over the datasets listed below.

-window(sum(field.credit_amount where field.credit_event_type = 'consumption' and field.consumption_basis = 'on_demand'), 3 month) * 4

Unit: currency

Notes: Also called Usage ARR. The trailing three months of on-demand consumption, annualised. Committed consumption is already in ARR through the commitment and overage through the usage_realisation pair, so only on-demand consumption enters, and ARR + Usage Run-Rate counts nothing twice. GASP fixes the window at three months (MongoDB's 90 days, Confluent's three months) so two companies' figures compare.

Data requirements

Grain: On-demand consumption in the trailing 3 months ending at period end, annualised · Frequency: Monthly · Aggregation: window (month) · Staged: no · Main source: Billing.

Field	Dataset	Type
`consumption_basis`	credit_event	string
`credit_amount`	credit_event	decimal
`credit_event_type`	credit_event	string
`event_date`	credit_event	date

Example SQL (Postgres)

SELECT ((-(SELECT COALESCE(SUM(credit_amount), 0) FROM credit_event WHERE event_date >= ((:period_end + INTERVAL '1 day') - INTERVAL '3 month') AND event_date <= :period_end AND (credit_event_type = 'consumption' AND consumption_basis = 'on_demand'))) * 4) AS usage_run_rate

Access: recommended sensitivity tier confidential, access scope unscoped. Guidance your policy engine enforces.

From an agent: with the GASP MCP server, call lookup_metric({ "name": "Usage Run-Rate" }) or generate_query({ "metric": "Usage Run-Rate", "adapter": "<your adapter JSON>" }).

What It Tells You

The annual scale of the usage that no contract guarantees. Set beside ARR it shows how much of the business runs on commitments and how much on customers who could stop tomorrow.

Common Mistakes

Annualising all consumption and adding it to ARR, which counts commitments and overage twice
Changing the window from one period to the next
Comparing two companies' usage figures without checking their windows

Connected in the GASP relationship graph.

Upstream: what drives this

ARR component of ARR Including Usage Run-Rate (Core)

Downstream: what this drives

Usage Run-Rate measures Customer (Entity)
Usage Run-Rate measures Subscription (Entity)
ARR Including Usage Run-Rate measures Customer (Entity)
ARR Including Usage Run-Rate measures Subscription (Entity)

Sources

← Back to Finance metrics