What this is
The stack popularised by Marc Lou and codified in his ShipFast Next.js boilerplate. Hundreds of indie SaaS launched in 2024, 2026 use a near-identical configuration; Marc himself documents it relentlessly on Twitter and in his email course.
When to pick this stack
- You’re shipping an indie SaaS solo or with a tiny team and want to go from idea to paid in days, not months
- You’re comfortable with JavaScript/TypeScript end-to-end (Next.js front and back)
- Schema-flex matters more than relational integrity, most indie SaaS data fits MongoDB’s document model fine, and the lack of schema migrations is a real productivity win in the early weeks
What we’d swap
- MongoDB Atlas → Supabase Postgres: if you’ll need relational queries, joins, or row-level security later, swap to Postgres now. Supabase wraps Postgres + auth + storage; you can drop Clerk too in that case.
- Clerk → Supabase Auth: if you’re already on Supabase. Clerk’s UX is better but you’re paying for it; Supabase Auth is good enough for most B2C SaaS.
- Resend + Mailgun → Loops: if you want transactional + marketing in one tool with a campaign builder, Loops fills both roles for SaaS-style emails.
Common gotchas
- Stripe webhooks need a public endpoint, Vercel preview URLs work for testing but production needs a stable URL with idempotency handled correctly.
- MongoDB free-tier instances pause when idle. Fine for personal projects, awkward when a real customer hits a cold-start delay.
- Clerk’s pricing scales with monthly active users. Past ~10k MAU the bill matters; some teams switch to Supabase Auth at that point.