Billing Infrastructure Pricing: Examples & Companies

What is it

Billing Infrastructure Pricing is pricing for usage-billing and metering platforms — the vendors that meter, rate, and invoice usage for other companies. It is the most self-referential corner of the corpus: Metronome, Orb, Lago, m3ter, OpenMeter, and Togai sell the pipeline that powers everyone else’s usage-based pricing, and they price themselves on the events and money flowing through that pipeline. Puzzle joins from the adjacent billing-operations side, automating the books those invoices land in.

The category’s defining irony is opacity: the companies whose product is publishing usage-based prices publish almost none of their own. m3ter describes a four-step custom quote with no dollar amounts; Metronome shows a free starter and a “talk to an expert” tier; Lago’s managed product is quote-only; Orb deleted the $1,750/month Core price it briefly published. The pattern is strong enough that this corpus tracks it as a standing trend — the billing layer gates itself.

It is also the corpus’s most acquired category: Zuora took Togai in 2024, Kong took OpenMeter in September 2025, and Stripe closed on Metronome in January 2026 at a reported ~$1B.

How it works

The typical structure is platform fee + usage meters + (sometimes) a cut of money processed:

Worked example — the pricing model that wouldn’t sit still. OpenMeter is the category compressed into one arc: per-event pricing in 2023, flat $249–$349/month in 2024, back to usage-based ($249 plus events plus 0.4% of billing volume) by mid-2025 — at which point a customer invoicing $500,000/month owed ~$2,000 from the billing-volume line alone, five times what the event meter saw — and then, after Kong’s acquisition, no public prices at all. Every step is a different answer to the same question: is billing infrastructure’s value proportional to rows, to money, or to neither?

Worked example — procurement without a rate card. A buyer comparing Metronome, m3ter, and Lago gets three quotes built from the same two inputs — event volume and invoice-value distribution — but weighted differently. The practical move is to model your own billing cycle first, bring twelve months of both numbers, and ask each vendor to price the same growth scenario, since percentage-of-billings components compound with your revenue.

Companies using this

7 in-corpus companies serve the billing use case: the metering platforms (Lago, m3ter, Metronome, OpenMeter, Orb, Togai) and Puzzle on the accounting-automation side.

Patterns observed

The cluster prices on what it processes and hides the rates. Every metering vendor anchors to events and/or invoice value, and every one gates managed pricing behind sales — Togai routes enterprise to a custom quote, Orb withdrew its published price, and the free tiers (Metronome’s starter, Lago’s and OpenMeter’s open source) exist precisely so adoption can start without a quote. The drift from event counts toward money meters is category-wide: Orb’s billings metric and Togai’s invoice-value scaling both concede that for billing infrastructure, rows are a cost proxy and money is the value proxy.

Consolidation is the other constant: four exits in under three years (Togai→Zuora, OpenMeter→Kong, Metronome→Stripe, with the observability-adjacent Langfuse→ClickHouse closing the same season) — and in each case the acquired vendor’s public pricing got less public afterward.

Counterexamples & variants

Lago is the open-source counterexample to the opacity rule: its self-hosted edition is free with the full engine, making “run it yourself” the published price and the managed quote an ops-outsourcing premium — the same discipline open source imposes on vector-database pricing. Puzzle is the variant from the demand side: it doesn’t meter billing events at all, but gates a flat-tier accounting product on $20,000 of transaction volume — billing data as a segmentation line rather than a meter. And OpenMeter’s three-models-in-two-years arc is the standing caution against treating any single snapshot of this category’s pricing as settled.

What this means for buyers vs vendors

For buyers

Buy the meter definition, not the brand: an event-count quote, an invoice-count quote, and a billings-percentage quote price the same workload incomparably, so force all bidders onto your own twelve-month usage-and-invoice scenario. Negotiate the percentage components hardest — they scale with your success — and pin down data export and rate-card stability in writing, because most of this category changed owners recently and pricing changed with ownership. Start on the free tiers and open-source editions to validate your usage-event pipeline before any quote conversation.

For vendors

The category’s own history is the playbook’s fine print: pick your value proxy deliberately (rows vs money) because reversing it in public — as Orb and OpenMeter both did — burns trust with exactly the buyers who read pricing pages professionally. Keep the free on-ramp wide (OSS or starter tier) since your buyers prototype before they procure, and if you must quote rather than publish, publish the mechanic anyway: in a category bought by billing experts, an undisclosed percentage-of-billings line is the fastest way to lose a renewal.