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 19 corpus companies that disclose both a classified metering and a classified billing layer, 13 run exactly this split: an in-house meter (events to aggregation to rating) feeding a bought biller — Orb, Stripe Billing, or a cloud marketplace — for invoicing and payments. Across the 295 companies carrying a monetization-stack profile, the meter resolves in-house 41 / vendor 8 while billing resolves vendor 59 / in-house 11 — companies build the meter ~5:1 and buy the biller ~5:1.
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. The aggregate is now lopsided enough to read straight off the corpus: among the 295 companies with a monetization-stack profile, the metering category resolves in-house 41 / vendor 8 (~5:1 built over bought), while billing resolves vendor 59 / in-house 11 and payments vendor 92 / in-house 1 — the biller and the payment rail are overwhelmingly bought.
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: Orb, Stripe Billing, Metronome and the cloud marketplaces already do invoicing, dunning, plans and tax, so there is little reason to rebuild them.
How it works
Evidence over time
18 supporting · 4 counter — hover or tap a point for detail, click to jump to the row.
Evidence
| Company | Date | What happened |
|---|---|---|
| Chroma | Jun 2026 | The textbook case, stated verbatim: an in-house meter (per-tenant aggregation flushed every ~minute to object storage, fed by Postgres-WAL change-data-capture) that explicitly partners with Orb for billing — 'Rather than building and maintaining this ourselves, we partner with Orb to handle these aspects.' (trychroma.com/engineering/billing). Build the meter, buy the biller, said in one post. |
| Weaviate | Jun 2026 | Owns the meter behind its signature per-vector-dimension price (objects x dimensionality x replication computed in-house, per the Oct-2025 pricing-update post) but buys the rails entirely — 'Weaviate Cloud (WCD) uses Stripe for billing' and marketplace billing rides AWS/GCP (docs.weaviate.io/wcs/platform/billing). |
| RunPod | Jun 2026 | The meter behind RunPod's per-second pricing is its own credit ledger ('Credits are deducted in real-time... Billing runs every 5 minutes', docs.runpod.io/accounts-billing/billing); only payments ride Stripe ('cards supported by Stripe'). In-house meter, bought payment rail. |
| 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. |
| Stripe Billing | Jul 2026 | The bought-biller side restructured, with a published build-vs-buy boundary. Stripe unbundled advanced usage-based billing out of its 0.7%-of-Billing-volume rate into Metronome (acquired January 2026): the Billing feature row changed from an 'Included' checkmark to 'Usage-based billing*' with a Contact Metronome link, and Metronome now sits as its own product card on stripe.com/pricing between Billing and Invoicing, labelled 'a Stripe product'. The asterisk sets the line: basic usage-based billing stays inside Billing pricing via the Meters API 'with up to 100M events per month included'. Metronome Startup covers a US$100,000 billing allotment plus 10 million usage events, overages subject to additional pricing; Metronome Custom is quoted. For the 19 build-meter/buy-biller companies this is the first published event-volume threshold at which renting the biller stops being enough. |
| Salesforce | Jul 2026 | The meter-vendor layer being absorbed by a CRM platform: Salesforce's investment in m3ter converted into ownership — the site banner now reads 'm3ter is now part of Salesforce', with the header lockup and footer copyright both 'm3ter from Salesforce' (replacing 'M3ter Holdings Limited'). m3ter is the metering-and-rating engine behind Revenue Cloud Advanced, and its /pricing page is otherwise word-for-word unchanged (core platform fee, add-ons, support package, implementation services; zero dollar amounts; 'Talk to us'). One of the corpus's few named metering vendors is now owned by the largest CRM incumbent — 'buy the meter' increasingly means buying from a platform owner. |
| HubSpot | Jul 2026 | Fully-built becomes a vendor. The in-house Commerce Hub build (CPQ / Billing / Payments / Revenue OS) that this page logged as the fully-built counter-pattern shipped as Revenue Hub, a priced sixth Hub described on HubSpot's own page as 'the evolution of Commerce Hub': Free (invoices, payment links, subscriptions), Professional from $95/mo (CPQ quoting, contracts, e-signature, revenue analytics), Enterprise from $140/mo (advanced quote approvals). HubSpot Payments takes 2.9% + $0.50 per card transaction (0.8% + $0.50 ACH, each capped at $10) with a 60-day no-platform-fee promo — and charges sellers who keep Stripe a flat 0.75% platform fee. The build this page had tracked only via a June-2026 'Principal Software Engineer - Commerce' req became a monetized product in about six weeks. |
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
-
Chroma states the split verbatim in a June-2026 engineering post: it built its own usage meter — per-tenant aggregation flushed to object storage roughly every minute, fed by change-data-capture off its Postgres SysDB write-ahead log — then writes, of the billing layer, "Rather than building and maintaining this ourselves, we partner with Orb." Built meter, bought biller, in one sentence each.
-
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 15 build-meter/buy-biller companies, most run Stripe in some form (anthropic, cursor, dust, langfuse, lovable, perplexity-ai, runpod, suno, synthesia, vercel, weaviate) and several run Orb (baseten, chroma, 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 among the most build-heavy of the 15: 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.
-
The build:buy asymmetry is far more extreme than the 190-block snapshot suggested. Recomputed at 353 companies, metering resolves in-house 43 / vendor 9 — a 4.8:1 build ratio, not the ~2:1 previously published — while billing-plus-payments resolves vendor 113 / in-house 12 (9.4:1 bought). Payments is the most one-sided category in the entire corpus: in-house 1 / vendor 93. Companies will build the thing that decides what a customer owes and almost never build the thing that collects it.
-
The largest hole in this dimension is a null, and it should be stated rather than inferred: of the ~90 companies with an in-house meter, exactly ONE (Kustomer) is outcome-based, against a 7% corpus base for outcome-based tagging. The metering basis of the 24 outcome-priced vendors is almost entirely `unknown` — so at the moment per-resolution billing became the default unit in AI customer service (14 of 19 companies), the corpus has essentially no sourced evidence of how any of those vendors actually meter a resolution.
-
Stripe published a number that defines the build-vs-buy line for the whole cohort. On 2026-07-22 it moved advanced usage-based billing out of its 0.7%-of-Billing-volume rate into Metronome (which Stripe acquired in January 2026) — the Billing feature row changed from "Included" to "Usage-based billing*" with a Contact Metronome link — and footnoted the boundary: basic usage-based billing stays in Billing pricing via the Meters API "with up to 100M events per month included." Above 100M events/month, buying Stripe stops being sufficient; Metronome Startup covers a US$100,000 billing allotment plus 10 million usage events.
-
The "rent the biller" half consolidated into three platform owners in twelve days. Stripe routed usage-based billing to its own Metronome (2026-07-22), Salesforce completed m3ter — the metering-and-rating engine behind Revenue Cloud Advanced (2026-07-21) — and HubSpot turned its previously in-house Commerce Hub into a sold product, Revenue Hub, charging 2.9% + $0.50 per card transaction and a flat 0.75% platform fee from sellers who keep Stripe (2026-07-30). 98 corpus companies name Stripe in some form; a further 10 name a cloud marketplace as their billing system of record.
-
HubSpot shows "fully built" is a route to becoming a vendor, not a permanent counter-pattern. It was logged here as the fully-built quote-to-cash exemplar (Commerce Hub: CPQ / Billing / Payments / Revenue OS in-house); on 2026-07-30 that build shipped as Revenue Hub, a priced sixth Hub at Free / from $95 / from $140 per month. The internal build this page had tracked only through a June-2026 "Principal Software Engineer - Commerce" job posting became a monetized product in roughly six weeks.
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 the billing vendor. 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 Orb, Stripe Billing, Metronome, or a cloud marketplace — 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 (Groq and Predibase run an in-house meter and in-house billing; Kustomer, Tavus the same) 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 — Google Cloud Billing meters and bills Vertex AI itself at hyperscaler scale. Buying both (Browserbase; Anthropic and Claude Code, which meter on Metronome and bill on Zuora) is the right call for a small team that does not want to run billing infrastructure, or a frontier lab standardizing on a quote-to-cash suite. 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), Stripe's metered-usage API (if you already run Stripe for payments), or a cloud marketplace (if you sell through AWS/GCP/Azure).
Outlook — what to watch
Sharpens in June 2026: across the broadened corpus the aggregate now backs the split outright — metering in-house 41 / vendor 8, billing vendor 59 / in-house 11 — and 13 of 19 companies that classify both layers run the build-meter / buy-biller shape. It strengthens further as fully-built holdouts (Kustomer, Tavus, Predibase) migrate their invoicing to a vendor while keeping the meter, 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, and the marketplace billers that meter for you, are the things to watch.
Bottom line
The metering pipeline is the one piece AI-infra companies refuse to outsource; everything around it is bought. 13 of 19 corpus companies that disclose both layers build the meter and rent the biller — and the corpus-wide aggregate agrees, with metering built ~5:1 and billing bought ~5:1. The exceptions split cleanly into build-everything (Groq, Predibase, Kustomer, Tavus) and buy-everything (Anthropic, Claude Code, 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. 13 of 19 corpus companies that classify both a metering and a billing layer disclose exactly this split, and the corpus-wide aggregate matches — metering resolves in-house 41 / vendor 8, while billing resolves vendor 59 / in-house 11.
Why don't AI companies just use a vendor 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, so the metering category runs in-house ~5:1 over bought. Orb, Stripe Billing, Metronome and the cloud marketplaces are bought for the commoditized part: invoicing, plans, dunning, tax.
Which billing vendors do they buy?
Orb, Stripe Billing, Metronome, and increasingly cloud marketplaces. Of the 13 build-meter/buy-biller companies, several run Orb (Chroma, Pinecone, Weaviate) or Stripe in some form (Langfuse, Suno, Weaviate), while infra vendors route billing through AWS/GCP/Azure marketplaces (Qdrant, SambaNova, Qodo, Hugging Face) or other rails (Dify on PartnerStack, Voyage AI on MongoDB Atlas).
Who builds the whole stack themselves?
Groq and Predibase run both an in-house meter and in-house billing; Kustomer (per-conversation metering, no named biller) and Tavus (in-house metering and billing in its Developer Portal) do the same. Google bills and meters Vertex AI through Google Cloud Billing at hyperscaler scale. The opposite corner — buy everything — is Anthropic and Claude Code, which meter on Metronome and bill on Zuora, plus Browserbase on Stripe Billing.