Orb is now part of Adyen: what it means for usage-based billing buyers
Adyen closed its $335 million acquisition of Orb on 1 July 2026. What the deal changes for teams evaluating usage-based billing, and the questions to ask before signing.
On 11 June 2026 Adyen announced it was acquiring Orb, the usage-based billing platform, for $335 million in cash. The transaction closed on 1 July 2026. Orb now operates as a wholly owned subsidiary of Adyen under what both companies describe as an incubator model, and Orb's co-founders reinvested part of their proceeds into Adyen shares.
Six months earlier, Stripe had announced its acquisition of Metronome. Within one half-year the two most cited independent metering engines for AI and API companies became parts of payment processors. This post is about what that means if you are choosing usage-based billing software this year.
What Adyen bought, and why
Orb tracks real-time usage events and translates complex pricing contracts into invoices. It became a default for AI companies, API businesses and event-driven SaaS because its metering engine handles very high volumes and its API is developer-friendly.
Adyen's stated goal is to unify billing and payments infrastructure for its enterprise merchants. Usage-based pricing is growing fast, driven by AI products that bill per token, per call or per outcome, and processing those payments is more valuable when you also produce the invoice. Owning the billing layer moves Adyen up the stack.
What changes for a buyer
Nothing on day one. Orb keeps running, its customers keep their contracts, and the incubator model is designed to preserve the product. The changes show up over the next two years, and they are about incentives.
Processor neutrality. Orb worked alongside Stripe and other PSPs. It now belongs to a company whose revenue comes from processing payments. Ask how first-class non-Adyen processors will remain, and get it in writing.
Roadmap priorities. Features that help Adyen's enterprise merchants will come first. If your needs overlap with theirs, good. If you are a mid-market SaaS on a different processor, you are further from the centre than you were.
The scope gap did not close. Orb was and remains a metering and invoicing engine. Quoting, contracts, revenue recognition, CRM workflows and finance-facing controls were never in scope. The acquisition adds payments, not those.
Fewer independents. With Metronome inside Stripe and Orb inside Adyen, the list of usage-based billing platforms that do not also want to process your payments got shorter.
Questions to ask Orb now
- Which payment processors will have first-class support in 24 months, and is that contractual?
- Will pricing or packaging change for customers that do not process with Adyen?
- What is the plan for data residency and entity structure once Orb is integrated into Adyen's platform?
- How will support and account management change under the incubator model?
- If we need CPQ, revenue recognition or e-invoicing, which partner does Orb recommend, and who owns the integration?
The processor-neutral alternatives
If the answers make you hesitate, the field still has independent options. Hyperline covers real-time usage billing plus CPQ, invoicing, revenue recognition and e-invoicing in one platform, and works with Stripe, Adyen, GoCardless, Mollie and Airwallex. Lago is the open-source route for engineering-led teams. M3ter stays independent for enterprise commit-and-draw contracts.
We keep a full comparison in Top 8 alternatives to Orb for usage-based billing and a direct one in Hyperline vs Orb.
Sources
- Adyen, press release announcing the acquisition of Orb, 11 June 2026
- Adyen, completion of the Talon.One and Orb acquisitions, July 2026
- Orb, Orb is joining Adyen, June 2026
Where this fits in Hyperline
Frequently asked questions
Usually not on its own. Oracle CPQ brings enterprise-grade catalog and pricing-rule capabilities for organizations operating at significant scale, but implementation timelines and total cost of ownership are heavy for a mid-market SaaS company evaluating it from scratch, unless the business is already committed to the Oracle CX or ERP ecosystem.
For low-frequency usage add-ons, batch processing is often fine. For consumption that drives a meaningful share of revenue, especially high-frequency events like API calls or AI token usage, batch cycles limit visibility into what a customer currently owes and make anomalies harder to catch before they hit an invoice.
Each platform is scored against five consistent criteria: best fit (the buyer situation it actually suits), strongest part of quote-to-cash (where it genuinely leads), evidence reviewed (public pricing pages, product documentation, and G2 category listings), and watch-out (the limitation buyers run into first). Vendor claims that aren't verifiable against a public source are described qualitatively rather than repeated as fact.
No. Conga CPQ is built for configuration depth on multi-line, rule-heavy quotes, historically tied closely to Salesforce. Billing and usage metering live outside the product, so it typically functions as the quoting layer in front of a separate billing system rather than a complete quote-to-cash platform on its own.
Salesforce Revenue Cloud's strength is CPQ configurability inside the Salesforce ecosystem. Usage-based and consumption billing is a comparatively newer layer than its quoting core, and the platform generally requires meaningful Salesforce admin and implementation investment to configure well for hybrid pricing.
As SaaS companies grow, billing needs become more complex. HubSpot CPQ has limits: no quote-to-invoice automation, little pricing flexibility, basic reporting, manual revenue recognition, and no advanced subscription support.
LedgerUp is focused on the post-signature handoff: getting from a signed contract to a first invoice quickly. It does not include native CPQ, and its global e-invoicing and revenue recognition depth are limited compared to a full quote-to-cash platform, so teams that scale into hybrid pricing or larger, multi-country contracts typically re-evaluate.
Billing software converts an existing subscription or contract into invoices. Quote-to-cash software covers the full process before and after that: configuring a quote, getting it approved and signed, billing it correctly (including usage-based components), collecting payment, and recognizing revenue. A billing tool can be one part of a quote-to-cash stack; on its own, it isn't the whole thing.
