Metronome vs Orb: A SaaS Usage Billing Guide 2026

Key Takeaways

• Metronome and Orb are both still sold under those names. Each one now sits inside a payments company, Stripe for Metronome and Adyen for Orb.

• On Metronome, the public page prints two consumption rates and leaves the upper tier quote-based. On Orb, Core, Advanced, and Enterprise are all quote-based.

• The contract split is commits, credits, and rate cards described on Metronome's pricing page, against invoicing, threshold bills, and customer hierarchy described on Orb's pricing page.

• A single vendor time-saved claim and a logo row are not a forecast of your invoice accuracy.

• After either purchase, someone still has to tie rated usage to the ledger. That review is a separate job from picking the rating engine.

• Neither page offers a self-hosted edition. A team that must run billing inside its own cloud is outside this short list.

Two payments companies now own this short list

Usage-based billing charges a customer from measured consumption, alone or mixed with a seat fee or a platform fee, rather than from a flat subscription alone. The 2026 buying fact is ownership. You are no longer choosing between two independent billing startups.

TL;DR: pick Metronome when Stripe is already your collector and you want the two published consumption rates plus the contract objects on its pricing page. Pick Orb when you want invoicing, dunning, and customer hierarchy described on the price card and you can accept a quote. Neither choice removes the month-end review between the usage file and the ledger.

Metronome was not renamed and was not discontinued. Scott Woody's post says the Stripe acquisition is complete, Stripe close: January 13, 2026 according to Metronome (2026). The product is still offered under the Metronome name, and the pricing page carries a banner that Metronome is now part of Stripe.

Orb was not renamed and was not discontinued. On June 11, 2026 Adyen agreed to buy Orb for $335 million in cash, said Orb was founded in 2021, said a $25 million Series B closed in 2024, said total funding was $44 million, and said the first phase would keep an incubator model with multi-processor support, Deal value: $335 million according to Adyen (2026). The close then happened on the date that release had expected, Orb close: July 1, 2026 according to Adyen (2026).

That ownership change is the disqualifier hiding in a logo comparison. A contract signed this quarter is a contract with Stripe's subsidiary or Adyen's subsidiary. Ask who the vendor of record will be, which roadmap absorbs the product, and whether a second payment processor is still allowed after the first integration phase. Adyen's June release said multi-processor support continues in that first phase. It also said the later intent is one infrastructure experience across billing and payments. Those are different time horizons. Get the horizon into the order form.

If your real fork is Stripe's own billing suite against another billing suite, settle that beside this page. Stripe Billing versus Maxio and Recurly versus Stripe Billing cover that neighboring choice. A wider map of metering tools sits in the roundup of usage metering software for B2B SaaS. This page stays on Metronome and Orb.

Who this is for

This comparison is for a finance lead or a product lead at a software company that already prices on usage, seats, or a hybrid, and is close to signing one of these two platforms. You want to know what is public, what is a sales quote, and which contract objects exist on the current pricing page. You are past the "what is usage billing" stage.

Red flags: you need a complete public dollar subscription with no sales conversation; you need the rating engine to run in your own cloud; you are shopping for a general ledger rather than a usage rating and invoicing layer.

A company still inventing its first meter, with one flat plan and a handful of invoices a month, will feel both products as more system than the problem requires. A company whose pain is a disputed overage, a restated commit, or a marketplace invoice that does not match the direct invoice is in the right room. The rest of this guide separates what each vendor page states from the judgment we apply to a buying meeting.

How we evaluated Metronome and Orb

We weighted six buying questions that a finance or product lead actually argues about in the meeting. The weights sum to 100%. They are our priorities for this reader. They are not product scores, not a lab result, and not a ranking published by either vendor. Factual claims below come from pages opened for this guide. The judgment of who should sign is marked as analysis.

Contract and commit fit is 22% because a usage-priced company usually loses cash on the special term, not on the list rate. Metering and late events are 18% because a retry that double-counts, or a definition you cannot recompute, becomes a credit memo. Invoice and collection path and price-change control are 16% each, because a rating engine that cannot issue an invoice just moves the work, and a price change that needs an engineering project will not happen. Finance-system handoff and commercial transparency are 14% each. They matter, and they are rarely the reason the first implementation fails.

Outside grades are context, and they are old relative to the closes. Analyst score: 45 according to MGI Research (2025). That December 4, 2025 note also scored Stripe at 57.3 with an A grade, said Metronome had raised $128 million including a $50 million Series C closed in February of 2025, and said the purchase terms were undisclosed. MGI, writing before the close, called Metronome a metering tool attached to Stripe Billing and said the deal did not by itself fill every gap in complex billing. Treat 45 and the B- grade on that note as a 2025 analyst view. The pricing page live for this guide lists contracts, hybrid pricing, alerts, and invoicing integrations, so do not stop at the 2025 label. Do ask Stripe how Metronome and Stripe Billing overlap, because that open question is why the weight on invoice path is as high as it is.

Pricing checked against the public pages

Quote-based means the vendor does not print a dollar figure you can put in a model without a sales conversation. On Orb, that is the entire price card. On Metronome, the lower card prints two consumption rates and the upper card does not. The lower card is labeled Startup. The upper card says it includes everything in Starter. The page does not print a second rate list under the Starter spelling. Read those as one lower tier with two labels, and confirm the spelling in the order form so procurement does not think it bought a different package.

The headline on Metronome's pricing page invites a team to start. The page does not print a zero-dollar plan, a trial length, or an included event allowance. Picture a month with $2,000,000 of customer invoices and 50,000,000 usage events, each stamped with a transaction_id. The Startup tier on Metronome bills that invoice total at 0.8% and those events at $0.04 per 1,000, which is $16,000 plus $2,000, or $18,000, equal to 0.9% of the invoices, Volume rate: 0.8% according to Metronome (2026). No platform-fee dollar amount is printed on that page, Orb publishes no matching rate, and this paragraph is an illustration of the printed rates, not a quote and not a customer result. Your order form's definition of billing volume can move the $16,000. If credits, tax, or unpaid invoices are inside or outside that base, the 0.8% applies to a different number than the cash you collected.

Pricing checked October 10, 2026.

The math table uses only the two rates in the cited paragraph. It assumes the $2,000,000 is the billing-volume base. It ignores a minimum commitment, a separate platform fee, and any pass-through payment cost. An Orb column is absent because a blank rate would be a guess. In analysis, a team that needs a number in the budget this week can model the Metronome variable piece and must leave the Orb piece as a placeholder until the quote arrives. A team that will not accept a percentage of billings plus a per-event charge should not treat those two rates as a curiosity. They are the commercial shape of the lower tier.

On the Custom card, Metronome lists invoicing integrations with Salesforce, NetSuite, and the AWS, Azure, and GCP marketplaces, plus warehouse and BI exports, a dedicated account manager, and enhanced service levels. Those items are not printed as included on the Startup card. If your deal needs the marketplace invoice, you are in a quote even if the variable rates were the reason you opened the page.

The split that shows up in a contract review

Read the matrix as "listed on the pricing page we opened," not as a scored feature contest. Where a cell says a capability is listed, the page describes it. Where a cell says it is not listed, the page did not put it on the card. Absence from a marketing page is a question for the order form, not proof that the feature cannot be sold.

On Metronome, the features block under the cards describes SQL queries on raw events without a requirement to pre-aggregate, streaming metrics for fast alerts, centralized rate cards, commits, credit models, per-customer discounts and amendments, and price updates that can take effect now, later, or on a past date. The page also describes embeddable dashboards, webhooks, and an API. Native Stripe integration is on the Startup card. Treat the commits and credits language as a reason to bring a real contract into the pilot: a prepaid commit, an overage rate, and an amendment date. Do not assume a parent account can be invoiced for child accounts. That object is not on the page.

Orb publishes no dollar rate, prices from billings and events, adds an unpublished platform fee on the Advanced and Enterprise plans, states an ingest example of 250,000+ events per second, and reports that Stytch cut bill-processing time by 75%, Ingest example: 250,000+ events/second according to Orb (2026). That page also says ingestion has idempotency guarantees, puts Orb Invoicing on every plan, and defines billings as the total value of invoices you issue through Orb, including fixed fees, usage fees, taxes, and other amounts on the invoice. An event, on that same page, is a raw record with an identifier, a timestamp, and optional metadata. Every plan lists finance and tax connections, including QuickBooks, Bill.com, and Stripe for invoicing, and Avalara, Anrok, Numeral, Sphere, Stripe Tax, and TaxJar for tax. Advanced and Enterprise add NetSuite, Salesforce, customer hierarchy, and warehouse sync, with Snowflake and Redshift named among warehouse destinations. The page describes custom SQL metrics, threshold invoices that fire at a dollar amount, and tools to migrate subscriptions onto a new price version. The 75% figure is Orb's claim about one named company. It is not a benchmark for your close.

Adyen's description of Orb, in the June release cited above, is an engine that keeps the full event stream and separates ingestion from invoicing, which is the basis for recomputing a price later. Adyen called that backtesting. Use the vendor's word in the pilot script. Ask for a worked change on last quarter's events, and ask who is allowed to press it, finance or engineering. Metronome's page says price updates can be retroactive. Ask the same question there, with your own event sample, and compare the answer. That demo is worth more than a feature adjective.

Our analysis of the matrix: a company whose hard problem is a negotiated commit, a credit balance, and a Stripe charge should start on Metronome and confirm the Custom tier only if marketplace or NetSuite invoicing is in scope. A company whose hard problem is issuing the invoice, dunning it, and rolling child accounts into a parent invoice should start on Orb and expect the hierarchy and the NetSuite path to sit on a higher quote. A company that needs both a rich commit model and parent-child invoicing should not let a single demo imply both are on the cheap tier. Make each object a line in the order form.

A proposed configuration from US Tech Automations sits beside either platform rather than inside this matrix. The trigger is a nightly invoice export or a usage file from Metronome or Orb. The action matches the customer identifier and the billing period, compares the rated total with the exported total, and opens one review item when they differ. The output is an exception list for a named reviewer. Prerequisites are an API or file export, a stable customer identifier, and a person who approves any credit or rebill. The design stores the source file key so a retry does not post the same difference twice. This is a configurable workflow with a human review point, not a live deployment and not a measured savings figure.

Which buyer each product fits

PitchBook's public profile lists Metronome as a Stripe subsidiary acquired on January 13, 2026, founded in 2019, with a 2025 headcount of 164, Listed headcount: 164 according to PitchBook (2025). Use 164 as a 2025 staffing figure, not as a census for this month. Primary evidence for the product itself is the pricing page and the January 13, 2026 completion post linked above.

The best fit for Metronome is a software company that already collects on Stripe, sells a mix of self-serve and negotiated contracts, and wants commits, credits, and rate cards in the billing system. The lower tier is the one a finance lead can model with the 0.8% and $0.04 rates. The limitation is commercial and structural. The Custom price is quote-based, the card label disagrees with itself, marketplace and ledger invoicing are on that upper card, and the owner can fold the product into Stripe Billing on a timetable you do not control. There is no self-hosted offer on the pages reviewed, and there is no public throughput number to set next to Orb's ingest example. Implementation starts by defining the event before you send volume. Metronome's event guide requires a transaction_id, a customer_id, a timestamp, and an event_type, with property values sent as strings. Put the stream on a queue, retry a failed delivery, and create the customer in your own system first so a late event can still attach. Have finance sign the billable-metric definition before production traffic, because a later rename of a property is how invoices drift.

The best fit for Orb is a software company that wants the billing product to create the invoice, deliver it, and run dunning, and that may need a parent invoice for child accounts. Adyen's June release names Vercel, Glean, Replit, and Supabase among clients. That is the acquirer's list, not a set of results we rechecked. The limitation is price transparency and tier placement. Every plan is quote-based, the platform fee on Advanced and Enterprise has no printed amount, and hierarchy, NetSuite, Salesforce, and warehouse sync are on the higher cards. The first phase under Adyen is an incubator, which is good for continuity and incomplete as a five-year architecture promise. Implementation is an event stream plus a metric query. The pricing page says you can send events by API or from S3, define SQL metrics, fire webhook alerts, and rely on idempotency so a retry does not invent usage. Confirm in the pilot that a finance user can schedule a price migration without a ticket to engineering, because the page describes the tool and does not publish a permission matrix.

Our analysis: choose Metronome when the scary artifact in the deal room is the enterprise order form and Stripe is an acceptable collector. Choose Orb when the scary artifact is the invoice packet, the dunning cycle, or a family of accounts. Choose neither when you need a self-hosted engine, a fully public all-in price, or a ledger. If both artifacts are scary, run one paid pilot on the object that is harder to change later, which is usually the commit and the amendment history, and keep the invoice layout as a scripted test on the same data.

The review work that remains after you pick

Buying the rating engine does not close the books. A usage file, a contract amendment, and a threshold alert still have to become one number a person will defend. The tie-out steps are the point of the recipe for reconciling usage-based overage and the guide to automating SaaS usage reporting. Those jobs remain whether the rating system is Metronome or Orb.

In a second configurable design, US Tech Automations watches a threshold alert or a contract-amendment file, opens one review item for that customer and period, and keeps a second delivery of the same file from creating a second item. Zapier, Make, and n8n can support run history, retries, error branches, and audit evidence when someone configures them. The buyer still has to design and own observability, idempotency, escalation, access control, and maintenance. A US Tech Automations design can pre-set the review gate and the replay rule once the export path and the approver list exist, and a person still signs off before a credit or a rebill is issued. Prerequisites are the same export or API feed, a stable customer key, and a named reviewer. Nothing in that design is a claim that a customer is live on it today.

The fair contrast with a do-it-yourself scenario is ownership of the failure, not a slogan about simplicity. A well-built scenario in Zapier, Make, or n8n can show that a run happened, can try again, and can branch when a file is empty. It will not decide, by itself, which difference is material, who may approve a credit over a given size, or how a replay avoids a double credit. Those rules are the product of the design. If your team already has an owner for that scenario and the volume is modest, adding another system duplicates the path. If the owner is "whoever has the login," the next price change becomes a silent edit.

Common mistakes before signature

• Treating the two logos as still-independent companies. The vendor of record is now a Stripe subsidiary or an Adyen subsidiary.

• Dropping an old blog's dollar estimate for Orb into a forecast. The live pricing page is quote-based. An estimate from memory is not a price.

• Calling Metronome "metering only" because a 2025 note or a competitor's comparison said so. The current pricing page lists contracts, hybrid plans, alerts, dashboards, and invoicing paths. Verify the path you need against the tier.

• Missing the Startup versus Starter wording. Procurement should bind the order form to the card you modeled.

• Sending production events before finance has signed the metric, then discovering a retry or a property change moved the invoice.

• Assuming customer hierarchy, NetSuite, or a cloud marketplace invoice is included because a demo showed it. On these pages those items sit on the upper cards.

• Expecting either product to replace the human check between rated usage and the ledger.

Glossary

• Usage-based billing. A charge computed from measured consumption, sometimes combined with a seat or a fixed fee.

• Billings. On Orb's pricing page, the total value of the invoices you issue through Orb, including fixed fees, usage fees, taxes, and other amounts. Confirm whether Metronome's billing-volume base matches that definition before you reuse a model.

• Event. A single usage record. On Orb's page it carries an identifier, a timestamp, and optional metadata. On Metronome's event guide it carries a transaction_id, a customer_id, a timestamp, an event_type, and optional properties.

• Billable metric. The query that turns events into a quantity on an invoice line. Both pricing pages describe SQL-style metrics.

• Commit. A contracted spend amount. Metronome's pricing page lists commits and credits beside rate cards. Bring your own contract before you assume the shape.

• Threshold billing. On Orb's page, an invoice that fires when a customer reaches a set dollar amount, used to limit unpaid exposure.

• Platform fee. A charge Orb says is included on Advanced and Enterprise, with no dollar amount printed. Metronome's pricing page does not print a platform-fee amount either.

• Hybrid pricing. Usage plus a seat fee or a fixed fee on the same plan. Both pricing pages say they support that mix.

Questions to settle before you sign

Is Metronome still an independent company?

No. Stripe completed the acquisition and the product is still sold under the Metronome name, so the contract should name the vendor of record and the support path you will actually call.

Did Adyen rename Orb?

No. Orb kept its name after the close, and Adyen described an incubator model for the first phase, which means you should ask what changes in phase two before you treat today's packaging as permanent.

What can finance type into a budget before a sales call?

Only the two consumption rates on the lower Metronome card, as shown in the pricing table. Every Orb plan is quote-based, and the upper Metronome card is quote-based. Anything else in a spreadsheet is a placeholder.

Does either product include invoicing?

Yes for Orb, which puts Orb Invoicing on every plan on its pricing page, including collection, dunning, and delivery. Metronome lists native Stripe integration on the lower card and lists Salesforce, NetSuite, and cloud marketplace invoicing on the Custom card.

Who should choose Metronome?

A team that already collects on Stripe, needs the commit and rate-card objects described on the pricing page, and wants the published consumption rates in the model. Confirm marketplace or ledger invoicing as a Custom-tier question if you need them.

Who should choose Orb?

A team that wants invoices, dunning, and customer hierarchy handled in the billing product, and that can wait for a quote. Ask for the platform fee in writing, and ask which payment processors remain allowed after the first Adyen integration phase.

Should a team add software above the billing platform?

No, not in every case. When NOT to use US Tech Automations, keep the billing vendor alone if all you need is its invoice screen and one processor, if usage is still a monthly spreadsheet with a checker, or if a maintained Make or n8n flow already has an owner and a review step.

The choice, then the work around it

Metronome fits the Stripe-centered company that will model 0.8% of billing volume and $0.04 per 1,000 events and then test commits, credits, and amendments on a real contract. Orb fits the company that will trade a public rate for invoicing, threshold bills, versioned price changes, and parent-child billing on the higher plans. Both are owned by payments companies as of the 2026 closes cited above. Both leave a quote-shaped hole in a total-cost model. Both still need a person when the rated file and the ledger disagree.

The short list ends when the order form names the tier, the processors, the invoice objects, and the owner. The close still needs a checked handoff from rated usage to the ledger. For that handoff, see how US Tech Automations configures this.