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.

The category’s defining tension is opacity. The companies whose product is publishing usage-based prices publish almost none of their own. m3ter describes a four-component custom quote — core platform fee, add-ons, support package, implementation services — with no dollar amounts attached. Metronome shows a free Starter and a “talk to an expert” tier. Lago’s managed Business and Enterprise editions are quote-only, and Orb routes every tier through “Contact Sales.” The pattern is strong enough that this corpus tracks it as a standing trend: the billing layer gates itself.

A newer cohort is pushing the opposite way. Flexprice, Hyperline, Schematic, and Sequence all publish real numbers on a page, and the broader suites — Chargebee, Maxio, and Stripe Billing — carry SMB-oriented transparency the pure-metering cluster abandoned as it moved upmarket. The result is a category split down the middle on the one thing it sells: whether the price is visible before the sales call. It is also the corpus’s most acquired category — and, as the pattern below shows, each acquisition made the target’s pricing less public.

How it works

The typical structure is platform fee + usage meters + (sometimes) a cut of money processed. The distinguishing variable across the category is the value proxy: some vendors meter the rows they ingest, some meter the money they invoice, and most eventually add a percentage of billing volume because that is what actually scales with a customer’s success.

Worked example — the pricing model that wouldn’t sit still. OpenMeter is the category compressed into one arc: per-event pricing in 2023, a flat $249–$349/month in 2024, then a usage-based Pro plan by mid-2025 ($249/month, 1M events included, $10 per additional million, and 0.4% of billing volume above $25,000), then no public price at all once Kong acquired it. The visualization above prices that 2025 Pro plan for a mid-stage AI startup and shows the punchline — the 0.4% money line dwarfs the per-event line five to one. Every step of the arc is a different answer to the same question: is billing infrastructure’s value proportional to rows, to money, or to neither? The company cycled through all three before the acquisition made the question moot.

Worked example — procurement without a rate card. A buyer comparing Metronome, m3ter, and Orb gets three quotes built from the same two inputs — event volume and invoice-value distribution — but weighted differently, and none of the three publishes a rate. The practical move is to model your own billing cycle first, bring twelve months of both numbers, and ask each vendor to price the identical growth scenario — because a percentage-of-billings line compounds directly with your revenue while a flat event meter does not. Deciding which of the two you’d rather be charged on is really a question about choosing the right usage metric.

Companies using this

17 corpus entries carry the billing use case. The standalone metering platforms are Lago, m3ter, Metronome, OpenMeter, Orb, and Togai — purpose-built to ingest events, rate them, and generate invoices. The broader billing suites — Chargebee, Maxio, and Stripe Billing — combine subscription management with usage metering and bring more SMB-oriented transparency. The usage-billing specialists — Flexprice, Hyperline, Schematic, Sequence, and Zenskar — occupy the gaps between the metering cluster and the big suites, usually with more published pricing. Kill Bill and self-hosted Lago represent the open-source options; Alguna rounds out the cohort from the quote-to-revenue angle (and notably does not meter usage — it sells unlimited event ingestion on flat tiers).

Patterns observed

The value proxy drifts from rows to money. The metering cluster’s two real cost drivers are compute at ingestion time and the financial liability of the invoices it raises — so early pricing anchored on event volume. But the drift toward money meters is category-wide, and it shows up in the language vendors use: Orb’s own FAQ names “billings” — the total value of all invoices issued through it — as a first-class pricing metric, and Togai’s platform fee explicitly follows “event volume + invoice value.” Rows are a cost proxy; money is the value proxy, and vendors keep migrating toward the latter because that is what actually tracks a customer’s success.

Free on-ramps power a land-and-expand motion. Nearly all of the pure-metering pricing is quote-only, yet nearly all of it also has a free door. Lago, OpenMeter, and Flexprice ship open-source self-hosted editions with the full engine; Metronome and Togai ship free managed Starter tiers (“no credit card,” unlimited users on Togai’s). The free tier exists precisely so adoption can start without a sales conversation, and the real price only appears once the metering pipeline is embedded deep enough that ripping it out means re-plumbing every rate card. That is the classic land-and-expand structure of infrastructure sold to engineers and priced to CFOs.

Transparency tracks the buyer, not the technology. The suites and specialists — Chargebee, Stripe Billing, Hyperline, Schematic — sell to audiences that expect a price on a page, and their published percentages (in the table above) become the buyer’s reference point when a quote-only sales team starts explaining its “value-based pricing.” Surface transparency in one corner of the category disciplines the opacity in the other: the gated vendor knows the buyer can already see what the same mechanic costs next door, which quietly caps how far a custom quote can stray.

Consolidation reshapes what pricing buyers see. Three exits in under three years — Togai to Zuora (2024), OpenMeter to Kong (September 2025), Metronome to Stripe (January 2026, ~$1B reported) — each left the target’s public pricing less public. OpenMeter’s page went from a full Free/Pro/Enterprise grid to a migration announcement with no dollar amounts. The mechanism is not coincidental: absorbed into a larger payment or API infrastructure player, the parent’s enterprise pricing culture dominates and transparent per-event tiers become friction in large-deal negotiations. Buyers should therefore model what happens to their contract if their vendor is acquired mid-term — a standalone startup’s commercial terms rarely survive intact into the acquirer’s framework.

Counterexamples & variants

Open source publishes the price by definition. Lago is the 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 self-hosted edition is not a stripped-down trial — it includes the complete metering and invoicing stack — so a buyer that can operate infrastructure never has to enter a sales conversation, and the free option puts a hard floor under what any managed-Lago quote can charge. Kill Bill occupies the same position at the older, more established end: Apache-2.0 core, self-hosted for free, with money made on modular add-ons (an ~$40/month AWS Marketplace software fee, cumulative “Aviate” tiers, and flat-annual support packages) — and, notably, never a percentage of your revenue. Together Lago and Kill Bill represent the two generations of open-source billing — the post-2020 usage-metering generation and the pre-2020 subscription-management generation — and both prove the opacity pattern is a choice managed-service vendors make, not a feature of the category. When the code is public, the price follows.

Some vendors reject the meter entirely. Alguna sits inside the billing use case but deliberately does not meter usage: it prices on flat SaaS tiers — a free Starter (up to 10 invoices/month), $699/month Growth, and a quoted Enterprise — with unlimited seats and unlimited event ingestion across every tier. That is a direct repudiation of the category’s core premise. Where Metronome, Orb, and OpenMeter treat ingested events as the thing to charge for, Alguna treats event volume as free and charges for the workflow layer (CPQ, contracts, revenue recognition) on top. Zenskar takes a related stance — three custom-quoted tiers priced “by scale/support,” explicitly not a percentage of your revenue — showing that even among quote-only vendors, “percentage of billings” is a design choice some deliberately refuse in order to win buyers wary of a fee that scales with their own success.

Payment infrastructure is a structural variant. Stripe Billing prices billing as a component of payment infrastructure rather than as a standalone metering product. Its 0.7% of billing volume (for recurring plus usage-based billing) and 0.4% per paid invoice (Invoicing Starter) layer on top of standard Stripe payment-processing fees, which is unusually transparent for a category dominated by opaque enterprise quotes — but the transparency comes with a catch: a buyer already on Stripe rails can add billing metering with no new vendor relationship, while a buyer not using Stripe for payments faces far higher switching costs than adopting a payment-agnostic platform like m3ter or Orb. The convenience and the lock-in are the same fact viewed from two directions.

And any snapshot of this category’s pricing can expire overnight. The OpenMeter arc above is the standing caution: every mechanic it tried produced a defensible answer, yet none stuck. The lesson is not that any one choice was wrong, but that the category has not converged on a single value proxy — so a vendor or buyer who assumes today’s pricing structure will still exist in three years is carrying real model risk.

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 — the decomposition above shows the money line dwarfing the row meter on identical usage. Force every bidder onto your own twelve-month usage-and-invoice scenario, negotiate the percentage components hardest because they compound with your success, and pin data export and rate-card stability in writing, since 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.

Segmentation matters as much as the sticker. The pure metering cluster (Metronome, Orb, m3ter, Togai) is the right choice when your billing model is deeply custom and you process tens of millions of events a month. The broader suites (Chargebee, Maxio, Stripe Billing) fit when you need subscription management, dunning, and invoicing alongside metering and can’t operate a bespoke pipeline. The usage-billing specialists (Flexprice, Hyperline, Sequence) often deliver faster time-to-value for mid-market teams that need more than a suite but lack the engineering to run a pure-metering platform — and they publish numbers, so you can price the deal before the call. Weight the open-source options (Lago, Kill Bill) whenever infrastructure ownership or cost control is the binding constraint: they hand you a credible walk-away number in every managed-vendor negotiation.

For vendors

The category’s own history is the fine print in the playbook: 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; every serious vendor in this cohort, from Metronome to Flexprice, has one. 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.

The transparency gradient is itself a positioning decision. The specialists carve niches the original metering cluster deprioritized — feature-flag and entitlement integration, revenue-ops reporting, quote-to-revenue workflow — and do it with public prices and self-serve tiers. That is the most accessible path for a buyer avoiding a full enterprise sales cycle, and it is a live threat to incumbents: it repeats the trajectory the metering cluster itself once rode, where a transparent mid-market entrant wins on accessibility and grows upmarket. For an incumbent now behind a “Contact Sales” wall, the open question is whether the deals opacity protects are worth the mid-market it cedes.

Finally, decide whether to meter at all as a deliberate stance, not a default — the refusals in the counterexamples above show “not a percentage of your revenue” is now a marketable feature. Whichever way you go, your most sophisticated buyers read the choice as positioning, so make it on purpose.

Explore this theme in the knowledge graph →