Does self-hosting Lago cost less than Chargebee for your billing?
A finance or platform leader facing a Chargebee renewal or pricing change usually wants one answer: does Chargebee cost less to keep, or does self-hosted Lago cost less to run? Lago's free open-source edition removes the Chargebee subscription line, but it does not remove the Chargebee cost of running billing. Those costs move to your own infrastructure and team. Servers, PostgreSQL for application data, Redis as the job queue, and Gotenberg for PDF generation all need hosting, patching, backups and monitoring. The implementation partner, the migration of customers, subscriptions and invoices, and the internal staff time to operate billing replace the software fee with recurring and one-time labor. Lago's FAQ describes a forever-free edition with fundamental billing features and Enterprise plans that add premium features. The Enterprise price is not part of the facts we can cite here, so ask Lago for it in writing and check which features your renewal depends on.
Payment gateway fees stay under both options. Lago calculates what to charge and when, then sends the charge to a payment processor such as Stripe, Adyen or GoCardless, so processing fees, chargeback costs and card-network fees do not disappear when you leave Chargebee. The same applies to Chargebee, which also depends on a gateway. Confirm with your current gateway whether card tokens can move, because a move changes who holds the vaulted cards and may add export fees or effort. Do not compare the two totals without including the gateway line on both sides.
The honest answer depends on your own numbers. Build a three-year model with separate lines for Chargebee plans and add-on modules, Lago Enterprise if needed, hosting for the Docker Compose components or a Helm deployment at larger scale, database and Redis operations, the implementation quote, the migration, parallel running through a billing cycle, and the share of staff time that billing operations will consume. Ask each vendor and partner for a written quote tied to a fixed scope. The break-even point is most sensitive to how many engineers and finance operators you must keep on billing duty, and to how much of Chargebee's add-on functionality you actually use.
Which cost components change when you move from Chargebee to Lago
This table sets each cost component of Chargebee against the matching component of a self-hosted Lago deployment, and marks whether it is one-time or recurring. Read it as a checklist of who gets paid for what, because several lines, especially payment gateway fees and billing staff time, stay on the books after the move.
| Cost component | Commercial side (Chargebee) | Self-hosted side (Lago) | One-time or recurring |
|---|---|---|---|
| Billing platform subscription | Chargebee plan and add-on modules, priced by the vendor; confirm module scope and any usage tiers in your contract | Lago is AGPLv3 open source with a free edition for core billing; Enterprise plans add premium features, so confirm which features you need | Chargebee recurring; Lago free edition has no license fee, Enterprise recurring |
| Application servers | Included in the vendor's hosted service | Compute for the front end, API, API worker and clock worker, sized to event volume in your cloud or data center | Recurring infrastructure cost |
| PostgreSQL | Not visible to you | Holds Lago application data; use a managed or well-run instance with backups and tested restores | Recurring; setup one-time |
| Redis | Not visible to you | Used as Lago's job queue in the Docker Compose stack; size and monitor it alongside workers | Recurring; setup one-time |
| Gotenberg for PDF generation | Invoice PDFs produced by the vendor | Included in the Docker Compose stack; runs as a service you operate and patch | Recurring infrastructure cost |
| Optional ClickHouse | Not applicable | Off by default; only add it if high-volume event storage is needed, which adds a separate database to run | One-time setup and recurring if enabled |
| Payment gateway fees | Paid to the gateway (such as Stripe, Adyen or GoCardless) under your own agreement | Unchanged: Lago calculates charges and hands payment to a gateway you still contract with | Recurring, per transaction; does not disappear on migration |
| Implementation and configuration | Vendor onboarding and internal setup of plans and add-ons | Installing, pinning a tagged Lago version, configuring gateways, tax and accounting integrations | One-time, scope-dependent |
| Data migration and parallel running | Export of customers, subscriptions and invoices, plus running both systems through a billing cycle | Import work and duplicate operating effort until cutover, which is often the largest one-time item | One-time |
| Upgrades and ongoing support | Included in the subscription | Your team or a support partner applies tagged releases, patches databases and monitors the stack | Recurring |
| Billing and engineering skills | Internal staff manage the vendor's admin and integrations | Staff need skills for Lago operations, PostgreSQL, Redis and billing rule changes | Recurring staff time |
What moves the Chargebee versus Lago comparison
Six drivers decide whether self-hosting Lago costs less than Chargebee for your billing volume. Each one moves a different cost line, from infrastructure and licensing to the staff who keep billing running.
Invoice volume and event throughput
Invoice count and usage event rate set the size of the PostgreSQL, Redis and worker tier. Lago's Docker Compose stack includes PostgreSQL for application data and Redis as the job queue, and ClickHouse is an optional store for high-volume events that is disabled by default. Ask your team to model peak event rates per minute and monthly invoice runs before choosing sizing, because a high-volume usage model is what makes ClickHouse worth its added operating cost.
Enterprise features versus the free edition
Lago's open-source edition is free and covers fundamental billing features, while Enterprise plans add premium features at a cost you negotiate. If your Chargebee plan relies on revenue, retention or advanced modules, list each one and check whether it sits in the free edition or the Enterprise plan. A gap in that list is the most likely reason the self-hosted total cost rises.
Payment gateways and their fees
Lago calculates what to charge and when, then sends the charge to a separate payment gateway such as Stripe, Adyen or GoCardless. Gateway processing fees stay the same whichever billing engine you run, so they do not offset the platform comparison. Count how many gateways you use and confirm each one's fee structure, since every extra gateway adds integration and reconciliation work.
Availability and on-call expectations
Chargebee runs as a managed service, while a self-hosted Lago stack puts uptime, patching and recovery on your team. The clock worker and job queue must keep running for billing cycles to close on time, so define the out-of-hours coverage you need before you compare staffing costs. Ask whether your organization will pay for a support contract with an outside vendor or will staff this in-house.
Accounting and CRM integrations
Lago lists integrations with NetSuite, Xero, Salesforce and HubSpot. If your finance or sales team depends on a Chargebee connector for a different system, that connector may need custom work to rebuild on Lago. Check each integration you use today against the Lago list, and estimate the build and test effort for any gap, including the ongoing maintenance of custom syncs.
Skills already on the team
The largest cost in a self-hosted billing stack is often engineering time, not servers. A team already fluent in Ruby on Rails, PostgreSQL, Kubernetes and payment reconciliation will spend less time on upgrades and incident response than a team that is new to these tools. Ask who will own upgrades, since Lago's docs recommend pinning the last tagged version rather than the latest image tag, and who will carry that work each release cycle.
What the Lago free edition and Enterprise plan change in the budget
The first budget question is which Lago edition you would actually run. Lago's own FAQ describes a forever-free open-source edition with fundamental billing features, and Enterprise plans that add premium features on top. The core platform is licensed under the AGPLv3, so the free edition carries no license fee, but the Enterprise plan is a separate commercial agreement with its own price. Ask Lago in writing which features sit in each tier, whether the Enterprise contract includes support or an SLA, and how pricing is set. Do not assume a figure from published material; request a quote tied to your metered events, number of plans and entities.
The license also matters if you change the code. Under the AGPL, distributing a modified version carries source obligations, and the AGPL extends them to software that users interact with over a network. If you modify Lago and offer the modified service to your customers or partners, the obligation to publish those changes may apply. Your legal team should confirm how this applies to internal use, to customer-facing portals and to any custom connectors you write, before you plan the engineering work. This review is a cost item in its own right and belongs in the migration budget.
Once you have the Enterprise feature list, compare it line by line with the Chargebee modules your finance and revenue teams actually use. Pull the current Chargebee invoice and mark which add-ons are live, such as revenue recognition, retention or dunning tools, and which are paid but unused. Then decide, for each live module, whether the free edition covers it, the Enterprise plan covers it, or your team must build or buy it elsewhere. That mapping turns a vague edition choice into a concrete cost line, and it shows whether the Enterprise plan changes the budget enough to matter.
How to build the Chargebee versus self-hosted Lago cost model
This sequence turns your own billing volumes, contract terms and infrastructure estimates into a three-year cost comparison that you can defend in a renewal or budget discussion.
Export twelve months of invoice and subscription counts
Your finance or billing owner pulls twelve months of Chargebee data: invoice counts by month, active subscriptions, usage events where you bill on metering, and the number of customers in each plan. Chargebee lets you export entities as zipped CSVs or through its API, so use the same export method for every month to keep the numbers comparable. You are done when you have a single sheet of monthly volumes that your platform team and your finance team both accept as the baseline.
List every add-on module on the current order form
Your procurement or commercial owner lists each subscribed Chargebee module and add-on from the current order form, with the billing term, the unit basis and the renewal date for each. Ask Chargebee in writing to confirm which features are included in your plan and which are priced separately, because the included set changes between editions. You are done when every line on the order form maps to a feature you actually use, and each unused module is flagged for removal in the comparison.
Price the payment gateway fees that stay
Your finance team takes the gateway agreements you already hold, such as Stripe, Adyen or GoCardless, and models the processing fees against your twelve-month volumes. Lago's FAQ states that businesses using Lago still need a separate payment processor, so these fees appear in both the current and the self-hosted scenario and should be treated as a shared line. You are done when the gateway total is identical in both columns of the model, with any card-token export or gateway change costs noted separately.
Size servers and databases with your platform team
Your platform or infrastructure team estimates compute, storage and backup for the Lago deployment in your own cloud account or data center. Lago's Docker Compose setup runs a front end, an API, an API worker, a clock worker, PostgreSQL, Redis and Gotenberg, with ClickHouse optional and disabled by default, and larger deployments move to Helm charts and dedicated workers. Ask your team to size each component against the volumes from step one, and note that the Lago docs recommend pinning a tagged version rather than the latest image. You are done when the team hands over a sized infrastructure list with a monthly run cost from your own cloud pricing.
Estimate engineering and on-call hours
Your engineering and finance leads estimate the recurring hours needed to upgrade Lago, patch the platform, monitor background workers, handle failed payment jobs and maintain integrations with your accounting and CRM systems. Lago's README lists integrations with NetSuite, Xero, Salesforce and HubSpot, and each one you keep adds maintenance work. Record hours by role and by month, and decide whether the work is covered by in-house staff or by a retainer. You are done when the staffing line shows who is paid, for what, and how often.
Add migration and parallel-run effort from a written scope
Ask implementation partners and your internal team for a written scope covering data export, plan and usage metric rebuilds, card token handling with the existing gateway, and running both systems through at least one billing cycle. Lago's source code is licensed under AGPLv3, and the Enterprise plan is a separate commercial line, so ask whether you need any Enterprise features and request that price separately. You are done when every migration item has a quote tied to a written deliverable, and each one is marked one-time or recurring.
Compare three-year totals side by side
Your finance team builds a three-year model with the current Chargebee costs, shared gateway fees, self-hosted infrastructure, staffing, Enterprise license if chosen, and one-time migration and parallel-run costs. Mark each figure with its source, whether it came from your invoices, a vendor quote, your cloud pricing or your team's estimate. Add a sensitivity row for volume growth, because usage-based pricing and infrastructure both change with volume. You are done when the model shows the three-year total for each option with every assumption traceable to a named source.
Where infrastructure and upgrade costs recur
Self-hosting does not remove the bill. It moves it from a Chargebee subscription to recurring infrastructure, patching and staff time. The recurring line items to model are production and staging servers, managed or self-run PostgreSQL and Redis, backups, monitoring, and the on-call rota that answers when the API worker or clock worker stops. Ask your team to price each of these as a monthly figure, because they continue whether or not you upgrade anything.
Upgrades are the cost most often underestimated. Lago's self-hosting guide recommends pinning the last tagged version rather than the latest image tag, so every move to a newer release is a deliberate change that someone must test, schedule and roll out. The project's releases illustrate the cadence: v1.54.0 arrived on October 6, 2026 and v1.55.0 on October 7, 2026, according to the GitHub releases page. Plan for a review of each tagged release, a staging run against your own plans and invoices, and a rollback path. Confirm with the vendor how breaking changes are announced and whether migrations need downtime.
Scale changes the work. Lago's documentation points larger deployments to its Helm charts and to dedicated workers, which means more manifests to maintain, more resource tuning and possibly more PostgreSQL capacity. Ask whether your target cluster and database tier can absorb that setup without new hardware, and who owns the chart values after go-live. Each of these items is a recurring effort, not a one-time project cost, so write them into the run budget with a named owner.
Questions buyers ask before comparing Chargebee and Lago costs
Is self-hosting Lago actually cheaper than paying Chargebee?
It can be, but the answer depends on components you must price yourself. Lago's Docker Compose deployment is open source under AGPLv3, so there is no license fee for the free edition, but you pay for servers, PostgreSQL, Redis, backups, monitoring and the engineers who run them. Chargebee's plan and add-on modules are a recurring vendor fee that covers the platform and its support. Build a side-by-side model with the same components on both sides, then add the payment gateway fees, which stay either way. Ask Chargebee for the exact fees for your plan and modules in writing, and confirm Lago's edition terms directly with Lago.
What work does our team have to do in-house after switching to Lago?
Your team owns the running system, so the work is ongoing rather than a one-time setup. It covers deploying and pinning a tagged Lago version, which Lago's self-hosting documentation recommends over the latest image tag, along with database operations, Redis job queue health, PDF generation, upgrades, security patching, backups and restore tests. Larger deployments move to Lago's Helm charts and dedicated workers, which adds Kubernetes skills. Billing logic such as plans, usage metrics and tax rules also stays with your finance and engineering staff. Estimate these hours with your own platform team before comparing against Chargebee's managed service.
How long does a migration from Chargebee to Lago take, and what drives it?
The timeline depends on how much of your billing data and logic must move, and no duration is set by this page. The main drivers are the number of plans, add-ons and usage metrics you need to rebuild in Lago, the volume of active subscriptions and historical invoices, how many accounting and CRM integrations you connect, and how long you run both systems in parallel through a full billing cycle. Your gateway and data export steps also affect the schedule. Ask any implementation partner for a written scope and timeline before work starts, and confirm import options with Lago and Chargebee.
Does switching to Lago remove our payment gateway fees?
No. Lago calculates what to charge and when, then sends the charge to a payment gateway, and Lago's FAQ states that businesses using Lago need a separate payment processor. The README names Stripe, Adyen and GoCardless as supported providers. Those processing fees continue whether billing runs on Chargebee, Lago or Kill Bill, so exclude them from the comparison of billing platform costs. Confirm the rates in your current gateway agreement and check how each gateway's card tokens and fees would be handled after a move.
Does Lago's free open-source edition cover what we need?
Lago's free edition covers fundamental billing features, according to its FAQ, and Enterprise plans add premium features. Whether that is enough depends on which capabilities you use today. Compare your current subscriptions, usage metering, invoicing, dunning, tax and revenue reporting against the feature list in Lago's documentation, and list any Chargebee add-on modules your team relies on for revenue or retention. Gaps found in that review are the basis for deciding whether an Enterprise plan is needed. Confirm exact feature availability with Lago before you commit.
What should a consultant's quote for a Lago migration include?
A useful quote lists scope, deliverables and timelines in writing before work starts, since most DeployOpen engagements are fixed-scope. Ask for the components covered: hosting design, Lago deployment and version pinning, PostgreSQL and Redis configuration, backup and restore, data migration of customers, subscriptions and invoices, plan and usage metric rebuilds, gateway connection, parallel-run testing and cutover steps. Also ask what is excluded, such as ongoing support, upgrades or continuous testing, which DeployOpen offers as retainers. DeployOpen does not publish a price list, so a quote follows from the written scope.
Can a team run Lago without outside help?
Yes, if the team has the skills and capacity to operate the stack long term. Lago is designed for self-hosting and its Docker Compose documentation covers the core services, but you must handle deployment, upgrades, database operations, job queue monitoring and billing configuration yourself. Outside help is often used for the one-time migration and for hardening, while the team takes over operations. Assess your engineers' experience with PostgreSQL, Redis and container platforms, and decide who will own on-call support for billing runs before choosing this path.
What happens to our card tokens during a move from Chargebee?
Card tokens are usually kept with your payment gateway rather than moved between billing systems. Lago does not store card data itself; it sends charges to a payment gateway such as Stripe, Adyen or GoCardless. In practice, you keep the existing gateway connection so tokens stay where they are, then map each customer's payment method to the new billing system. Chargebee's own export documentation covers what you can take out of the platform. Confirm with your gateway whether tokens can be used by Lago and how PCI DSS responsibilities change for your organization.
How DeployOpen scopes a fixed-price Lago cost and migration plan
DeployOpen plans, implements, integrates, hardens, backs up, documents and supports self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For a Chargebee cost comparison and Lago move, we start from a written scope that separates licensing, infrastructure, gateway fees and staffing so you can compare options on the same terms.
How we scope
- We inventory your Chargebee plans, add-on modules, usage metrics and invoice volumes before estimating any Lago work.
- We list every cost component in the written scope, including gateway fees that stay the same under either option.
- Engagements are fixed-scope, with deliverables and timelines agreed in writing before work starts.
How we build
- We deploy Lago from a pinned tagged release in your environment, with PostgreSQL, Redis and Gotenberg configured for your sizing.
- We connect your existing payment gateway, such as Stripe, Adyen or GoCardless, and confirm which card tokens stay with it.
- We run security testing on the deployment and map its controls to the evidence your compliance assessors will request.
How we hand over
- We document the architecture, upgrade path, backup and restore steps, and the monthly cost drivers for your finance team.
- We run parallel billing cycles with you so invoices from Chargebee and Lago can be reconciled before cutover.
- Your staff receive runbooks and walkthroughs so billing operations do not depend on DeployOpen after handover.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover.
- Retainer scope covers Lago version upgrades, dependency patching and periodic security testing of the billing stack.
- Changes to plans, metrics or gateway connections are scoped in writing before they are built.
