awesome-saas-boilerplates VS django-allauth

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.

django-allauth - authorisation with email and social media accounts

Complete user authentication (Log-in/Log-out, ...) via Django Allauth

I've been screwing around with https://github.com/pennersr/django-allauth/. I got it up and running; was able to get Discord and Twich oauth2 working on it without much issue, Steam's OpenID implementation is really giving me a hard time though.

Usually when people talk about oauth with django, they mean letting users access a django app using oauth and django-allauth is often a good choice for that, but if you're accessing an API that doesn't sound like what you're after.

When I started web development with Django. I thoroughly didn't know about the django-allauth package. I had knowledge of MVC and some core parts of Django. During college projects I had been working on a demo project and done user authentication and all manually. That time one of my seniors advised me to use django-allauth. I did some research and configured django-allauth with my project within a couple of minutes. For me it was an invigorating thing.

Although the answer given below solved my problem, I just want to share that I ended up using django-allauth instead of social-auth. And the latest version of django-allauth appears to be the best Django authentication app.