TL;DR: Orb is Adyen's. The $335 million acquisition closed on 1 July 2026 and Adyen is running it under an incubator model, so the product is intact and the team is intact. It remains one of the best-designed usage-billing products available — the metric-definition experience in particular is genuinely better than its competitors'. The one line worth reading carefully is that multi-PSP support "continues initially".
This page previously reviewed Orb as an independent vendor. It is not one, and that fact now matters more to most evaluations than anything in the feature list.
What changed, and what did not
Adyen agreed to acquire Orb in June 2026 for $335 million in cash, alongside Talon.One, closing on 1 July. Orb became an indirect wholly-owned subsidiary, run under an incubator model that Adyen says is intended to preserve product momentum and operational continuity during the initial phase.
The stated logic is coherent: link billing signals to Adyen's identification layer, and use real-time payment data and risk scores to improve billing execution and transaction success. If you are already an Adyen merchant, this acquisition makes your stack better, not worse.
What did not change: the product, the team, or your contract. Nobody should migrate off Orb because of a press release.
The word to read carefully
Adyen's messaging says multi-PSP support continues initially.
That is not a removal and it is not a commitment. It is the amount of ambiguity a company puts in writing when the honest answer is "we have not decided". Six months earlier Stripe acquired Metronome and now describes it as "a Stripe product purpose-built for the most sophisticated usage-based billing scenarios", pointing at native Stripe payment integrations — which is where this pattern tends to go. Not a removal; a convergence, in which the well-supported path becomes the acquirer's rail.
If you process somewhere other than Adyen and intend to keep doing so, ask your account team what the roadmap commitment is and what notice you would get, and get it in writing. The quality of that answer is the answer.
What Orb is genuinely good at
Defining billable metrics. This is Orb's standout and it is a real advantage, not a UI preference. Being able to express a metric without writing YAML or a migration means pricing changes stop being an engineering ticket, which is the difference between running pricing experiments and talking about running them.
Pricing iteration velocity. Versions, pilots and adoption monitoring without waking up engineering. For a product-led business where pricing is a live variable rather than a settled decision, that is the whole value proposition.
Sophisticated pricing models. Tiers, commitments, hybrid shapes and multi-attribute rating are well covered. It sits in the same class as Metronome on capability.
Documentation and onboarding. The quickstart is unusually good for this category, where documentation quality varies wildly.
What to weigh against it
Event schema discipline is on you. Loose event schemas produce a noisy rating pipeline. This is true of every metering system and is not an Orb defect, but it is the work that gets left out of the estimate.
Entitlement enforcement is usually still in your app. Knowing a customer is over their limit and stopping them at the moment of the request are different problems, and the second one lives in your code path regardless of what your billing vendor knows.
Ownership is now part of the purchase. Not a product criticism — a fact that belongs on the evaluation matrix. Orb means Adyen, the same way Metronome means Stripe and m3ter means Salesforce.
Should you pick it?
Yes, comfortably, if you process on Adyen or are indifferent to your processor. You get a strong product with a well-funded owner and tighter payments integration ahead of you.
Ask hard questions first if you deliberately run multiple processors for redundancy or negotiating leverage. Your consumption data is effectively your price book, and it now sits with a party to those negotiations.
Look at licence-protected options if your objection is structural rather than commercial. Lago and Flexprice are AGPL, OpenMeter is Apache 2.0 — and a licence is the only form of independence an acquisition cannot reach.
Where UsageBox fits, stated accurately
It is not an Orb competitor and this page will not pretend otherwise.
UsageBox is a metering layer — idempotent ingest, a documented dedupe window, per-account key scoping, late-event handling, monthly rollups. It has no rating engine, no invoicing, no credits, no entitlements and no customer portal. Orb does the things UsageBox does not do. The only overlap is the narrow case where you want the counting to sit outside a payment company and you already have a biller you are keeping.