Boilerplatesv1.0.0

Next.js SaaS Boilerplate

Name: Next.js SaaS Boilerplate
Brand: Avnish Yadav
SKU: nextjs-saas-boilerplate
Price: 49 USD
Availability: InStock

Start a SaaS on Next.js with auth, database, emails, admin and billing hooks wired.

Who it's for

You are starting a SaaS or an internal tool on Next.js and don't want to spend the first two weeks on sign-up, password reset, emails and an admin page.
You want a codebase you can read end to end: no hosted auth service, no paid dependencies to run it locally.
You care about tests from day one: unit, integration and end-to-end tests and a CI workflow are already there.

Not for you if you need organisations and teams, SSO/SAML or a payment provider implemented in code out of the box: billing ships as an interface with a mock provider and a step-by-step Stripe guide.

Generated from the zip

What's inside

One Next.js 16 project folder. It runs locally with no accounts and no .env file: the database is a SQLite file, emails go to a local outbox page, and billing uses a mock provider.

Routes: 24 routes, including the landing, pricing and legal pages, sign-in and sign-up with email verification and password reset, a dashboard, a Pro-only page, settings, billing, an admin area with users and an audit log, and the API handlers for auth, billing and health.
Modules: validated environment, Better Auth configuration, role and plan guards, the Drizzle schema with migrations and a seed, email sending, the billing interface with a mock provider and webhook handling, the audit log and rate limiting.
Components and emails: 37 UI components and 4 email templates.
Tests and CI: Vitest unit and integration tests on temporary SQLite databases, 3 Playwright end-to-end specs and a GitHub Actions workflow.
Guides: getting started, configuration, auth, database, emails, billing (with a Stripe implementation), admin, deployment (Vercel, Netlify, Docker), security and testing.

App routes (pages and API): 24
Library modules: 24
UI components: 37
Email templates: 4
Unit and integration tests: 15
Playwright end-to-end tests: 3
Guides: 10

In the zip · 161 files · 242 KB

.dockerignore
.env.example
.github/1 files
.gitignore
AGENTS.md
CHANGELOG.md
CLAUDE.md
Dockerfile
LICENSE.md
README.md
app/35 files
components/37 files
docs/10 files
drizzle.config.ts
drizzle/3 files
e2e/4 files
emails/5 files
eslint.config.mjs
instrumentation.ts
lib/24 files
next.config.ts
package-lock.json
package.json
playwright.config.ts
postcss.config.mjs
proxy.ts
public/1 files
scripts/4 files
tests/17 files
tsconfig.json
vitest.config.ts

Setup

Requirements

Node.js 22.12 or newer and npm
Nothing else for local development (SQLite file database, emails written to a local outbox, mock billing provider)
For production: a Turso (or other libSQL) database, a Resend account with a verified sending domain, and a host such as Vercel, Netlify or Docker
For real payments: a Stripe, Lemon Squeezy or Paddle account (the billing provider is an interface you implement; a guide covers Stripe)
For the end-to-end tests: Playwright's Chromium, downloaded once with npx playwright install chromium

Unzip, then install: cd nextjs-saas-boilerplate && npm ci.
Start the app with npm run dev. The first run creates and migrates data/dev.db.
Open http://localhost:3000, choose Create an account and sign up with any email address.
Open http://localhost:3000/dev/outbox and click the verification link. You land on your dashboard.
Optional: npm run db:seed adds an admin and two example users so you can see /admin and the audit log.

Time to first result: about 3 minutes.

Tested with

Clean-install test passed on 2026-10-01 (darwin-arm64, node 22.23.2, npm 10.9.8): extract, base, node, yaml, docs, acceptance.

Licence

You may use this product in unlimited personal and commercial projects, including client work. You may not resell, redistribute, sublicense or share the product itself, in whole or in part, including as a template, starter kit or course material. One purchase covers one person.

The full licence is in LICENSE.md inside the zip. Site terms: /terms.

FAQ

Questions

Do I need Turso or Resend to try it?

No. Locally it uses a SQLite file and writes emails to a dev outbox. For production you add a Turso (or other libSQL) database and a Resend account with a verified sending domain.

How do I take real payments?

Billing is an interface (BillingProvider) with a mock provider and a simulated checkout. You implement it for Stripe, Lemon Squeezy or Paddle; the billing guide walks through Stripe with the provider code.

Has it been deployed to production?

The clean-install test ran lint, type checks, the test suite and a production build on a fresh copy of the zip, and the Playwright suite ran from the same copy. A deployment to Vercel or Netlify with Turso and Resend was not part of those runs; the deployment guide covers the steps.

How do updates work?

New versions go to your Gumroad library; download them from there. Changes are listed in the CHANGELOG inside the zip.

Can I use it for client work?

Yes. Apps you build from it, for yourself or for clients, are yours. You can't resell or share the boilerplate itself.

What about refunds?

Payment goes through Gumroad. All sales are final: the files are delivered instantly, so there are no refunds. Updates within version 1.x are free.