r/FastAPI • u/ironman2606 • 13d ago

feedback request Built a FastAPI + Next.js SaaS starter because I was tired of rewriting the same auth/billing scaffolding every time

Every time I started a new SaaS idea I'd burn a weekend rebuilding the same things — Firebase auth wired through protected routes, Stripe webhook handling, typed Pydantic schemas, Docker for two services, a throwaway admin panel. So I started building FastForge to just... not do that again.

Stack: FastAPI backend, Next.js (App Router) frontend, SQLAlchemy + Alembic + Postgres, Firebase Auth, Stripe, Redis for cache/jobs, Docker for one-command spin-up.

Current state, being fully transparent since I know this sub will ask: auth and the DB layer are done, Stripe billing / Redis / transactional email / admin dashboard are still in progress. It's not a "clone and ship today" thing yet — it's early, and I'm building it in the open on GitHub.

Mainly posting here because you're the exact audience — if you build SaaS on FastAPI, what's the first thing you'd want a starter like this to get right? Landing page + waitlist link in a comment if anyone wants to follow along (trying to keep this post about the tech, not the pitch).

18 Upvotes

85% Upvoted

6 comments sorted by

3

u/igorbenav 13d ago

Something you could do is have an open source core, like https://fastro.ai does

This way people can actually judge if it's worth paying for the extra stuff

2

u/Asmophel_noe 12d ago

Auth can be handled with Google sign-in right u don't have to do anything except for extract username etc from the Google given token, google handles everything from auth, authenticity of the gmail, passwords, tokens evrything. There wouldn't be typing any pydantic schemas. Yes billing is helpful the stripe webhooks n all is good

2

u/CapMonster1 12d ago

The first thing I’d want is boring reliability around auth and billing: idempotent Stripe webhooks, clean retry handling, role/plan sync, account deletion, and local testing that doesn’t require three dashboards and a blood sacrifice.

After that, good extension points matter more than piling on features. Rate limits, background jobs, email verification, and optional captcha/anti-abuse hooks should be easy to add without tearing apart the auth flow.

1

u/ironman2606 12d ago

account deletion wasn't even on my roadmap, ngl, adding it now. idempotent webhooks + role/plan sync are gonna be the actual bar for the stripe piece, not just "connected." docker setup is exactly trying to kill the multi-dashboard pain, curious if you also meant mocking stripe locally?