[btown]

This is an alternative to Stripe Billing, not the core Stripe payment rails themselves. In fact, one would use Stripe or similar with Lago: https://docs.getlago.com/guide/payments/overview .

Tracking the edge cases around recurring payments, invoicing, pro-rated tier changes, and metered billing is hard! And Stripe Billing APIs aren’t the most fluent for many cases. It’s good to see new layers in the space.

[lucw]

Right Lago could be used as replacement to Stripe Billing. And one attractive feature is that it decouples your tech stack from Stripe (could use another payment processor and still handle the subscription lifecycle the same way). This is going to be more and more interesting to businesses who are getting increasingly wary of Stripe account bans.

[btown]

Yep, couple it with a third party vaulting solution like Spreedly or VeryGoodSecurity and you can dynamically route any card-on-file to any payment processor with a simple configuration change, including routing higher-risk/newer accounts to less ban-happy processors. Honestly surprised that space hasn't innovated more around this offering.

[squigglydonut]

What are you talking about Stripe is great and really well made. I just built on it and was able to do whatever I wanted. Lago looks like just one more platform I'd have to keep track of for no reason.

[TheCapeGreek]

Then it's evidently not for you, if the use case benefit isn't apparent? Same reason you personally wouldn't use Chargebee but others might.

[squigglydonut]

What's your point?

[TheCapeGreek]

That when you say "Lago looks like just one more platform I'd have to keep track of for no reason", it clearly means it's not for you, but there might be other users who get benefit from it.

Surely that's obvious?