Three usage-billing vendors win the buy decision — and Stripe Billing has pulled ahead
When an AI company buys (rather than builds) its usage-billing layer, the choice has concentrated on three vendors: Orb, Stripe Billing, and Metronome. Across the corpus's named-vendor companies, Orb appears in 5, Stripe Billing in 5, and Metronome in 3 — 13 of roughly 16 — with OpenMeter, Lago, RevenueCat and cloud marketplaces in the tail.
What's happening — and why
What's happening: the AI usage-billing market looks fragmented from the outside, but the actual buy decisions cluster on a three-name shortlist. Orb and Stripe Billing each appear in five corpus stacks; Metronome in three. Everything else is a one-off.
Why: each of the three wins a different lane. Orb wins where the buyer already built its own meter and wants a billing-native system of record on top. Stripe Billing wins where the company already runs Stripe for payments and wants the meter and biller in one place. Metronome wins at frontier-lab and large-infra scale, where it sits inside a broader quote-to-cash stack alongside Salesforce and NetSuite.
How it works
Evidence over time
27 supporting · 8 counter — hover or tap a point for detail, click to jump to the row.
Evidence
| Company | Date | What happened |
|---|---|---|
| Baseten | Feb 2026 | Orb named in a billing-eng req: build and evolve our billing platform and integrations (including Orb). In-house meter feeds Orb. |
| Pinecone | Jun 2026 | Adopted Orb as system of record for all usage and billing data when launching serverless, replacing a homegrown billing engine. |
| Vercel | Jun 2026 | Orb is the billing layer on top of Vercels real-time usage pipeline; Stripe handles payments. |
| Relevance AI | Jun 2026 | Orb (billing) plus Stripe (payments) over an in-house billing & metering core. |
| Replit AI | Jun 2026 | Orb named as the metering vendor alongside Stripe (payments) and a usage/credit metering layer. |
| Chroma | Jun 2026 | Strongest exemplar: in a billing-engineering blog Chroma says 'Rather than building and maintaining this ourselves, we partner with Orb to handle these aspects' (invoicing, plans, credits) and feeds Orb from its own in-house CDC/WAL meter — the buy-the-bill, build-the-meter split stated outright. Source: trychroma.com/engineering/billing. |
| fal.ai | Jun 2026 | A Payments-team job req states 'integrate with Orb for usage metering and Stripe for payments and invoicing' — fal buys Orb as the meter+bill layer. Source: jobs.ashbyhq.com/fal-ai. |
| Fireworks AI | Jun 2026 | Orb named as the billing platform ('You will work hands-on with our billing platform (Orb, etc)') over an in-house BigQuery+dbt order-to-cash pipeline, with NetSuite as ERP. Source: job-boards.greenhouse.io/fireworksai. |
| Browserbase | May 2026 | Stripe Billing meters and bills hundreds of millions of browser-session-minutes a month; the company chose to buy rather than build. |
| Intercom | Jun 2026 | Stripe Billing in the stack alongside an in-house billing platform — buys the rail for the self-serve surface. |
| Langfuse | Jun 2026 | Stripe Billing/Checkout/Tax bought as the biller after migrating off homegrown billing; in-house ClickHouse meter feeds it. |
| Higgsfield | Jun 2026 | Stripe Payments + Stripe Billing as the consumption-billing rail. |
| Wispr Flow | Jun 2026 | Stripe Billing as the billing system of record alongside a ClickHouse/dbt data stack. |
| ElevenLabs | Jun 2026 | Buys its entire monetization stack on Stripe — even the meter behind its usage pricing runs on Stripe Billing ('A single engineer initially set up Stripe Billing ... Stripe's flexibility allowed us to seamlessly introduce usage-based pricing'), with Stripe Connect for marketplace payouts. Source: elevenlabs.io/blog/heres-how-elevenlabs-scaled-with-stripe. |
| Linear | Jun 2026 | 'Linear chose Stripe Billing, an automated solution for managing recurring revenue, paired with Stripe's Optimized Checkout Suite' — Stripe Billing + Checkout + Tax as the full self-serve rail. Source: stripe.com/customers/linear. |
| Anthropic | Jun 2026 | Metronome named for usage metering inside a QTC stack also using Salesforce, Stripe and Ironclad. |
| Together AI | Jun 2026 | Metronome (metering) with Stripe (payments), NetSuite (rev-rec) and Salesforce (CRM). |
| LiveKit | Jun 2026 | Metronome (metering) + Stripe (payments) + NetSuite, migrating rev-rec off legacy QuickBooks. |
| Replicate | Sep 2025 | Metronome's 5th stated corpus user and the clearest statement of why the real-time lane exists: "Metronome handles event metering and credit balances in real-time, so Replicate ensures that every customer is charged accurately the moment usage occurs." Stripe stays as payment processor only. Source: monetization_signals billing stack entry (Metronome case study). |
| Manus | Jun 2026 | Stripe Billing add: "Manus implemented Stripe Billing to manage its subscription-based revenue model," on top of Stripe's Optimized Checkout Suite (card, Apple Pay, Google Pay, Alipay, Link) and Stripe Invoicing for the rev-rec layer. Manus now charges in 31 currencies and over half its payment volume flows through Link — the whole monetization stack bought from one vendor. Source: monetization_signals stack entries (Stripe case study). |
| Heidi Health | Jun 2025 | Stripe Billing add, with an implementation-speed number the build side never publishes: "setting up Payments and the Optimised Checkout Suite, along with Billing and Invoicing, took the team just two to three days," where Billing "manages flat-fee subscription tiers and usage-based pricing models" — both halves of a hybrid model on the bought rail. Source: monetization_signals billing + payments stack entries. |
| invideo AI | Jun 2026 | Stripe Billing add with a hard recovery metric: "Stripe Billing optimisations such as Smart Retries improved Invideo's failed subscription renewal recovery rate from 23% to 30%." The buy-side case is dunning and recovery, not metering — a different reason to buy than Orb's or Metronome's. Source: monetization_signals billing stack entry. |
| tl;dv | Jan 2023 | Stripe Billing add, and the earliest-dated one: "using Stripe Billing, tl;dv designed a freemium, per-seat subscription model, which it was able to launch without slowing down product development" — Billing chosen as the packaging design surface, not just the invoicing rail. Source: monetization_signals billing stack entry (Stripe case study). |
| Leonardo.Ai | Jun 2024 | Stripe Billing add: "Stripe Billing really allows us to streamline our backend efficiency so we can focus on our core product," with Checkout described as "the company's bread and butter." Leonardo is also one of the 19 clean build-meter/buy-biller companies — its own credit meter, Stripe's biller. Source: monetization_signals billing + payments stack entries. |
| Bardeen | Jun 2026 | Stripe Billing add, disclosed the humblest possible way — a docs line telling customers to "cancel your subscription via the Stripe Billing Portal." Worth counting because it shows how much of the Stripe Billing lead is small self-serve AI apps that never wrote a case study. Source: monetization_signals billing stack entry. |
| Zuora | Jun 2026 | Fourth-lane observation, first recorded at this review: Zuora is named by 7 corpus companies and was absent from the 190-block read entirely. Anthropic's Finance Systems Engineer req lists it explicitly — "configure and extend the third-party platforms that run our financial operations including Zuora, Stripe, and Tesorio" — alongside Metronome for metering. Other users: canva (rev-rec, with NetSuite for B2B billing), claude-code, deepgram (candidate list), gitlab ("billing platforms such as Salesforce and Zuora"), yellow-ai, zendesk-ai. Every one is an incumbent or enterprise-vintage seller, none AI-native. Source: monetization_signals billing/rev-rec stack entries across those 7 companies. |
| Yellow.ai | Feb 2024 | The two lanes are complements, not rivals: "Yellow.ai was using another billing system (Zuora) to manage their existing subscription-based offerings," then bought Togai because "Togai's marketplace for quote-to-cash apps, with native bi-directional support for syncing with Zuora, enabled Yellow.ai to manage their metered billing needs." A usage meter bolted onto an incumbent subscription biller rather than replacing it. Source: monetization_signals billing stack entries (Togai case study). |
Counterexamples
- Trigger.dev · Jun 2026 — Tail vendor: runs OpenMeter (metering) and OpenMeter Entitlements for free-tier gating, with Stripe for payments — the only OpenMeter user in the corpus.
- Mistral AI · Jun 2026 — Tail vendor: runs Lago (open-source billing) with Stripe, SAP and Salesforce — the only Lago user among the labs.
- Milvus · Jun 2026 — No standalone billing vendor: cloud-marketplace billing (AWS/GCP/Azure) is the rail, sidestepping the Orb/Stripe/Metronome choice entirely.
- Suno · Jun 2026 — RevenueCat handles app-store subscription billing — a consumer-app rail outside the three-name B2B shortlist.
- n8n · Jun 2026 — Tail vendor, and the only corpus company with NO Stripe presence in its monetization stack at all: "each plan object on the live pricing page carries a Paddle product ID ('paddleId'/'annualPaddleId') and the page loads a Paddle logo asset; no Stripe present" — Paddle as merchant-of-record for a workflow-execution meter. A company can run a usage meter and never touch any of the three.
- Gladia · Jan 2024 — Tail vendor: Hyperline, the only user in the corpus, chosen for exactly the job the three claim — "we wanted to have a unique billing tool to onboard our future customers autonomously on our free and pay-as-you-go plans and manage Enterprise subscriptions—all in one place." Same requirement, different answer, and it predates most of the Orb/Metronome adoptions.
- Writesonic · Jun 2026 — Tail vendor: Chargebee, disclosed not in a case study or a job req but in a legal sub-processor table ("Chargebee — Function: Billing — Entity Country: US"). One of 3 Chargebee mentions (with windsurf and deepgram, both inferred from candidate lists), the largest tail vendor after Zuora — a reminder that the subscription-billing incumbents never left, they just stopped being written about.
- Zoominfo · Jul 2026 — Sidesteps the shortlist entirely at enterprise scale: its quote-to-cash spine is Salesforce CPQ/Revenue Cloud for quoting, Thomson Reuters OneSource for tax, and SAP S/4HANA for posting, with no billing vendor named and no in-house billing engine — even though it runs a pooled export-credit meter. For fully sales-led sellers the relevant shortlist is CPQ vendors, not usage-billing vendors.
Trivia
-
Mistral runs on Lago, the open-source billing vendor — the only frontier-lab user of a non-US billing platform in the corpus, while its US-lab peers Anthropic and Together AI both run Metronome.
-
Orb wins where the buyer already built its own meter: 6 of its 8 corpus users — baseten, chroma, fireworks-ai, pinecone, relevance-ai, vercel — pair Orb with an in-house metering pipeline. Chroma is the cleanest statement of the split ("Rather than building and maintaining this ourselves, we partner with Orb"; its own CDC meter off the Postgres WAL feeds Orb), and fal-ai buys both halves ("integrate with Orb for usage metering and Stripe for payments"). Orb is bought as the invoicing/plan/credit layer on top of someone elses meter, not as the meter itself.
-
Stripe Billing is the only one of the three that also does the metering: Browserbase meters hundreds of millions of browser-session-minutes a month on Stripe directly and explicitly chose not to build, whereas Langfuse uses Stripe Billing only as the biller and keeps its own ClickHouse meter.
-
The ranking flipped between the two reviews. Between 2026-06-23 and 2026-07-30 Stripe Billing went from 9 named users to 18 while Orb added exactly zero, so Stripe Billing now outnumbers Orb (8) and Metronome (8) combined — a reversal of the 2026-06-17 first observation, when Orb and Stripe Billing were tied at 5 each. Two of the new Stripe case studies also publish numbers the build side never does: Heidi Health had Payments, Optimized Checkout, Billing and Invoicing live in "two to three days," and invideo's failed-renewal recovery went from 23% to 30% on Smart Retries alone.
-
Anthropic disproves the premise that this is one decision: it names Metronome for metering, Zuora for billing, Stripe for payments, and NetSuite plus Tesorio for rev-rec — four vendors across four layers, in a single Finance Systems Engineer req dated 2026-06-19 that also announces it is building a homegrown ledger on top of all of them.
-
Zuora went from zero corpus users at the 190-block review to 7 by 2026-07-30 — anthropic, canva, claude-code, deepgram, gitlab, yellow-ai, zendesk-ai — and not one is an AI-native. Zendesk's endorsement is a decade old ("Zuora is the number one choice when it comes to billing systems," Zack Urlocker, 2014), which is precisely the point: Zuora wins the installed subscription base, not the new meter. Meanwhile Yellow.ai bought Togai specifically to sync metered billing back INTO its existing Zuora (2024-02), the clearest statement that the two lanes are complements.
For buyers
If you are choosing a usage-billing vendor, the corpus narrows the field fast. Already built your own meter? Orb is the most common pairing — it is the invoicing/plan layer that sits on top. Already on Stripe for payments? Stripe Billing keeps the meter and biller in one system. At enterprise/lab scale inside a Salesforce + NetSuite stack? Metronome is the conventional pick. Outside those three you are in idiosyncratic territory — OpenMeter (open-source, entitlements), Lago (open-source, EU), RevenueCat (app-store subscriptions), or routing everything through a cloud marketplace.
For vendors
For billing-platform vendors, the corpus says the AI-infra buy decision is effectively a three-horse race, and each horse has a defensible lane rather than competing head-on. Orb's wedge is companies that built their own meter and want billing on top; Stripe's is its installed payments base; Metronome's is the enterprise quote-to-cash co-sell. The tail vendors win on a specific attribute (open-source, app-store, marketplace co-sell) — competing on general-purpose usage billing against the three leaders is the hard path.
Outlook — what to watch
Logged as new in June 2026. The shortlist tightens if Orb and Stripe Billing keep splitting the meter-already-built vs payments-already-Stripe lanes while Metronome holds the lab tier. It loosens if a cloud marketplace billing path (milvus, vantage) or an open-source option (Lago, OpenMeter) starts taking share from the three — watch whether marketplace-as-biller spreads below the infra layer.
Bottom line
The AI usage-billing buy decision is a three-name shortlist — Orb, Stripe Billing, Metronome account for 13 of ~16 named-vendor corpus companies. Each wins a distinct lane; the rest are one-offs.
FAQ
What are the most common usage-billing vendors for AI companies?
Orb, Stripe Billing, and Metronome. In the corpus, Orb and Stripe Billing each appear in 5 company stacks and Metronome in 3 — together 13 of roughly 16 companies that name a usage-billing vendor. OpenMeter, Lago, RevenueCat and cloud marketplaces make up the tail.
When do companies pick Orb vs Stripe Billing?
Orb tends to win where the company already built its own meter and wants a billing-native system of record on top (Baseten, Pinecone, Relevance AI, Vercel). Stripe Billing tends to win where the company already runs Stripe for payments — and it is the only one of the three that also does the metering itself (Browserbase).
What do frontier labs use for usage billing?
Metronome is the lab-scale pick — Anthropic and Together AI both run it inside a broader Salesforce + NetSuite quote-to-cash stack. The exception is Mistral, the only frontier lab on the open-source Lago platform.
Are there alternatives to the big three?
Yes, but they are idiosyncratic: Trigger.dev runs OpenMeter (including its entitlements for free-tier gating), Mistral runs Lago, Suno uses RevenueCat for app-store subscription billing, and Milvus and Vantage route enterprise billing through AWS/Azure cloud marketplaces instead of a standalone vendor.