Build the meter, buy the biller: the AI-infra monetization split
Usage-metered AI-infrastructure companies build their own metering pipeline but buy the billing system at the edge. Of 77 corpus companies with a monetization-stack profile, 12 disclose exactly this split: an in-house meter (events to aggregation to rating) feeding a bought biller — Stripe, Orb, or Metronome — for invoicing and payments.
What's happening — and why
What's happening: companies whose pricing is computed from usage events treat the metering layer as something to build in-house, but treat invoicing, plan management, and payments as a commodity to buy. The recurring shape is a homegrown pipeline that counts usage per account and ships it out-of-band to a third-party billing system of record.
Why: the meter is too coupled to the value metric to outsource — read-units, traces, browser-session-minutes, agent-compute-units and tool-calls are each idiosyncratic, and the pipeline that produces them is the literal mechanism that turns the product into revenue. The biller, by contrast, is a solved problem: Stripe, Orb, and Metronome already do invoicing, dunning, plans and tax, so there is little reason to rebuild them.
How it works
Evidence over time
12 supporting · 4 counter — hover or tap a point for detail, click to jump to the row.
Evidence
| Company | Date | What happened |
|---|---|---|
| Baseten | May 2026 | Frontier Gateway post: in-house metering/rate-limiting tracks token/character consumption per API key and ships usage out-of-band to plug directly into your billing provider; a billing-eng req names that provider as Orb. In-house meter, bought biller. |
| Cursor | Jun 2026 | Billing-eng req: in-house usage metering pipelines, aggregation logic, entitlement enforcement and ledger feeding invoiced amounts in Stripe. Meter built, payments bought. |
| Perplexity AI | Jun 2026 | In-house usage-based billing and metering platform plus a build-over-buy CPQ; buys Stripe (payments), NetSuite (rev-rec), Salesforce (CRM) at the edges only. |
| Vercel | Jun 2026 | Real-time usage data pipeline (in-house) feeding Orb (billing) and Stripe (payments); NetSuite for rev-rec. The classic own-the-meter / buy-the-biller layering. |
| Langfuse | Jun 2026 | Stripe case study: migrated off a homegrown per-event billing system to Stripe Billing/Checkout/Tax but kept metering in-house — posts hourly event counts from its own ClickHouse/OLAP store to Stripes metered-usage API (up to 200M events/mo per account). |
| Pinecone | Jun 2026 | Replaced its in-house billing engine with Orb when it launched serverless; the read-unit/write-unit metering layer stays in-house, Orb handles invoicing and plans. |
| Relevance AI | Jun 2026 | Stack carries an in-house billing and metering core alongside bought Stripe (payments) and Orb (billing). |
| Lovable | Feb 2026 | In-house credit-usage metering ledger feeding Stripe for payments; five billing-eng roles open against that ledger. |
| Suno | Jun 2026 | In-house usage metering and subscription lifecycle feeding Stripe (payments) and RevenueCat (app-store billing). |
| Synthesia | Feb 2026 | In-house billing system plus in-house usage metering, with Stripe (payments), Salesforce (CRM) and DealHub (CPQ) bought around the core. |
| Dust | Jun 2026 | In-house usage metering and credits with Stripe (payments) and HubSpot (CRM) at the edges. |
| Anthropic | Jun 2026 | Most build-heavy variant: a homegrown ledger application explicitly beyond configuring off-the-shelf platforms, but still wires to bought Stripe, Zuora, Metronome (metering) and NetSuite — build the core ledger, buy the rails. |
Counterexamples
- Browserbase · May 2026 — Fully bought: Stripe customer case study confirms it runs metering AND billing on Stripe Billing and preferred to partner with a billing vendor rather than build custom billing infrastructure — no in-house meter.
- Kustomer · Jun 2026 — Fully built: per-conversation usage metering and API rate-limit/quota enforcement are Kustomer-operated with no named billing vendor — meter and biller both in-house.
- Milvus · Jun 2026 — Buys the rail entirely: cloud-marketplace billing (AWS/GCP/Azure) is the billing system of record; the CU/vCU meter is operated but no separate biller is built or bought.
- Tavus · Jun 2026 — Fully built: in-house usage metering and billing in the Developer Portal, no third-party billing vendor disclosed.
Trivia
-
Baseten states the split almost verbatim: its May-2026 Frontier Gateway post says token/character consumption is tracked per API key and sent out-of-band to plug directly into your billing provider, while a billing-eng req names that provider as Orb — the meter is Baseten built, the biller is bought.
-
Of the 12 build-meter/buy-biller companies, 9 run Stripe in some form (anthropic, cursor, dust, langfuse, lovable, perplexity-ai, suno, synthesia, vercel) and 4 run Orb (baseten, pinecone, relevance-ai, vercel) — Vercel runs both, Orb for billing and Stripe for payments, on top of its own real-time usage pipeline.
-
Perplexity is the most build-heavy of the 12: it discloses an in-house usage-based billing platform AND a build-over-buy CPQ/quote-to-cash layer, buying only Stripe (payments), NetSuite (rev-rec) and Salesforce (CRM) at the edges — closer to the Anthropic homegrown-ledger end than the rent-everything end.
For buyers
If you are evaluating a usage-metered AI vendor, ask which half of the stack is theirs. A vendor that built its own meter controls the accuracy and the definition of the unit you are billed on — dispute resolution lives with them, not Stripe. A vendor running fully on a bought billing platform (Browserbase on Stripe Billing) has outsourced both, which can mean cleaner invoices but less ability to model bespoke usage events. Either way, the system of record for invoices is almost always Stripe, Orb, or Metronome — that is who issues the document you reconcile against.
For vendors
The build-vs-buy line is well-established: build the metering pipeline, buy the biller. Building both (Kustomer, Tavus) only pays off if your usage events are too exotic for a vendor to ingest or you are large enough to amortize an invoicing team. Buying both (Browserbase) is the right call for a small team that explicitly does not want to run billing infrastructure. The default for everyone in between is an in-house meter that posts usage to Orb (if you want a billing-native system of record) or Stripe's metered-usage API (if you already run Stripe for payments).
Outlook — what to watch
Logged as new in June 2026 across 12 of 77 monetization-stack profiles — the dominant disclosed architecture for usage-metered AI infra. It strengthens if more of the fully-built holdouts (Kustomer, Tavus) migrate their invoicing to a vendor while keeping the meter, which is exactly the path Pinecone and Langfuse already took. It weakens only if a billing vendor starts ingesting arbitrary usage events well enough that companies stop building the meter at all — Stripe Billing's own metering is the thing to watch.
Bottom line
The metering pipeline is the one piece AI-infra companies refuse to outsource; everything around it is bought. 12 of 77 corpus companies build the meter and rent the biller, against a handful who build everything (Kustomer, Tavus) or buy everything (Browserbase).
FAQ
Do AI companies build or buy their billing?
Most usage-metered AI-infra companies split the decision: they build the metering pipeline in-house and buy the billing/invoicing layer from a vendor. 12 of 77 corpus companies with a monetization-stack profile disclose exactly this split, against a small number who build everything or buy everything.
Why don't AI companies just use Stripe for metering too?
The meter is coupled to the value metric — read-units, traces, browser-minutes, agent-compute-units — and the pipeline that produces those counts is the mechanism that turns the product into revenue. Companies treat it as core IP. Stripe, Orb, and Metronome are bought for the commoditized part: invoicing, plans, dunning, tax.
Which billing vendors do they buy?
Almost always Stripe, Orb, or Metronome. Of the 12 build-meter/buy-biller companies, 9 run Stripe in some form and 4 run Orb; Vercel runs both (Orb for billing, Stripe for payments) on top of its own usage pipeline.
Who builds the whole stack themselves?
Kustomer (per-conversation metering and quota enforcement, no named biller) and Tavus (in-house metering and billing in its Developer Portal) build both halves. Anthropic is the most build-heavy of the metered cohort — it runs a homegrown ledger explicitly beyond off-the-shelf platforms — but still buys Stripe, Zuora, Metronome and NetSuite at the edges.