Usage-Based Billing
Charge customers for what they use — API calls, AI tokens, seats, storage — by metering events and turning them into invoices.
Trends
Metronome gained the most ground in package downloads: 10.7× against the median npm package over a year.
Public counts each month: pull requests on GitHub, package downloads, stars, Product Hunt followers. They show direction, not market share.
The real choice
Your payment processor, a dedicated metering engine, or a merchant of record. Using your processor's own metering keeps everything in one place; a dedicated engine handles complex pricing and heavy event volume but is another system to integrate; a merchant of record also takes on sales tax, for a higher fee per transaction.
Pick by situation
Tap the ones that are you — the tools that fit light up below.- Your subscriptions already run on Stripe and your pricing is a plan plus overage
Stripe - You're solo, sell worldwide and don't want to deal with sales tax
Polar - Your pricing is too complex for your processor and you'd rather self-host the metering than pay for it
Lago
OpenMeter - You're on Stripe and want credits, limits and plan changes without writing webhook code
Autumn - Usage revenue is the core of the business and you have the budget for a sales-priced tool
Orb
Compare the tools
Grouped by the side of the choice they answer, not ranked. Open a row for when to use it, the trade-off and what makers say.
StripeapiApps already on Stripe that want meters and usage-based prices next to their subscriptions.
119.7M/wk+40% vs npm
Use it whenYou want to add a metered charge to existing Stripe subscriptions without another vendor.
Trade-offYou are the merchant of record, so sales tax and VAT are yours to handle.
llms.txtMCPCLIIn Bolt, Lovable, Replit, v0Used by giselle.
Stripe powers our entire billing infrastructure. The new Billing for LLM tokens feature (Private Preview) made it incredibly easy to implement usage-based pricing for AI API consumption — what would have taken weeks to build ourselves was ready in days. Combined with Pricing Plan Subscriptions for our team plans, Str…
Polarservice · open sourceSolo developers who want usage billing, subscriptions and sales tax handled by one open-source service.No evidence yet275.8k/wk+142% vs npm
Use it whenYou want to charge for usage without registering for sales tax in every country you sell to.
Trade-offHigher per-transaction fee than a plain processor; fewer billing options than dedicated engines.
llms.txtNo maker's product we track shows it for this yet.
OrbapiHigh-volume usage billing with many pricing models, for products whose revenue depends on it.


15179.3k/wk+0% vs npm
Autumnservice · open source · free tierCredits, usage limits and plan entitlements on top of Stripe, checked from your code with a few calls instead of Stripe webhooks.


12+15 open source170.6k/wk7.9× vs npm
Use it whenYou're on Stripe and want to change pricing — plans, credits, overage — without rewriting billing code each time.
Trade-offA young company; one more service between your app and Stripe that access checks depend on.
llms.txtCLIUsed by Almanac, Prism Videos, Slashspace AI, Backdrop, Databuddy Analytics and 7 more · in 15 open-source projects.
Autumn made usage-based billing and subscription management much easier for our small team.
Lagoapi · open source · free tierComplex usage pricing you want to self-host for free, sitting on top of your payment processor.
148.1k/wk+38% vs npm
Use it whenYour processor's metering can't express your pricing, and you're fine running one more service to keep it free.
Trade-offOne more system to host and connect to payments.
llms.txtUsed by Cerebrium.
Lago has made it very simple to implement usage based billing for our clients that we could easily integrate via API. It is also very feature rich when it comes to
OpenMeterapi · open source · free tierOpen-source, real-time metering of high-volume usage events (API calls, tokens, compute), turned into entitlements and invoices.No evidence yet23.7k/wk+6% vs npm
Use it whenYou need accurate usage counts at high event volume and want to self-host the meter, or run it on Kong's cloud.
Trade-offA stack of services (including Kafka and ClickHouse) to run if self-hosted; now part of Kong's product line.
llms.txtNo maker's product we track shows it for this yet.
Who switches to what
Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes, by developers in general rather than makers only. Pick a flow to see its pull requests.
- Handle Stripe subscriptions migrated to Polarschej-it/timeful.app · 2026-10-01
- Move new purchases from Stripe to Polarschej-it/timeful.app · 2026-10-01
- fix: allow to import archived products in live Stripe subscriptions to Polarpolarsource/polar · 2026-09-16
- feat: improve the copy of Stripe to Polar messagingpolarsource/polar · 2026-09-16
- Switch checkout from Stripe to PolarChetan3777/top-builders · 2026-08-23
- feat(billing): migrate from Stripe-direct to Polar.sh + Apache-2.0 LICENSEbuildproven/qa-architect · 2026-05-20
- feat(billing): migrate SaaS billing from Stripe to Polarmohamed-ndoye811/horaya · 2026-03-23
- RED-72: Migrate billing from Stripe to Polar (PR2)aegloist/Openfast · 2026-02-19
- feat: migrate payment integration from Stripe to PolarTheGoatedDev/NearIRM · 2026-02-06
- [Issues #808, #887] Migrate billing tests and production code from Stripe to PolarEibon7/roastr-ai · 2025-11-19
- Implement logic to migrate subscription from Stripe to Polar enginepolarsource/polar · 2025-09-24
- payment flow - Stripe to Polar Migration: Update Payment, Subscription API & SchemaBetrixDev/slipstream · 2025-02-28
- Migrate billing from Lemon Squeezy to Stripeazmainraihan28-netizen/hirebest2 · 2026-09-30
- Migrate the buy flow from Lemon Squeezy to direct Stripe CheckoutMarxal/obertura · 2026-08-17
- swap lemon squeezy to stripe and fix beta code timezonenicomigu/runRename · 2026-06-02
- Switch payment integration from Lemon Squeezy to Stripejddelia/thriftypigeon-v2 · 2025-10-09
- fix: migrate lemon squeezy to stripeformizee/formizee · 2025-01-16
- Switch payment provider from Lemon Squeezy to Polarpejochto/VisionFrame · 2026-08-19
- Pricing: move checkout from Lemon Squeezy to Polarthai-pc/thai-pc.github.io · 2026-08-05
- ops: rewrite the v6.4 hold and checkout bindings from Lemon Squeezy to Polardevswha/patina · 2026-08-02
- Migrate payment provider from Lemon Squeezy to Polar.raza-ali12/license-api · 2026-07-23
- feat(billing): migrate Pairlens Intelligence from Polar to StripePairlens/trading-terminal · 2026-08-09
- feat(billing): complete pricing plans + Polar to Stripe migrationstrait-dev/strait · 2026-03-31
- Transitioning from Polar to the Stripe plugin for Better AuthSteellgold/simplist.blog · 2025-03-02
- Migrate platform billing from Stripe to Lemon Squeezyflgmindfulnessalive/WeWebinar · 2026-09-03
- Migrate checkout from Stripe to Lemon Squeezysifoukhelif/bob · 2026-07-17
- [FEAT] Migrate payment system from Stripe to Lemon Squeezy (#23)agentgram/agentgram · 2026-02-02
Before you choose
Record every billable event in your own database first, with an idempotency key, even if a billing tool also meters it — that's your audit trail when a customer disputes an invoice. Keep pricing simple at launch (a base plan with included usage plus overage) and put a hard spending cap in place for AI costs. Move to a dedicated engine only when your processor can't express the pricing you need.
- Relying only on the billing tool's meter with no event log of your own, so you can't show a customer why their invoice says what it says.
- Sending usage events without idempotency keys, so a retry after a timeout bills the same API call twice.
- Selling uncapped AI usage at a flat price, where one heavy user can cost more in model fees than they pay you.
Other options
Real choices most makers here won't need to weigh.
Decided alongside
What the 30 makers' products here chose for their other decisions.