Hacker News Reader

The value prop is composability, extensibility, building trust, and no lock in into Stripe’s ecosystem More details here: https://www.getlago.com/resources/compare/lago-vs-stripe

Yes we’d love feedback on our UX/UI as well!

View on HN

Did you guys implement versioning and grandfathering yet? Iterating on pricing and packaging without overwriting the whole config and f-ing up existing subscriptions is important.

I remember when I last time looked into lago, there was no versioning and the json configs were unintuitive and difficult to use. (I think it was also impossible to create a metered usage with a fixed one time fee$

Reply on news.ycombinator.com