Usage-Based Billing Infrastructure After Stripe Acquired Metronome
Stripe's acquisition of Metronome consolidated usage-based billing under one payment giant, and Metronome announced it will focus only on its largest customers. This leaves mid-market SaaS companies needing consumption-based pricing (API calls, active users, compute time) without a vendor-neutral option. Lago is open-source but complex. Reddit's r/SaaS shows growing frustration with per-seat pricing models that customers reject.
The Metronome acquisition is your window. Every Metronome customer below their new 'largest customers' focus threshold is evaluating alternatives RIGHT NOW. Ship a Lago-based managed service: host the open-source engine, add a no-code pricing model builder, and charge a percentage of metered revenue. You get Lago's engine without asking customers to self-host it.
landscape (4 existing solutions)
The Stripe-Metronome acquisition centralized usage billing under Stripe's umbrella, creating vendor lock-in concerns. Orb targets large-scale infrastructure companies. Lago is open-source but requires billing engineering expertise. The gap is a mid-market usage billing tool: easier than Lago, cheaper than Orb, and not locked to Stripe. Think 'Stripe Billing but actually good at usage-based pricing' as a standalone product.