Three usage-billing vendors win the buy decision: Orb, Stripe Billing, Metronome
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
13 supporting · 4 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. |
| 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. |
| 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. |
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.
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 (baseten, pinecone, relevance-ai, vercel all pair Orb with an in-house metering pipeline) — Orb is bought as the invoicing/plan 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.
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.