lotus VS dj-stripe

I'm a cofounder at Lotus (https://github.com/uselotus/lotus).

First, congrats on the launch Lago. I've been very impressed with your ability to educate devs about the intricacies of billing and you are certainly pushing the entire space forward.

While you offer coupons and credit notes, there are features you don't have that we have prioritized and built, including, usage alerts, plan versioning, gauge metrics, custom sql etc. etc. Point being I think its unfair to say we are a subset of your product.

In addition, we have a 25+ year billing expert on our team who has been CTO of a startup processing $300 million a year.

Lastly, I don't think it's fair to make statements about our customers just because we haven't "announced" them yet.

Happy to chat more with anyone about our differences.

Sharing Lotus, a universal pricing and packaging system that is written in Django/python. Very excited about this project and having an open-source monetization engine in the python ecosystem. https://github.com/uselotus/lotus

Show HN: Lotus – Open source pricing and packaging infrastructure\ (24 comments)

If you don't want to use Pegasus or another paid product (presumably because of the cost), the packages I'd reach for are django-allauth for login/user stuff and dj-stripe for the Stripe integration. As for teams, there wasn't a library I was happy with so I rolled my own for Pegasus, but some people like django-tenants. It's too heavyweight for my taste as it requires a more complex dev/test/infrastructure setup with Postgres schemas, as opposed to having a single-database and handling multitenancy in the application layer. But there are pros and cons to both approaches.

dj-stripe, Django library for Stripe, released a long awaited version 2.7, which features full in-db management of webhook endpoints through the admin, multiple endpoints per install, and more.

I would also recommend using dj-stripe to help with syncing payment intents and setting foreign keys to the whole payment intent object since it also will handle updates via webhooks for you. https://github.com/dj-stripe/dj-stripe

Just gonna leave this here: dj-stripe

Add Stripe to your site via dj-stripe. That will help you manage customers and plans. I strongly recommend focusing on integrating Stripe Checkout, as you won't have to handle any cards or anything like that. Unfortunately, I did not yet write a guide about that :( And I haven't found a good one online that will go into details, step by step.

I make it a point to check the current status and state of issues and pull requests for djstripe before updating or modifying the surrounding codebase codebase for every project I have that uses the module itself.

Nice work. Why start from scratch, instead of building atop https://github.com/dj-stripe/dj-stripe?

Django 4.0 support has been added in the master-branch as stated in https://github.com/dj-stripe/dj-stripe/issues/1507 But… this has not been released to pypi yet.

You might also want to take a look at the dj-stripe library: https://github.com/dj-stripe/dj-stripe