Start with Stripe Billing. Its built-in usage meters cover per-unit, tiered, and graduated pricing — enough for almost every micro-SaaS. Reach for Lago if you want open-source control, Chargebee when billing operations get complicated, and a merchant of record like Paddle if global sales tax is your bigger problem. Orb and Metronome are excellent but built for enterprise scale — skip them until you have a team.
Usage-based pricing keeps eating SaaS — AI products especially have made per-credit and per-request pricing normal. But the moment you move past flat subscriptions, billing becomes a real engineering problem: you have to meter events, aggregate them per customer, rate them against your pricing, and invoice correctly — every period, without errors.
If you haven't decided whether usage-based pricing is even right for your product, read our data-driven guide on whether micro-SaaS founders should use usage-based pricing first. This article is for when you've decided yes — and need the tooling.
What Usage-Based Billing Software Actually Does
Every tool on this list solves some slice of the same four-stage pipeline:
- 1.Metering — capturing usage events (API calls, seats, credits, GB processed) reliably.
- 2.Aggregation — summing, counting, or taking the max of those events per customer per period.
- 3.Rating — applying your price model: per-unit, tiered, graduated, volume, or prepaid credits.
- 4.Invoicing & collection — generating the invoice, charging the card, handling failures and dunning.
The right question isn't "which tool is best" — it's how much of this pipeline you actually need to outsource. A solo founder billing simple per-unit usage needs far less machinery than a platform team supporting custom enterprise contracts.
The Tools, Compared
1. Stripe Billing — the default starting point
Stripe Billing has built-in usage meters: you send usage events from your code, Stripe aggregates them, and bills customers at period end. It supports per-unit, tiered, and graduated pricing, plus hybrid models (base fee + overage). Pricing is a percentage of billing volume on top of standard processing fees — check current rates, but for a small product the cost is trivial compared to running your own pipeline.
Why it wins for solo founders: you almost certainly already use Stripe for payments, the documentation is the best in the industry, and there's no second system to reconcile. The main limits: real-time spend visibility for customers takes extra work, and complex enterprise contract logic (custom minimums, commitments, true-ups) gets painful.
2. Lago — open-source control
Lago is an open-source metering and billing engine. You self-host it (free) or use their cloud, define billable metrics, and it handles aggregation and invoicing — typically pushing the final charge through Stripe or another processor. It's the strongest option if you want to own your billing data, avoid per-volume platform fees, or have event volumes that would get expensive elsewhere.
The trade-off: self-hosting is real operational work — a database, upgrades, monitoring. For a technical founder who enjoys infrastructure it's excellent; if you'd rather never think about billing servers, it isn't.
3. Chargebee — when billing ops outgrow you
Chargebee sits on top of your payment gateway and handles subscription management, metered billing, coupons, dunning, invoicing, and revenue reporting. It has historically offered a generous free launch tier for early-stage companies (verify the current threshold), which makes it a reasonable choice once your pricing has many moving parts — multiple plans, add-ons, trials, proration rules.
The trade-off: it's another system between you and Stripe, with its own dashboard, webhooks, and edge cases. Adopt it when billing administration is genuinely eating your time — not before.
4. Orb & Metronome — enterprise-grade, probably not yet
Orb and Metronome are the tools AI and infrastructure companies reach for: event-level ingestion at massive scale, real-time spend dashboards, custom contracts, commitments and credits, finance-grade reporting. They are genuinely the best-in-class usage billing platforms — and they're built (and priced) for funded teams. As a solo founder you'll spend more time in sales calls than integration. Bookmark them for when you have revenue that justifies it.
5. Paddle & Lemon Squeezy — the merchant-of-record angle
Paddle and Lemon Squeezy solve a different problem: as merchants of record they handle global sales tax and VAT for you, in exchange for a higher percentage fee. Their usage-billing support is coarser than Stripe's — fine for credit packs and simple tiers, limiting for precise per-unit metering. If tax compliance is your biggest worry and your usage model is simple, they're viable; we compare them head-to-head in our Stripe vs Paddle vs Lemon Squeezy guide.
| Tool | Best For | Watch Out For |
|---|---|---|
| Stripe Billing | Most solo founders; per-unit & tiered pricing | Complex enterprise contracts |
| Lago | Open-source control; high event volume | Self-hosting ops burden |
| Chargebee | Many plans, coupons, dunning, billing ops | Extra system to reconcile |
| Orb / Metronome | Enterprise scale; AI/infra billing | Overkill below 7-figure ARR |
| Paddle / Lemon Squeezy | Global tax handled for you; simple tiers | Coarse usage metering; higher fees |
How to Choose: Three Questions
1. How precise is your metering? Prepaid credit packs and simple tiers work on almost anything — even a merchant of record. Precise per-unit billing (per API call, per GB) wants Stripe Billing or Lago.
2. What's your bigger risk — engineering time or tax compliance? If it's engineering time, stay on Stripe and let it do the aggregation. If it's international tax exposure, the merchant-of-record premium may be worth paying — do that math in our pricing guide context.
3. Do you actually need usage-based pricing at all? The honest answer for many products is a hybrid: a flat base plan plus usage overage. That model keeps revenue predictable, is fully supported by Stripe Billing out of the box, and avoids the "surprise bill" churn problem pure usage pricing creates.
Don't build your own metering pipeline "because it's just a counter." Usage billing has brutal edge cases — late events, retries and double-counting, plan changes mid-period, refunds against consumed usage. Every founder who rolls their own ends up rebuilding a worse Lago. Buy or adopt; don't build.
Setup Tips That Save You Later
- 1.Emit idempotent events. Give every usage event a unique ID so retries never double-bill. This is the #1 source of billing disputes.
- 2.Show customers their usage in-app before the invoice does. Surprise bills are the top churn driver for usage pricing.
- 3.Add a spend cap or alert threshold from day one — customers trust usage pricing far more when they can bound it.
- 4.Keep raw events for at least a year. When a customer disputes an invoice, you want receipts, not aggregates.
If you're on Stripe already, prototype your pricing with Stripe Billing usage meters this week — you can model per-unit and tiered plans without writing a billing engine. Only add another tool when you hit a concrete wall, not because a comparison post (even this one) made it sound necessary.
Still deciding on the pricing model itself? Read Usage-Based Pricing for Micro SaaS: Should You Actually Use It? for the data on when usage pricing helps and when it quietly kills conversion — and see what the rest of your stack should look like in the indie hacker tool stack guide.