SQL-Based Billable Metrics

Fulfill & Bill Consume & Meter High-signal capability Updated July 2026

SQL-Based Billable Metrics — Defines billable metrics as SQL over the event stream — count of distinct users, sum of compute-seconds, max concurrent sessions — instead of hard-coded aggregations. Mediated events are its input, and the rating engine prices whatever the query returns.

Where it sits in the lifecycle

SQL-Based Billable Metrics lives in the Consume & Meter phase of Fulfill & Bill — the stage where you activate what was sold, meter what's used, bill it right. In the corpus tool index this phase maps to the Meteringcategory.

What strong looks like

The critical requirements that test this capability in UsagePricing's Usage-based billing & metering rubric — scored tool profiles link from the list below.

Tools that support it

CORPUS ADOPTION — TRACKED COMPANIES RUNNING EACH TOOL dbt 26 Snowflake 23 Orb 8 Metronome 5
Companies whose monetization signals name each tool, of the sql-based billable metrics supporters — from public job posts, blogs, and filings.
  • dbt Core 26 in corpus The common pattern — meters defined as tested dbt models over raw usage events.
  • Orb Core 8 in corpus Metrics defined in SQL over ingested events.
  • Cube (semantic layer) Core Defines the governed usage metric; rating and invoicing happen in downstream billing systems.
  • Snowflake Supported 23 in corpus Metric definitions typically managed with dbt on top.
  • Metronome Supported 5 in corpus
  • Zenskar Supported Billable metrics definable in SQL over ingested data — the flexibility centerpiece

Related modules in Consume & Meter

Back to the capability map