Stop rebuilding SaaS boilerplate. I packaged auth + payments + dashboard into one Next.js starter

#nextjs #sass #webdev #typescript

Every time I started a new SaaS project, the first two weeks looked the same:

Set up auth (again)
Wire up Stripe (again)
Build a dashboard layout (again)
Write the same DB schema (again) Before writing a single line of actual product code. So I built LaunchKit — a production-ready Next.js SaaS starter with everything already connected. ## What's included: Authentication (Clerk) Email/password, Google OAuth, GitHub OAuth, magic links. Route protection, session handling, user management. Zero config beyond adding your API keys. Stripe subscriptions Three pricing tiers (Free / Pro / Enterprise), checkout sessions, billing portal, and all three webhooks handled:
checkout.session.completed → activates subscription
invoice.payment_succeeded → renews period
customer.subscription.deleted → downgrades to free Dashboard Sidebar layout, stats cards, upgrade banner (auto-hides on paid plans), billing page, settings page, analytics placeholder. Dark mode. Fully responsive. Database Drizzle ORM + PostgreSQL schema ready to go. Works with Supabase free tier out of the box. TypeScript + shadcn/ui Fully typed. Beautiful, accessible components via shadcn/ui + Tailwind CSS. ## The stack
Framework: Next.js 16 (App Router)
Auth: Clerk
Payments: Stripe
Database: Drizzle ORM + PostgreSQL
UI: Tailwind CSS + shadcn/ui
Deploy: Vercel + Supabase ## Setup time ~30 minutes from download to live on Vercel. The README walks you through every step.