awesome-saas-boilerplates VS dj-stripe

Amazing to see more options in the market! Consider adding your solution to: https://github.com/smirnov-am/awesome-saas-boilerplates .

I'm obviously biased, so take what I say with a grain of salt, but I also probably know more about this space than ~anyone else. I'd say that your characterization is pretty accurate. There are many similar products to Pegasus (you can find a pretty comprehensive list here: https://github.com/smirnov-am/awesome-saas-boilerplates) but most of them are either more focused on infrastructure/setup (e.g. cookiecutter-django or - as you noted - far less mature/maintained (most of the others on that list).

Don’t worry about technology too much. Google for “SaaS boilerplate” and use one that suits your existing skills. Example: https://github.com/smirnov-am/awesome-saas-boilerplates

https://github.com/smirnov-am/awesome-saas-boilerplates collects such frameworks, it lists 4 for Rails.

If you end up building one, please add it to https://github.com/smirnov-am/awesome-saas-boilerplates

I think what you're describing is an entire product category, often referred to as a "SaaS boilerplate" or a "SaaS Starter". There are a huge number of them, and you can find lists of them on github as well as places like starter.place.

https://github.com/smirnov-am/awesome-saas-boilerplates There are also some golang based

Skip team features until a customer (or somebody ready to pay) is asking for it. In our B2B SaaS we have Fortune 100 companies as customers and even they are so far fine with individual accounts. We implemented two-factor-auth after customer requests but it's shocking how few of our users actually switch it on, definitely not relevant to grow or get more sales.

Start with a framework that includes authentication. It will save weeks of work. https://github.com/smirnov-am/awesome-saas-boilerplates

Good luck for your MVP/launch.

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