awesome-saas-boilerplates VS zero

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.

Many "startup starting guides" or "startup in zero steps" guides recommend using no-code or zero setup frameworks to build your product. They recommend getting started as fast as possible, acquiring users, then thinking about the technical implications of your choices down the road. These are really good tips. In fact, I strongly recommend looking at frameworks like getzero to get started as fast as possible if you're a more technically oriented person. What most of these guides/frameworks omit is that you should probably already be proficient in the platform they recommend before you even start. Building an entire product on Bubble is more than possible, but in my case, I am a very technical person. My strength lies in building backends, APIs and DevOps workflows.

There are some good open source options like https://getzero.dev/

Commit's Chief Architect - formerly at Hootsuite - manages an open source project Zero (https://github.com/commitdev/zero). As part of regular maintenance, he was trying to make a switch to using Amazon Web Services’ Network Load Balancer from their “Classic” Elastic Load Balancer. NLB is billed as AWS’s next generation of load balancers. He was hoping for a better experience than he's had with ELB—although my experience with ELB has been mostly positive, as it tends to be fairly fast and stable. We’ve been using ELB with Kubernetes for quite some time, and he's fairly confident in how these technologies work together.