SStackforge
← Back to all posts

Why I Built next-supabase-saas

buildinpublicsupabasenextjs

Motivation

I've built two SaaS projects with this exact stack. Both times, the hardest part wasn't writing the business logic — it was the setup.

Keys scattered across five different dashboards. Supabase's service_role, R2's secret (shown only once), Modal's token, OAuth callback URLs…

The first time, it took me most of a day. The second time, still one to two hours.

What I built

v0.1.0 is out: a /setup panel that puts everything in one place.

The goal

Let the next person go from clone to running app in 30 minutes — not a full day.

What's next

  • Connection tests for environment variables
  • MySQL → Supabase migration workflow
  • Google / GitHub OAuth setup guide