Usage-Based Billing for Next.js: what 13 makers' products chose
Among 13 makers' products built with Next.js that we know the Usage-Based billing of, Orb leads: 6 of them (46%). Next come Autumn (3) and Chargebee (2).
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.
What makers on Next.js chose
| Option | Next.js products | All makers |
|---|---|---|
| 6 (46%) | 38% | |
| 3 (23%) | 30% | |
| ChargebeeMetering engine | 2 (15%) | 18% |
| 1 (8%) | 3% | |
| 1 (8%) | 3% |
Live makers' products with a source for both: that they're built with Next.js, and what they use for Usage-Based billing. A product using two options counts in both; not market share. "All makers" is the option's share among every maker's product that made this decision.
Which to pick, by situation
- Your subscriptions already run on Stripe and your pricing is a plan plus overage
Stripe 1 here - You're on Stripe and want credits, limits and plan changes without writing webhook code
Autumn 3 here - Usage revenue is the core of the business and you have the budget for a sales-priced tool
Orb 6 here
Orb
Metering engine6 Next.js products here (46%).
llms.txtBest forHigh-volume usage billing with many pricing models, for products whose revenue depends on it.
Trade-offNo free tier and sales-priced — built for funded teams, not side projects.
- Teams launch hybrid seat-plus-usage pricing quickly without pulling engineers off core product work. 3 sources
- Automated charge calculation and invoicing give finance reliable data for multi-product usage pricing. 3 sources
Status page: 6 incidents in the last 90 days, 1 major (its own page, 2026-10-19).
Autumn
Metering engine3 Next.js products here (23%).
llms.txtCLIBest forCredits, usage limits and plan entitlements on top of Stripe, checked from your code with a few calls instead of Stripe webhooks.
Trade-offA young company; one more service between your app and Stripe that access checks depend on.
“Autumn made usage-based billing and subscription management much easier for our small team.”
- It sits on top of Stripe so teams add usage-based pricing without managing webhooks themselves. 3 sources
- The SDK and dashboard feel neat and intentional, and billing goes live in days. 2 sources
Status page: 3 incidents in the last 90 days, 3 major (its own page, 2026-10-19).
“super easy usage based billing”
Usage-Based BillingMaker says so · source ↗“Autumn made usage-based billing and subscription management much easier for our small team.”
Usage-Based BillingMaker says so · source ↗Chargebee
Metering engine2 Next.js products here (15%).
llms.txtBest forA mature hosted billing system for subscriptions plus usage charges, invoices and dunning, on top of the payment gateway you already use.
Trade-offTakes a percentage of invoiced revenue on top of gateway fees, and you are still the merchant of record for tax.
“Integrated with Kroolo's backend and revenue operations engines for all the effective client onboarding, plan setting and billing.”
Status page: 14 incidents in the last 90 days, 2 major (its own page, 2026-10-19).
“Integrated with Kroolo's backend and revenue operations engines for all the effective client onboarding, plan setting and billing.”
Usage-Based BillingMaker says so · source ↗“…imilar ideals to us, and we’re pleased to support them by using their incredible product! Chargebee - We use Chargebee to manage our subscriptions with Stripe and PayPal as our payment gate…”
Usage-Based BillingMaker says so · source ↗Also chosen, and not seen yet
Fewer Next.js products here: Stripe (1), Paid (1).
Real options for Usage-Based billing not seen among these Next.js products yet: Polar, Lago, OpenMeter.
Getting Usage-Based billing right
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.
The rest of the Next.js stack
What makers' Next.js products chose for their other decisions, the most common pick for each:
- Hosting: Vercel 1,078 of 1,312
- Transactional Email: Resend 493 of 830
- Database: Supabase 171 of 382
- Payments: Stripe 288 of 359
- LLM API: OpenAI API 222 of 301
- Authentication: Clerk 176 of 211
- Web Analytics: Google Analytics 105 of 197
- Product Analytics: PostHog 123 of 168
Questions
What do most Next.js apps use for Usage-Based billing?
Among 13 makers' products built with Next.js that we know the Usage-Based billing of, Orb leads: 6 of them (46%). Next come Autumn (3) and Chargebee (2).
How this is counted: a product is on Next.js when a live-product source says so (the maker, its website, a customer story or a subprocessor list), and the same for its Usage-Based billing. How evidence is collected.