Lago vs Chargebee: Open-Source Billing vs a Subscription-First Suite

Lago vs Chargebee

Lago is open-source usage-based billing infrastructure you can self-host or run on Lago Cloud. Chargebee is a closed-source, cloud-only subscription revenue platform built for recurring billing, dunning, and RevRec. Both handle usage-based billing today. The difference is what each was built for first: Lago metered usage from day one, Chargebee added it on top of a subscription core.

If you're evaluating both, the honest framing is this: Chargebee is the more mature product for dunning, retention workflows, and finance-owned RevRec. Lago is the one where you can read the rating engine, run it on infrastructure you control, and keep billing logic independent of a managed suite's release calendar.

What each platform actually is

Lago is open-source: metering, rating, invoicing, prepaid credits and wallets, entitlements, subscription management. AGPLv3 license, code on GitHub. Deploys self-hosted or on Lago Cloud.

Chargebee is a mature, cloud-only SaaS revenue platform: subscriptions, usage billing as an add-on, invoicing, dunning, RevRec, and accounting integrations with NetSuite, QuickBooks, and Xero. It's sales-led and built for a finance-and-operations buyer, not an engineering one.

Neither of these is a value judgment, and it's worth saying that upfront. Chargebee is genuinely good at what it does. The real difference is architectural: Lago is a control layer that sits close to your product and your data. Chargebee is a managed suite that sits between you and your billing logic. For a lot of teams that trade is exactly right. For others, once pricing gets complicated, it's the problem.

Deployment: self-hosted vs. cloud-only

Lago runs on your own infrastructure or on Lago Cloud. Chargebee is cloud-only. There's no self-hosted option in its public documentation, and nothing suggesting that's changing. We've gone deeper on this trade-off, and when data sovereignty specifically forces the self-hosted decision, in Self-Hosted vs. Cloud Billing.

For most subscription SaaS companies, this doesn't matter much. For healthcare companies under HIPAA, financial services firms with data residency mandates, and government contractors under security review, it's disqualifying regardless of how good the rest of the product is.

Self-hosted Lago means the billing database, the webhook infrastructure, and the rating engine's source code sit under your control. AGPLv3 means the code is auditable, which matters when a billing bug has direct revenue and compliance consequences, not just a support ticket.

Subscription and dunning: Chargebee's real strength

This is the section to be honest about, the same way the Lago vs Metronome comparison is honest about enterprise contracts being Metronome's real strength. Chargebee's dunning and retention tooling is mature: smart retry logic, failed-payment recovery sequences, in-app and email dunning flows tuned over years of subscription businesses churning less because of them. Its RevRec module handles ASC 606 and IFRS 15 out of the box, which matters a lot when finance, not engineering, owns the billing relationship.

Lago supports dunning and retry logic too, but if your primary requirement is deep, finance-configured dunning workflows at Chargebee's level of polish, that's a real gap, not something to argue around. The question worth asking honestly: is subscription retention your core billing problem, or is it usage metering that Chargebee happens to also do?

Usage metering and event ingestion

Chargebee handles usage billing fine. This isn't a "Chargebee can't do it" argument. It was built subscription-first, and usage billing got layered in afterward, and that shows up in a few specific places.

Lago ingests through REST, batch, SDK, Kafka, Redpanda, Kinesis, and S3, all part of the same usage metering layer. Chargebee supports a usage API, bulk import, and CSV upload. For simple periodic overages, both work fine. For high event volume or a streaming pipeline, Lago's ingestion options are meaningfully broader, and the pipeline being open-source means custom deduplication logic gets built directly into code your team owns instead of requested from support.

Custom aggregation is the other place it shows. Lago supports weighted sum and fully custom aggregation logic, which matters for AI billing where a "token" isn't one unit, input, output, and cached tokens carry different costs in pricing tiers like Mistral's. Chargebee covers standard metered patterns well but needs workarounds for that kind of model-specific math.

Prepaid credits and entitlements

Lago's wallet is native to the billing and entitlement system: credits that expire and roll over on configurable schedules, real-time consumption alerts, and a direct connection to entitlements, so when a balance hits zero, product access changes immediately because the wallet and the entitlement layer are the same system.

Chargebee's credit model leans toward included-usage allowances and overages rather than persistent wallet balances, and its usage billing is invoice-time, not real-time. For AI companies where credit packs are the actual pricing mechanism, buy a million tokens, watch it draw down, auto-renew at zero, that's an architectural gap, not a checkbox Chargebee is missing by oversight.

Pricing: what you actually pay

Lago's open-source core is free to self-host; you pay for your own infrastructure and the engineering time to run it. Lago Cloud is a flat monthly fee that doesn't scale with revenue.

Chargebee's pricing is sales-led and not published. Market expectation is a fee that scales with revenue or transaction volume, with exact terms depending on your contract. The crossover point where a flat-fee platform gets cheaper than a revenue-scaled one typically lands somewhere in the $3 to 5M ARR range. Below that, managed platforms often win on cost. Above it, flat-fee or self-hosted usually does.

Lago vs Chargebee: feature comparison

When Lago is the right choice

Your billing model is usage-first: AI, API, or infrastructure products where tokens, calls, or compute seconds drive revenue. Self-hosted deployment is a requirement, not a preference. PSP neutrality matters on a multi-year horizon. Credit and entitlement logic needs to move in real time, not just be tracked accurately at invoice time. You're past roughly $3 to 5M ARR and a flat fee beats a revenue-scaled one.

When Chargebee is the right choice

Subscriptions or flat fees are most of your revenue, with usage as a secondary layer on top, which is exactly what Chargebee was built for. Finance owns the billing project and wants native RevRec and mature dunning without building it. You want one vendor covering billing, retention, and accounting integrations with SLA-backed support, and self-hosting isn't a requirement for your business.

The honest read

Chargebee earned its reputation the regular way: years of subscription businesses running dunning and retention through it, and a RevRec module finance teams trust. Nothing about Lago being usage-native changes that.

What's changed is which billing problem you're actually solving. If it's subscription retention with usage as an add-on, Chargebee's depth there is real. If it's metering complex, high-volume usage with billing logic your team wants to own and audit, that's the gap Lago was built for, and it's a different starting assumption than Chargebee's.

For the wider field of Chargebee alternatives, Lago's roundup of the top 7 covers it. For a deeper look at exactly this matchup, including a real migration timeline and where engineering-led teams specifically hit Chargebee's ceiling, see Chargebee Alternative? Why Engineering-Led Teams Choose Lago.

Mistral and Blacksmith run usage-based billing on Lago. Read the documentation, deploy the open-source version, or book a demo to walk through your pricing model.