SuperTokens Community VS saas-express-starter-kit

I get what you are trying to do, but it feels a bit insecure. Why not use an OSS passwordless project like https://github.com/supertokens/supertokens-core/ or https://github.com/teamhanko/hanko

Checkout https://supertokens.com/ - open source alternative to Auth0. It has a lot of free features and if you self host it, it's free at any scale. For our managed service, it's still far cheaper compared to Auth0.

SuperTokens

Building auth for your SaaS product shouldn't be hard. Try these free solutions for your next project 👇 http://supabase.com/auth free up to 50k users/month http://firebase.google.com/products/auth free up to 50k users/month http://aws.amazon.com/cognito free up to 50k users/month http://clerk.com free up to 10k users/month http://kinde.com free up to 7.5k users/month https://www.descope.com free up to 7.5k users/month https://supertokens.com free up to 5k users/month Save for later! Besides users/month what other features do you look for in auth products?

The Developer-First Security Week event is on August 7-11. The theme is shifting left with a security mindset with top expert speakers from Snyk, BoxyHQ, Microsoft, Google, Gitlab, Bearer, SuperTokens, Cerbos, and more...Come learn with us as the speakers dive into complex topics on Authorization, Authentication, Data Privacy.

Supertokens dont reinvent, just reuse

GitHub: https://github.com/supertokens/supertokens-core Website: https://supertokens.com/

Signing up - You're not actually signing up to anything. Supertokens (open source auth provider) is running locally on your machine. It's just a means for you to be able to have an account (and soon invite others to your project to collaborate together). The data doesn't leave your computer.

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