Modern Indie SaaS Architecture (2026)
Default stack: Next.js + Supabase + Vercel + Resend, with the request flow drawn out
Modern Indie SaaS Architecture (2026)
The stack at a glance
Request lifecycle (a checkout, end to end)
Auth flow (Supabase Auth)
Why each choice (and what would change your mind)
Next.js + Vercel
Supabase
Lemon Squeezy (over Stripe)
# Modern Indie SaaS Architecture (2026) The default stack for shipping an indie SaaS in 2026, with the request flow drawn out, the costs spelled out, and the tradeoffs called out. Optimized for one-person teams that want to ship quickly, scale to ~$10K MRR before touching any of it, and keep cognitive load near zero. ## The stack at a glance ``` ┌───────────────────────────────────────────────────────────────┐ │ Browser ← Next.js (Vercel Edge) ← Supabase Postgres + RLS │ │ + Resend (email) │ │ + Lemon Squeezy (payments) │ │ + PostHog (analytics, free tier) │ └───────────────────────────────────────────────────────────────┘ ``` | Layer | Service | Why | |------------------|--------------------------|-------------------------------------------------| | Frontend | Next.js 15 (App Router) | React + RSC + file-based routing | | Hosting / CDN | Vercel | Zero-config Next deploys, edge functions | | Database | Supabase (Postgres) | Postgres + auth + RLS + storage in one | | Auth | Supabase…
By @meliwat - License: -
Raw markdown