saas-express-starter-kit VS open-saas

So I have been working on a SaaS starter kit - a boilerplate code for a SaaS app, using node and express. Now that it has become useful to some people and the code is growing, I want to make sure thag the developer experience is not lost in an attempt to add more features. I thought having a clear project goals with principles(e.g. no opinion about styling) to follow will help with this. So here I have written down the goals and the principles that will make DevX better, need your feedback what other principles should I add? TIA

Best comment on how to structure your web app. There's a GitHub repo with boilerplate to follow this pattern

Agree. And that's where express boilerplate such as saas-express-starter-kit can become handy.

How will we do it within a week? We will use this starter kit template to start with common things structured and built out of the box (e.g. auth, email, events, etc.)

I choose Express, always. To speed up further, use the boilerplate - https://github.com/makeitcount/saas-express-starter-kit

It won't be a small discussion. Let's discuss this on the GitHub repo issues

For the even faster start, it also features Open SaaS - a 100% free and open-source boilerplate starter for React & Node.js. Just clone it and get a working app with auth, billing, Open AI API, user dashboard and more!

When building AI Blog Articles, I decided to get started as fast as possible. So I looked for a free boilerplate and stumbled upon Open SaaS, which used YC-backed Wasp. It is a full-stack React + NodeJS + Prisma that takes 8 hours to get started with.

In addition, their CLI can help you start faster too. By running wasp new, you can get yourself a custom template that fits your needs. For example, if you’re building up a new SaaS, you’ll probably find a fit with OpenSaaS or if you’re creating a more specific solution, an AI code generator can help you start quickly if nothing else fits.

9,500 stars and almost 3 years later, here we are today. Wasp is getting close to entering the elite 10,000 stars club on GitHub, next to the giants of the industry. The framework we started, and developed further with the invaluable feedback from the community, is being used by all kinds of developers - from weekend projects, to startups and top enterprises. Startups made with Wasp have been acquired. I just saw a job ad today on Upwork, where a company is hiring for Open SaaS (an open-source, free boilerplate starter for React & Node.js, powered by Wasp) developers 🤯.

These days, I'm building side projects, like Open SaaS pictured above, and working as a developer relations engineer.

Although some people could consider Wasp’s opinionated stance a negative thing, it is the driver behind Wasp’s numerous full-stack features. With Wasp, starting a full-stack project for a single developer or a small team is much easier, especially if you use one of the pre-made templates or OpenSaaS as your SaaS starter. Because the core of the project is well-defined, it is very easy to get started with a project and potentially, make your own full-stack SaaS in a couple of days! What’s also cool is the fact that most of the pre-existing knowledge of web developers for most of them still applies here, because the technologies that Wasp uses are established.

OpenSaaS – I was curious what the latest starter kit for building out SaaS apps looks like. I wrote my own a whole decade ago github.com/eddywashere/node-stripe-membership-saas.

We’ve launched 6 times on Product Hunt in the last 3 years, won “Top Product” awards (#1 and #5 of the day), and collected over 2,000 upvotes in total. We just finished our sixth launch with Open SaaS - an open-source alternative to $300+ SaaS starters, a week ago.

Hey,

a few people have asked me how we got our [open-source SaaS starter](https://github.com/wasp-lang/open-saas) to the front page of GitHub trending, so I thought I'd share the details:

1. started sharing a funny promo [video on twitter](https://x.com/hot_town/status/1752243248439910626?s=20) and reddit