Chargebee is a SaaS subscription billing and revenue platform that stores card tokens in the payment gateways it connects. Pages here cover replacing it with self-hosted Lago or Kill Bill.
Comparing Chargebee with Lago, the AGPL open-source billing engine: subscriptions, usage metering and invoicing, payment collection through Stripe, Adyen or GoCardless, accounting integrations, what Chargebee's revenue and retention modules add, and running Lago yourself.
Comparing Chargebee with Kill Bill, the Apache-licensed Java billing and payments platform: catalogs, subscriptions, invoicing and payment plugins, the Kaui back office, and the engineering a Kill Bill deployment needs compared with Chargebee's managed service.
Moving subscription billing from Chargebee to Lago: exporting customers, subscriptions and invoices, rebuilding plans and usage metrics, keeping card tokens with the existing gateway, and running both systems in parallel through a billing cycle.
Moving from Chargebee to Kill Bill: mapping plans and add-ons to a Kill Bill catalog, importing accounts and subscriptions through its APIs, connecting the gateway that holds your card tokens through a payment plugin, and cutting over without double billing.
Cost of ownership by component: Chargebee's billing plans and add-on modules, against Lago's free open-source edition or Enterprise plan, servers, PostgreSQL and Redis, migration, payment gateway fees that stay either way, and the people who run billing.
What Chargebee lets you export, entity by entity as zipped CSVs or through the API, how long exports stay available, why card data stays with your gateway, and the order to move cards and billing data when you leave.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.