Scaffold a Multi-Tenant SaaS Starter

The opinionated, "I want to ship in a week, not architect for three months" SaaS scaffold. Multi-tenant by row-level security (not separate databases), org-based not user-based, billing wired from day one.

When to use

• New SaaS product, day 1.
• You know it'll be multi-tenant (B2B with teams/orgs).
• You're OK committing to: Next.js App Router, Postgres, Clerk, Razorpay or Stripe, Brevo, Vercel/Railway.

When NOT to use

• Adding tenancy to an existing app — surgery, not scaffolding. Different problem.
• Single-tenant SaaS (one customer, one DB) — use scaffold-fullstack-app instead.
• B2C consumer app where "user" is the tenancy boundary — over-engineered.
• You need separate-DB-per-tenant (regulated/HIPAA/sovereignty) — this scaffold uses RLS, not DB-per-tenant.

The architectural decisions (made for you)