TL;DR (July 2026): In under six months, every major pure-play usage-billing specialist got bought: Stripe acquired Metronome (reported ~$1B), Salesforce is acquiring m3ter, and Adyen's $335M acquisition of Orb - announced in June - is guided to close around July 1. The standalone metering-and-billing category effectively no longer exists; what exists now is billing capability owned by a payment processor (Stripe, Adyen), billing capability owned by a CRM (Salesforce), open-source independents (Lago the most visible), and the build-on-your-own-meter path. That changes the buying question from "which billing platform is best?" to "whose roadmap do I want my revenue infrastructure on - and how expensive is my exit?" This piece is the decision matrix: who should pick what now, and the four questions to ask any vendor before you sign in the consolidated era.
We covered each deal as news: Stripe buying Metronome, Adyen buying Orb for $335M, and Salesforce taking m3ter as the third metering acquisition. This is the piece those three were building toward - because with the Orb deal closing, the question readers keep asking is no longer "what happened?" but "what do I pick now?"
The board after the buyouts
| Platform | Now owned by | What that means in practice |
|---|---|---|
| Metronome | Stripe (~$1B, early 2026) | Real-time metering and enterprise contracts folding into Stripe Billing; deepest value if you already process on Stripe |
| Orb | Adyen ($335M, closing ~Jul 1) | Usage billing attached to an enterprise payment processor; strongest for Adyen-committed merchants |
| m3ter | Salesforce | Metering pulled toward RevOps - pricing, quoting, and billing living next to the CRM |
| Lago | Independent (open source) | The most visible processor-neutral survivor; self-hostable, positioning hard on neutrality |
| Chargebee, Zuora, Recurly | Independent (subscription-first suites) | Not metering-native pure-plays; usage support keeps improving but subscriptions remain the core |
| Your own meter | You | Usage events in your own store, billing computed from projections - maximum control, most engineering |
Why processor ownership actually matters (and when it does not)
The consolidation is not automatically bad news. Stripe and Adyen money makes these products more durable, better staffed, and less likely to disappear than any Series-B pure-play. If you are all-in on one processor, the acquisition is mostly upside: tighter native integration, one vendor, one contract, invoicing and payments finally speaking the same schema.
The cost is optionality, and it shows up in three specific places:
- Roadmap gravity. A billing product owned by a payment processor will, over time, work best with that processor. Features that help you route payments elsewhere - or negotiate processing fees down - are nobody's OKR anymore. The 0.7%-of-revenue billing fee math gets harder to escape when the meter and the money move together.
- Multi-processor strategies get awkward. Plenty of companies deliberately split volume across processors for redundancy and leverage. Metering vendors used to be neutral ground; now your usage data - the most sensitive commercial dataset you have, effectively your price book and your customers' consumption - sits with a party to those negotiations.
- Acquisitions reprice contracts eventually. Not on day one - migrations are always "seamless" in the announcement - but pricing, packaging, and minimums tend to drift toward the acquirer's enterprise motion at renewal time.
The decision matrix
| Your situation | Reasonable default (July 2026) | Why |
|---|---|---|
| All-in on Stripe for payments, want usage billing with least glue | Stripe Billing + the Metronome capabilities | The integration you would have built by hand is now the vendor's own roadmap |
| Enterprise merchant on Adyen | Orb under Adyen | Same logic on the Adyen side; watch the close and the first post-close pricing communication |
| Salesforce-centric revenue ops (CPQ, complex quoting) | m3ter within Salesforce | Metering next to the quote-to-cash motion you already run |
| Need processor neutrality, multi-processor, or data-residency control | Lago (hosted or self-hosted) | The remaining credible pure-play that is structurally unable to be captured by a processor - it is open source |
| Subscription-first product adding a usage component | Chargebee / Recurly / Zuora tier | If usage is a line item rather than the business model, a metering pure-play is overkill |
| AI product with per-token economics, custom pricing experiments, or agent workloads | Own meter + billing projection | Per-model, per-task, per-customer attribution is the product requirement; a real metering store feeding whichever biller you keep |
That last row is the one this site cares most about, and not only for house reasons: the acquisition wave is strongest evidence yet that the meter and the biller are separable layers. Stripe did not pay a reported billion dollars for invoice templates - it paid for the real-time metering layer. If the giants think the meter is the strategic asset, the conclusion for a buyer is to own your meter, or at minimum own your usage events, and treat the billing vendor as a swappable projection on top. We walked through that architecture in the meter-to-invoice kata and the UsageBox vs Stripe Billing vs Metronome comparison.
Four questions to ask any billing vendor now
- What is my exit path, concretely? Can you export raw usage events (not just invoices) in a documented format, continuously? If leaving requires re-instrumenting your product, you are not a customer, you are collateral.
- Is your pricing coupled to payment volume? Percent-of-revenue billing fees plus processing fees compound quietly. Get the all-in take rate - billing, metering, processing - as one number.
- What survives your acquisition? It is no longer a rude question; it is the base case. Contractual protections - price locks at renewal, data-export guarantees, notice periods - are worth more than roadmap promises.
- Where do my usage events live, and who can see them? Consumption data is your price book. If the party holding it also sits across the table in a processing negotiation, know that going in.
The honest take
Nobody should panic-migrate off Metronome or Orb - acquisition-day migrations are how you turn someone else's strategic decision into your own outage. The products will likely get better before they get captive, and if you live on the acquirer's processor anyway, you may be the winner here. But the era of assuming your metering vendor is a neutral utility ended this spring, in three press releases. The durable posture is the same one that survives model price changes, gateway changes, and every other vendor event we cover: own your usage data at write time. If every meterable event lands in a store you control, with attribution, then Stripe buying your biller - or your biller doubling its price - is a projection change and a quarter of glue work, not a re-instrumentation of your product. Billing vendors are temporary. The meter is permanent.