For the complete documentation index, see llms.txt. This page is also available as Markdown.

Metronome

Support for Metronome is available in PeakCommerce and rapidly deepening toward fully native, bringing usage-based and consumption billing for metered products into the same journeys and catalog you already use for subscriptions.

Why it matters

Usage-based pricing — metered consumption, prepaid credits, and tiered rates — is hard to get right because it ties metering, rating, and invoicing together. Metronome specializes in that rating engine; PeakCommerce contributes the catalog, journeys, and customer-facing buying and self-service experience, so you can package and sell consumption products without building the billing math yourself.

What you can do with it

  • Usage metering — stream usage events to Metronome, which aggregates and rates them in real time.

  • Flexible consumption pricing — bill on metered usage, prepaid credits, tiered rates, and hybrid subscription-plus-usage models.

  • Accurate invoices — rated usage flows back so invoices reflect exactly what each customer consumed.

  • One catalog, one journey — sell usage-based plans through the same catalog and journey flows you use for subscriptions, alongside flat-rate and recurring charges.

How it fits / connect

PeakCommerce already understands metered and usage-type charges — usage drawdown, included quantities, and consumption against a billing period are first-class concepts. Metronome support extends that by mapping your usage-based products to Metronome billable metrics: as customers consume your product, usage events are sent to Metronome, rated against the customer's pricing, and reconciled onto their invoices.

Who and when

Reach for Metronome when your product is priced by consumption — API calls, compute, seats-by-usage, or credit drawdown — and you need real-time metering paired with self-serve commerce.

Gotchas

  • Usage-based billing depends on accurate event instrumentation; map each billable metric to the right product charge before going live.

  • Reconciliation is only as correct as the usage you emit — validate metering end-to-end in a test account first.

See also

Last updated

Was this helpful?