Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
Free, MIT-licensed Next.js 16 + Supabase boilerplate with auth, RLS, server actions, and caching built in.
NextBase Starter is a free, MIT-licensed Next.js 16 + Supabase boilerplate that gives SaaS teams a production-grade foundation with authentication, Row Level Security, typed server actions, and caching already wired together.
NextBase Starter is the open-source baseline of the NextBase family of kits, maintained as a public GitHub repository. It takes a fresh Supabase project and a Next.js 16 app and produces a Turborepo monorepo with apps/web (the Next.js application) and apps/database (Supabase migrations and tests). The starter includes working sign-up, sign-in, magic link, OAuth, forgot-password, and update-password flows, a dashboard shell, and a reference CRUD page protected by RLS. The codebase assumes professional TypeScript fluency and is designed to be audited line by line.
@supabase/ssr clients for browser, server components, server actions, and middleware, so cookies survive every render boundary in Next.js 16 without breaking after refresh or deploy.apps/database/supabase/migrations, with every user-owned table shipping SELECT/INSERT/UPDATE/DELETE policies keyed off auth.uid().next-safe-action — All mutating endpoints are validated with Zod, and the authActionClient injects ctx.userId and refuses unauthenticated calls.cacheComponents: true enables static-by-default rendering with surgical use cache boundaries, plus a written guide at docs/NEXTJS_CACHE_COMPONENTS.md.@tailwindcss/postcss, including Forms and Typography plugins.build, lint, test, typecheck, gen-types, and test:e2e tasks, plus Changesets-driven release automation.NextBase Starter is for founders, indie hackers, and small teams shipping a SaaS on Next.js and Supabase who want to compress weeks of plumbing into a weekend of customization. It is also for senior engineers who want a credible, auditable reference architecture for RLS, SSR cookies, and Cache Components. Teams already on Supabase can use it as a consistent pattern for server actions, data access, and monorepo layout instead of maintaining three subtly different conventions.
pnpm database#start) with generated types for a fast MVP loop, then deploy to Vercel with Node 22+.After copying .env.local.example and .env.development.local.example into place, you provision the database either locally with pnpm database#start and pnpm gen-types-local, or against a hosted Supabase project with pnpm supabase db push and pnpm gen-types. Then pnpm dev starts the app at localhost:3000. The project ships with Playwright and Vitest configs already wired into Turbo pipelines.
The NextBase Starter is free and MIT-licensed, with no purchase required. The premium NextBase kits (Stripe billing, teams and organizations, RBAC admin, transactional emails, multi-tenancy, and AI starter kits) are commercial products sold at usenextbase.com; the starter remains free.
Yes, the starter is MIT-licensed. You can use it for personal projects, client work, internal tools, or commercial products without paying.
The starter covers the foundation: Supabase auth, RLS, typed server actions, Cache Components, monorepo, and tests. Premium kits add Stripe billing, teams, RBAC and admin, transactional emails, multi-tenancy, and AI starter flows on the same architectural patterns.
Supabase bundles Auth, Postgres, RLS, and Storage in one vendor with real SQL migrations and a real SQL surface. NextBase is opinionated about that choice, so you avoid stitching three separate SDKs together.
Yes; the architecture does not depend on any one UI or data-fetching library. You can replace or remove them and keep the rest of the data-access and caching structure intact.
