I packaged the SaaS foundation I reuse for every Next.js project

After working on several SaaS projects (both personal and client work), I started noticing a pattern that probably isn’t unique:

Before I could even validate an idea, I was spending weeks rebuilding the same foundation every time.

Not “fun” product work — but the necessary stuff:

authentication and session handling

Stripe subscriptions and webhooks

email flows (verification, notifications, onboarding)

file uploads and storage

basic app and dashboard structure

None of this was hard individually, but stitching it together properly — in a way that felt production-ready and maintainable — always took longer than expected.

Over time, I ended up with a base setup that I reused and refined across projects. Eventually, instead of copying it forward again, I decided to clean it up, document it properly, and package it as a Next.js SaaS starter kit.

A few important clarifications up front:

This is not a hosted SaaS

It’s not no-code

You get the full source code and run everything yourself

The goal isn’t to hide complexity — it’s to remove repetition.

What I wanted (and built) was:

a clean, opinionated project structure

auth, billing, emails, and storage already wired together

something I’d actually be happy to maintain long-term

Basically: a foundation that lets you start building the actual product on day one, instead of re-implementing infrastructure again.

I recently launched it as SupaSaaS and I’m sharing it here because Indie Hackers is full of people who are exactly in this phase — starting or restarting SaaS ideas and trying to move faster without cutting corners.

Here’s the link if you want to take a look:
👉 https://get-supasaas.vercel.app/

Happy to answer questions about:

what’s included vs intentionally left out

how opinionated the structure is

whether this makes sense for solo founders vs agencies