I kept rebuilding the same auth and billing code for every SaaS project, so I packaged it !
It's a React + Vite + Supabase + Stripe starter kit with everything already wired together:
- Sign up / sign in / password reset
- Protected routes
- Stripe billing with customer portal
- Real-time notifications
- Avatar upload
- SQL schema with RLS policies
- 3 Supabase Edge Functions ready to deploy
You drop in 4 environment variables and you're building your actual product on day one instead of day four.
Does this product have some a connection with supastarter .dev?
I'm using it and I'm surprised as both have same names and do similar things...
Hey Nijinsky23 - SupaStarter solves a clear pain: rebuilding auth and billing before every Supabase SaaS idea. One small copy thought: make the first screen lead with that repeated-work pain before the stack list. If useful, I can do a tiny $2-$3 homepage copy note: 2-3 hero/CTA wording tweaks plus a short before/after note. Small fixed scope, no big audit.
Nice job! I recently built a webpage where I used these components except for Stripe. Does your project support LemonSqueezy too? Stripe is not available in my country.
Most developers lose the first week of every project just wrestling with auth redirects and Stripe webhooks before they even write a single line of their actual product code. It is incredibly draining to keep reinventing the wheel for basic features like password resets or protected routes when you just want to ship. Since you have pre-configured the SQL schema with RLS policies, how much flexibility do users have to modify the core database structure without breaking the built-in auth and billing flows?
I've been spending ages playing around, building apps, none of which have really taken off, now someone else can try haha