Stripe Billing is Stripe's subscription and usage billing product, priced as a share of billing volume. Pages here cover moving the billing logic to self-hosted Lago or Kill Bill while keeping a payment processor.
Comparing Stripe Billing with Lago when Stripe stays as the payment processor: metering, plans and invoicing in Lago, the percentage-of-volume fee you stop paying, what moves out of Stripe and what stays, and running Lago yourself.
Comparing Stripe Billing with Kill Bill for teams that want billing logic in-house: catalogs and subscriptions, invoicing, the Stripe payment plugin, multi-gateway options, and the Java platform work Kill Bill adds.
Moving subscriptions and usage billing from Stripe Billing to Lago while keeping Stripe for payments: pulling subscriptions and invoices through the Stripe API, recreating plans and meters, linking existing Stripe customers, and switching invoice generation without double charges.
Cost of ownership by component: Stripe Billing's share of billing volume on top of processing fees, against Lago's open-source or Enterprise edition, infrastructure, migration and operations, and the volume at which the trade starts to matter.
For API and AI products sending large event volumes: what Stripe includes in its Meters API and when it points to Metronome, against Lago's event pipeline with optional ClickHouse storage, and the operating load of running metering yourself.
What you can take when billing or payments leave Stripe: subscriptions and invoices through the API, card data only to a PCI DSS Level 1 processor through Stripe's encrypted export, Link credentials that cannot move, and the order of steps.
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.