# 7 Best Lago Alternatives for Billing in 2026 (Open Source and Hosted)

> Compare 7 Lago billing alternatives across open-source and hosted options, weighing self-hosting cost, metering depth, and Merchant of Record coverage for SaaS and AI teams.
- **Author**: Deepak Jangir
- **Published**: 2026-09-12
- **Category**: Alternatives, Billing, SaaS
- **URL**: https://dodopayments.com/blogs/lago-alternatives

---

The billing engine is rarely the thing that breaks. Metering is accurate, invoices reconcile, and the plan model absorbs whatever pricing structure sales invented last quarter. What breaks is everything around it: the on-call page at 2am on the first of the month, the tax registration nobody owns, the payment integration that quietly stopped retrying failed cards.

That is the honest tension teams hit with Lago. It is a capable billing platform with open-source roots, and self-hosting is a genuine advantage if you have data residency requirements or a strong platform team. But "we run our own billing" is a commitment, not a checkbox, and the commercial tier ships a long add-on list behind a contact-us conversation. This guide compares 7 alternatives across open-source and hosted models, with the part most listicles skip as its spine: what self-hosted billing costs, and where a billing engine stops being enough.

## Quick Comparison: Lago Alternatives

| Platform | Model | Deployment | Pricing | MoR | Best For |
| --- | --- | --- | --- | --- | --- |
| **Dodo Payments** | MoR + usage billing + checkout | Hosted | 4% + 40c per US domestic txn, no monthly fee | Yes | Billing, payments, and global tax in one |
| Orb | Usage-based billing engine | Hosted | Custom, all tiers | No | Finance-led teams needing invoice-grade billing |
| Metronome | Usage-based billing platform | Hosted | Enterprise, contact sales | No | Large usage programs inside the Stripe ecosystem |
| m3ter | Usage-based billing | Hosted | Platform fee plus add-ons, contact sales | No | Mid-size and large B2B SaaS with complex contracts |
| Chargebee | Subscription management | Hosted | Published tiers plus overage | No | Hybrid subscription plus usage models |
| Stripe Billing | Billing layer on a processor | Hosted | Surcharge on Stripe fees | No | Teams already standardized on Stripe |
| Kill Bill | Open-source billing platform | Self-hosted | Open source, you run it | No | Teams committed to operating billing themselves |

## Why Teams Look for Lago Alternatives

Most teams that leave Lago are not leaving on quality. They leave on scope, cost predictability, or operational load.

- **Total cost is hard to predict before a sales call.** Lago Premium is available in both cloud and self-hosted deployments, but pricing is contact-us. With no public figures to model against, budgeting for year two is an estimate rather than a calculation.

- **Capabilities teams assume are core are add-ons.** Tax integrations, automatic dunning, progressive billing, premium ingestion sources, quotes and order forms, CRM and accounting integrations, custom branding, and 24x7 incident management are all add-on line items. Business hours incident management is included; round-the-clock is not.

- **Self-hosting is not free.** Somebody runs the database, applies upgrades, monitors ingestion lag, restores backups, and answers the page when invoices do not generate. That cost is denominated in engineering time.

- **Lago is not a Merchant of Record.** Tax handling is an integration, not assumed liability, so global registration, filing, remittance, and audit exposure stay on your side of the line. Our primer on [what a Merchant of Record actually covers](https://dodopayments.com/blogs/what-is-a-merchant-of-record) walks through the boundary.

- **There is no payment processing or checkout.** Lago integrates with payment providers rather than moving money itself, so you still need a gateway, a checkout surface, dispute handling, and a payout relationship.

## What Lago Does Well

Lago homepage describing its open-source billing platform available as managed cloud or self-hosted

_Lago's homepage._

Lago is one of the strongest options available if you need a billing engine you can run yourself, and the feature depth is not superficial.

The metering side is serious: billable metrics, usage ingestion, real-time usage alerts, lifetime usage calculation, and a data pipeline integration for your warehouse. Plan configuration supports custom pricing units and per-client overrides, which covers the messy reality of enterprise contracts better than most subscription tools. The commercial surface adds entitlements, prepaid credits, a customer portal, multiple billing entities, invoice preview, credit notes, an analytics dashboard, AI Billing and Finance Assistants, and an MCP server, alongside RBAC, audit logs, SSO via Okta, and SOC 2 Type II.

Deployment flexibility is the real differentiator. You can run Lago on-prem, inside a VPC, or wherever your compliance posture requires, which very few billing vendors permit at all. The public proof point is Mistral AI, whose CTO Timothee Lacroix has said Lago has been able to follow the pace of their releases and allowed the team to focus on what they do best.

## The Real Cost of Self-Hosted Billing

Self-hosting looks free on the invoice and expensive on the roster. Price the work honestly before picking a deployment model.

**Running it.** You operate a database that must not lose events, a queue that must not fall behind, and workers that must finish invoice generation inside a window finance already promised customers. That is a production service with an SLA, whether or not anyone wrote it down.

**Upgrading it.** Every upgrade needs a staging environment with representative data, a migration plan, and a rollback path. Skipping upgrades is not a strategy either, because the version gap compounds.

**Monitoring, backups, and security posture.** You need alerting on ingestion lag, invoice failures, webhook delivery, and drift between usage recorded and usage billed, plus backups you have actually restored rather than assume work. Even when the engine never touches card numbers it holds customer financial records, which pulls it into your security review scope and incident response plan.

**The on-call cost nobody budgets.** The first days of every month are the highest-risk window in billing, and somebody has to be awake for them. If 24x7 incident management is an add-on you did not buy, that somebody is one of your engineers. Two people rotating a billing pager is a meaningful fraction of a headcount that appears in no comparison.

**When self-hosting genuinely wins.** If regulation or a customer contract requires usage data to stay in a specific jurisdiction or your own VPC, self-hosting is the only clean answer. If metering volume is extreme enough that per-event pricing dominates your cost, running it yourself can be cheaper. And if your pricing logic requires patching the engine, open source is the only path that permits it.

Outside those cases the calculus usually favors hosted infrastructure. Our breakdown of [building a billing system for an AI SaaS](https://dodopayments.com/blogs/build-billing-system-ai-saas) covers the build-versus-buy math, and the common failure modes are catalogued in our guide to [billing system migration mistakes](https://dodopayments.com/blogs/billing-system-migration-mistakes).

## Where a Billing Engine Ends and an MoR Begins

Most comparisons treat "billing platform" as one category. Six stages sit between a usage event and money in your bank account, and vendors own different spans of that chain.

```mermaid
flowchart LR
    subgraph BE["Billing engine scope (Lago, Orb, m3ter, Kill Bill)"]
        A["Metering: ingest usage events"] --> B["Rating: apply plans and pricing"]
        B --> C["Invoicing: generate and issue invoices"]
    end
    subgraph MOR["Merchant of Record scope"]
        D["Payment collection: charge the customer"] --> E["Tax remittance: register, file, and pay"]
        E --> F["Payout: settle funds to your account"]
    end
    C --> D
```

A billing engine owns metering, rating, and invoicing, and it is very good at turning events into correct line items. What it does not own is the legal and financial layer: who is the seller of record, who is registered for tax in each jurisdiction, who is liable for a late filing, and who carries chargeback exposure.

A Merchant of Record owns that second half. It becomes the legal seller, remits tax where you sell, handles disputes, and pays you out. That is why "Lago plus a gateway plus a tax tool plus a compliance workflow" is a common stack rather than an unusual one. For a SaaS-specific view, see our guide on the [Merchant of Record model for SaaS](https://dodopayments.com/blogs/merchant-of-record-for-saas).

## 1. Dodo Payments

Dodo Payments homepage showing usage-based billing, checkout, and Merchant of Record coverage in one platform

_Dodo Payments' homepage._

Dodo Payments takes the opposite architectural bet from Lago. Instead of a billing engine you run and integrate, it collapses metering, rating, invoicing, checkout, payment processing, tax remittance, and payouts into one hosted platform where Dodo is the Merchant of Record. The entire chain above sits behind a single integration, and tax across 190+ countries is part of the platform rather than an add-on you configure and then own.

**Key strengths**

- Full Merchant of Record coverage, so global tax registration, filing, remittance, and liability sit with Dodo rather than your finance team
- Native [usage-based billing](https://dodopayments.com/billing/usage-based-billing) with event ingestion and metering included, not sold separately
- [Credit-based billing](https://dodopayments.com/billing/credit-based-billing) for prepaid and wallet-style models, mapping closely to Lago's prepaid credits
- Built-in checkout and payment processing with 40+ payment methods, 80+ currencies, and coverage across 220+ countries and territories
- Published pricing: 4% + 40c per domestic US transaction, +1.5% international, +0.5% for subscriptions, 4% + 15c for India domestic, and 0.5% for bring-your-own-processor
- No fixed monthly cost or setup fee, with invoicing, analytics, and tax compliance in the rate
- Predictable operational fees: $1 per refund, $30 per dispute, free payouts with a $5 fee only under $1,000
- Documented in the [integration guide](https://docs.dodopayments.com/developer-resources/integration-guide), plus an [MCP server](https://docs.dodopayments.com/developer-resources/mcp-server) for agent workflows

**Trade-offs**

- Hosted only. If you must run billing inside your own VPC or on-prem, Lago or Kill Bill fit better.
- A percentage-based MoR rate is a different cost shape than a platform fee. At high volume with thin margins, model both.
- If you want to keep merchant-of-record status yourself, the MoR model is broader than you need.

**Best for:** SaaS and AI teams that want metering, billing, checkout, and global tax as one product instead of four vendors. See the [pricing page](https://dodopayments.com/pricing) and the [Merchant of Record](https://dodopayments.com/payments/merchant-of-record) model breakdown.

## 2. Orb

Orb homepage describing its usage-based billing platform for high-volume event ingestion

_Orb's homepage._

Orb is a hosted usage-based billing engine for teams where billing accuracy is a finance requirement, not an engineering nicety. It handles real-time event ingestion and lets you define billable metrics in SQL. Plans are Core, Advanced, and Enterprise, all custom priced.

**Key strengths**

- Real-time event ingestion designed for high-volume usage data
- Custom SQL billable metrics, suiting teams with warehouse-native usage definitions
- Threshold billing and Orb Invoicing built in

**Trade-offs**

- Custom pricing on every tier means no self-serve start and no public number to budget against
- Not a Merchant of Record; tax is handled by integration and liability stays with you
- Hosted only, so it does not answer a data residency requirement the way Lago can

**Best for:** finance-led teams that need invoice-grade usage billing and accept an enterprise procurement cycle.

## 3. Metronome

Metronome homepage describing real-time usage-based billing for consumption products

_Metronome's homepage._

Metronome is a usage-based billing platform for high-volume consumption pricing, acquired by Stripe. Pricing is enterprise-only. Like Lago, it stops short of the financial layer.

**Key strengths**

- Mature metering and rating for large-scale consumption billing
- Well suited to teams already standardized on the Stripe ecosystem

**Trade-offs**

- Enterprise-only pricing with no published figures
- Not a Merchant of Record and no payment processing of its own
- Roadmap direction is now tied to Stripe, which matters if vendor independence drove your original choice

**Best for:** larger usage-billing programs comfortable inside Stripe's orbit. Our dedicated [Metronome alternatives](https://dodopayments.com/blogs/metronome-alternatives) guide goes deeper.

## 4. m3ter

m3ter homepage, now branded m3ter from Salesforce, describing usage-based billing infrastructure for CRM and ERP stacks

_m3ter's homepage, now branded "m3ter from Salesforce" following the acquisition._

m3ter is a usage-based billing platform for mid-size and large B2B SaaS with negotiated contracts rather than self-serve plans. Its commercial model is a monthly core platform fee sized to your needs, with allowances for usage data ingested and bill calculations performed, plus add-ons, support packages, and implementation services. No public figures are published.

**Key strengths**

- Built around the contract complexity that enterprise B2B deals actually produce
- Platform fee with defined allowances is a different cost shape than pure per-event pricing

**Trade-offs**

- No published pricing, and the total depends on add-ons, support tier, and implementation scope
- Not a Merchant of Record
- Implementation services are a real part of the engagement, so time to first invoice runs in weeks

**Best for:** mid-market and enterprise B2B SaaS with contract-heavy commercial models.

## 5. Chargebee

Chargebee homepage describing its subscription billing and revenue management platform

_Chargebee's homepage._

Chargebee is a mature subscription management platform that extended into usage. If your pricing is a base subscription with metered overages, it handles upgrades, proration, dunning, and revenue reporting well. Compared to Lago the emphasis is inverted: subscription logic is the core and usage layers on top.

**Key strengths**

- Strong hybrid handling of subscription plus usage in one plan model
- Mature dunning, revenue recovery, and reporting for finance teams
- Broad integrations across CRM, accounting, and gateways

**Trade-offs**

- Not a Merchant of Record; tax, compliance, and payment liability remain yours
- Metering is not the architectural core, so extreme event volumes fit poorly
- Costs stack once you add a gateway and a tax provider alongside it

**Best for:** scaling SaaS with hybrid pricing that needs subscription mechanics first. See our [Chargebee alternatives](https://dodopayments.com/blogs/chargebee-alternatives) comparison and our survey of [subscription billing platforms](https://dodopayments.com/blogs/subscription-billing-platforms).

## 6. Stripe Billing

Stripe homepage describing its payments and billing platform

_Stripe's homepage, whose Billing product is compared here._

Stripe Billing is the billing layer on top of Stripe's payment processing, and for teams already on Stripe it is the lowest-friction option available: no new gateway, no new reconciliation surface, one vendor. The distinction from an MoR is ownership. You remain the merchant of record, and while Stripe Tax can calculate tax, registration, filing, remittance, and liability stay with you.

**Key strengths**

- Zero additional gateway integration if you already process on Stripe
- Excellent developer documentation and a large ecosystem
- Subscription and simple metered models work out of the box

**Trade-offs**

- You remain merchant of record and own global tax compliance end to end
- Complex usage models often require custom engineering on top
- Fees stack across processing, billing, and tax tooling

**Best for:** teams already standardized on Stripe with straightforward billing needs. For a direct comparison of the metering layer, see [Stripe usage-based billing versus Dodo](https://dodopayments.com/blogs/stripe-usage-based-billing-vs-dodo).

## 7. Kill Bill

Kill Bill homepage describing open-source billing infrastructure priced at a fixed cost rather than a revenue percentage

_Kill Bill's homepage._

Kill Bill is the closest like-for-like to Lago's self-hosted model: an open-source billing platform with a long-running community that you operate yourself. It is plugin-oriented, so capabilities extend through community and custom plugins rather than purchased vendor add-ons.

**Key strengths**

- Genuinely open source with a long operating history and established community
- Full control over deployment, data location, and upgrade timing
- Plugin architecture allows deep customization

**Trade-offs**

- Every operational cost described earlier applies in full, with no vendor pager to escalate to
- Not a Merchant of Record, and payment collection requires separate providers
- Capability depth depends on which plugins you adopt and maintain

**Best for:** teams with a strong platform function that have already decided to own billing operations.

## Decision Framework: Which Lago Alternative Fits You?

Choose by constraint, not feature count.

**Do you have a hard requirement to run billing yourself?** If regulation or a data residency policy requires usage data to stay in your environment, the shortlist is Lago or Kill Bill. Nothing else here runs in your VPC. Accept the operational cost consciously and staff for it.

**If not, what stage are you at?**

- **Early traction.** Optimize for time to first invoice and for not hiring a billing engineer. A hosted MoR removes tax, gateway, and compliance work in one step; our walkthrough on how to [implement usage-based billing](https://dodopayments.com/blogs/implement-usage-based-billing) is a starting point.

- **Growth stage, self-serve heavy.** You need reliable metering, a checkout that converts, and someone else handling tax as you cross registration thresholds. An MoR is usually cheaper than the compliance headcount you would otherwise hire.

- **Growth stage, sales-led.** Contract complexity is the binding constraint. Orb and m3ter are built for it; budget for procurement and implementation.

- **Enterprise with an existing finance stack.** The question becomes ERP and revenue recognition depth, not metering. Chargebee and the enterprise suites compete here.

**Where does your compliance liability sit?** Only a Merchant of Record takes tax registration, filing, remittance, and chargeback liability off your balance sheet. A billing engine, however good, cannot. For a wider view, compare [flexible billing platforms](https://dodopayments.com/blogs/flexible-billing-platforms) and the [best billing platforms for usage-based pricing](https://dodopayments.com/blogs/best-billing-platform-usage-based-pricing).

## Migration Checklist: Moving Off Lago Safely

Billing migrations fail in reconciliation, not integration.

1. **Export billable metric definitions and plans first.** Inventory every metric, plan, pricing unit, per-client override, and add-on. Overrides are where the surprises live, since they are often created for one deal and never documented.

2. **Map every metric to the target platform's model.** Aggregation semantics differ. A metric that sums per period in one engine may count distinct values in another, so write the mapping down and have someone else review it.

3. **Replay historical usage events into the new system.** Replay at least one full billing period so you can compare rated output against invoices you already sent and know were correct.

4. **Run a parallel billing cycle and reconcile line by line.** Keep Lago authoritative while the new system shadows it for a full cycle, and compare at line item level, because offsetting errors hide inside matching invoice totals.

5. **Migrate wallets and prepaid credit balances deliberately.** Prepaid credits are customer money and the highest-risk part of any migration. Freeze balance changes during cutover, transfer exact balances, and confirm totals match your deferred revenue ledger. Our guide on how to [add credits to an AI app's billing](https://dodopayments.com/blogs/add-credits-billing-ai-app) covers the balance model.

6. **Cut over ingestion before invoicing.** Send events to both systems for a period, then make the new system authoritative for invoicing only after rating output matches.

7. **Confirm who owns tax registration after the move.** Moving to a Merchant of Record transfers tax liability and may change existing registrations; moving to another billing engine transfers nothing. Get this in writing before the first live invoice.

8. **Decommission self-hosted infrastructure only after a clean cycle.** Keep the Lago deployment restorable through at least one complete billing period after cutover, including month-end close, then snapshot the database per your retention policy.

## FAQ

### Is Lago free if I self-host it?

The open-source path has no license cost, but self-hosting is not free in practice. You take on engineering time to run, upgrade, monitor, and back up the deployment, plus on-call coverage at month end, and Lago Premium self-hosted is a commercial contract with contact-us pricing.

### Is Lago a Merchant of Record?

No. Lago is a billing engine, not a Merchant of Record. Tax handling is an integration add-on rather than assumed liability, and Lago does not process payments itself, so global tax registration, remittance, and chargeback exposure remain with your company.

### How much does Lago cost?

Lago does not publish pricing. Lago Premium is available in both cloud and self-hosted deployments with contact-us pricing, and capabilities including tax integrations, automatic dunning, progressive billing, and 24x7 incident management are priced as add-ons on top of the base contract.

### What is the best open-source alternative to Lago?

Kill Bill is the closest like-for-like option, since it is community-driven and you run it on your own infrastructure. Choose it if self-hosting is a hard requirement; if it is not, a hosted platform usually costs less once you price the operational work honestly.

### Which Lago alternative handles global tax compliance for me?

Only a Merchant of Record does that, and Dodo Payments is the one on this list. Orb, Metronome, m3ter, Chargebee, Stripe Billing, and Kill Bill all leave tax registration, filing, remittance, and liability with your company, whether or not they offer tax calculation.

## Final Take

Lago is a good billing engine and a rare one, because very few vendors let you run billing inside your own infrastructure at all. If data residency or deep control is a hard constraint, it belongs at the top of your shortlist and the honest comparison is against Kill Bill, not against hosted platforms.

For everyone else, the question is not whether Lago's metering is good enough. It is whether you want to own the operational surface at all: the upgrades, the month-end pager, the tax registrations in countries you have never visited, and a contract whose total depends on which add-ons you end up needing.

Dodo Payments takes the other side of that trade, bundling metering, invoicing, checkout, payment processing, and tax remittance across 190+ countries into one platform at 4% + 40c per domestic US transaction with no monthly fee. The [developer documentation](https://docs.dodopayments.com) covers the API surface, and our overview of [usage-based billing for SaaS](https://dodopayments.com/blogs/usage-based-billing-saas) explains the pricing model itself.
---
- [More Alternatives articles](https://dodopayments.com/blogs/category/alternatives)
- [All articles](https://dodopayments.com/blogs)