I would be very interested to know how Lotus compares to Lago too. I’m just about to start using something like this and was leaning towards Lago but was also considering killbill.
That being said, Lotus seems even more ideally suited for me (also a Postgres/Django app so kudos for that stack!).
The main thing I want is ability to centralize all subscription management despite customers potentially using different payment processors (eg stripe vs PayPal or crypto). It certainly looks like Lotus does this as well. I guess I’ll dive in to see how difficult it might be to add a custom payment processor (eg crypto payments), but I definitely think I’m leaning more towards using Lotus now. Thanks for making this!
We actually tried to build our payment processing infrastructure in a pretty modular way to make it super quick to integrate new processors. You can take a look at the extensibility guide here: https://docs.uselotus.io/docs/extensibility/integrate-paymen...
We'll be working on adding more options in the next weeks, but in the meantime if you need it ASAP we're happy to work with you to make it happen :)
I see one key difference in that we are focusing on pricing+packaging as a combined problem. We include the ability to add feature entitlements and usage limits in your plans and then programmatically check whether a customer has access to something based on the plan they are currently on. This augments your existing authorization system. It is a different approach than what Lago looks like they are going for and they don't support this now.
We also operate under an MIT license vs AGPL it looks like. So our business models may differ in the future. Looks like they definitely have some features we don't cover yet as well. Seems like a great project!
