Repository files navigation

🚀SaaS Boilerplate is a powerful and fully customizable template to kickstart your SaaS applications. Built withNext.js andTailwind CSS, and the modular UI components ofShadcn UI. ThisNext.js SaaS Template helps you to quickly build and launch SaaS with minimal effort.

Packed with essential features like built-inAuthentication,Multi-Tenancy with Team support,Role & Permission, Database, I18n (internationalization), Landing Page, User Dashboard, Form handling, SEO optimization, Logging, Error reporting withSentry, Testing, Deployment, Monitoring, andUser Impersonation, this SaaS template provides everything you need to get started.

Designed with developers in mind, thisNext.js Starter Kit uses TypeScript for type safety and integrates ESLint to maintain code quality, along with Prettier for consistent code formatting. The testing suite combines Vitest and React Testing Library for robust unit testing, while Playwright handles integration and E2E testing. Continuous integration and deployment are managed via GitHub Actions. For user management, authentication is handled byClerk. For database operations, it uses Drizzle ORM for type-safe database management across popular databases like PostgreSQL, SQLite, and MySQL. One recommended option is to usePrisma PostgreSQL, which provides a free PostgreSQL database that is compatible and has been tested with SaaS Boilerplate.

Whether you're building a new SaaS app or looking for a flexible,production-ready SaaS template, this boilerplate has you covered. This free, open-source starter kit has everything you need to accelerate your development and scale your product with ease.

Clone this project and use it to create your own SaaS. You can check the live demo atSaaS Boilerplate, which is a demo with a working authentication and multi-tenancy system.

Add your logo here

Live demo:SaaS Boilerplate

Landing Page	User Dashboard

Team Management	User Profile

Sign Up	Sign In

Landing Page with Dark Mode (Pro Version)	User Dashboard with Dark Mode (Pro Version)

User Dashboard with Sidebar (Pro Version)

Developer experience first, extremely flexible code structure and only keep what you need:

• ⚡Next.js with App Router support
• 🔥 Type checkingTypeScript
• 💎 Integrate withTailwind CSS and Shadcn UI
• ✅ Strict Mode for TypeScript andReact
• 🔒 Authentication withClerk: Sign up, Sign in, Sign out, Forgot password, Reset password, and more.
• 👤 Passwordless Authentication with Magic Links, Multi-Factor Auth (MFA), Social Auth (Google, Facebook, Twitter, GitHub, Apple, and more), Passwordless login with Passkeys, User Impersonation
• 👥 Multi-tenancy & team support: create, switch, update organization and invite team members
• 📝 Role-based access control and permissions
• 👤 Multi-Factor Auth (MFA), Social Auth (Google, Facebook, Twitter, GitHub, Apple, and more), User Impersonation
• 📦 Type-safe ORM with DrizzleORM, compatible with PostgreSQL, SQLite, and MySQL
• 💽 Offline and local development database with PGlite
• ☁️ Remote and production database withPrisma Postgres
• 🌐 Multi-language (i18n) withnext-intl andCrowdin
• ♻️ Type-safe environment variables with T3 Env
• ⌨️ Form withReact Hook Form
• 🔴 Validation library withZod
• 📏 Linter withESLint (default NextJS, NextJS Core Web Vitals, Tailwind CSS and Antfu configuration)
• 💖 Code Formatter withPrettier
• 🦊 Husky for Git Hooks
• 🚫 Lint-staged for running linters on Git staged files
• 🚓 Lint git commit with Commitlint
• 📓 Write standard compliant commit messages with Commitizen
• 🦺 Unit Testing withVitest and React Testing Library
• 🧪 Integration and E2E Testing withPlaywright
• 👷 Run tests on pull requests with GitHub Actions
• 🎉Storybook for UI development
• 🚨 Error Monitoring withSentry
• ☂️ Code coverage withCodecov
• 📝 Logging withPino.js and Log Management withBetter Stack
• 🖥️ Monitoring as Code withCheckly
• 🎁 Automatic changelog generation with Semantic Release
• 🔍 Visual testing with Percy (Optional)
• 💡 Absolute Imports using@ prefix
• 🗂 VSCode configuration: Debug, Settings, Tasks and Extensions
• 🤖 SEO metadata, JSON-LD and Open Graph tags
• 🗺️ Sitemap.xml and robots.txt
• ⌘ Database exploration with Drizzle Studio and CLI migration tool with Drizzle Kit
• ⚙️Bundler Analyzer
• 🌈 Include a FREE minimalist theme
• 💯 Maximize lighthouse score

Built-in features from Next.js:

• ☕ Minify HTML & CSS
• 💨 Live reload
• ✅ Cache busting

• Nothing is hidden from you, allowing you to make any necessary adjustments to suit your requirements and preferences.
• Dependencies are updated every month
• Start for free without upfront costs
• Easy to customize
• Minimal code
• SEO-friendly
• Everything you need to build a SaaS
• 🚀 Production-ready

• Node.js 20+ and npm

Run the following command on your local environment:

git clone --depth=1 https://github.com/ixartz/SaaS-Boilerplate.git my-project-namecd my-project-namenpm install

For your information, all dependencies are updated every month.

Then, you can run the project locally in development mode with live reload by executing:

npm run dev

Openhttp://localhost:3000 with your favorite browser to see your project.

Need advanced features? Next.js 16 & React 19, Multi-tenancy & Teams, Roles & Permissions, Shadcn UI, End-to-End Typesafety with oRPC, Stripe Payment, Light / Dark mode. TryNext.js Boilerplate Pro.

Or, need a Self-hosted auth stack (Better Auth)? TryNext.js Boilerplate Max

This project offers a free open-source version and premium Pro/Max versions. Here's a detailed comparison:

Live Demos:

• Free Version:https://react-saas.com
• Pro Version:https://pro-demo.nextjs-boilerplate.com
• Max Version:https://max-demo.nextjs-boilerplate.com

Create a Clerk account atClerk.com and create a new application in the Clerk Dashboard. Then, copy the values ofNEXT_PUBLIC_CLERK_PUBLISHABLE_KEY andCLERK_SECRET_KEY into the.env.local file (which is not tracked by Git):

NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=your_clerk_pub_keyCLERK_SECRET_KEY=your_clerk_secret_key

In your Clerk Dashboard, you also need toEnable Organization by navigating toOrganization management >Settings >Enable organization.

Now, you have a fully working authentication system with Next.js: Sign up, Sign in, Sign out, Forgot password, Reset password, Update profile, Update password, Update email, Delete account, and more.

The project uses DrizzleORM, a type-safe ORM that is compatible with PostgreSQL, SQLite, and MySQL databases. By default, the project is set up to work seamlessly with PostgreSQL and you can easily choose any PostgreSQL database provider.

To set up a remote and production database, you need to create a PostgreSQL database and obtain the connection string. One recommended option is to usePrisma PostgreSQL, which provides a free PostgreSQL database. This database is compatible and has been tested with Next.js Boilerplate.

After creating your Prisma account, you can get the connection string in theConnect to your database section and select theAny client tab. Then, you can generate the connection string by clicking theGenerate database credentials button. Finally, you can copy the connection string and add theDATABASE_URL variable to the.env.local file.

For translation, the project usesnext-intl combined withCrowdin. As a developer, you only need to take care of the English (or another default language) version. Translations for other languages are automatically generated and handled by Crowdin. You can use Crowdin to collaborate with your translation team or translate the messages yourself with the help of machine translation.

To set up translation (i18n), create an account atCrowdin.com and create a new project. In the newly created project, you will be able to find the project ID. You will also need to create a new Personal Access Token by going to Account Settings > API. Then, in your GitHub Actions, you need to define the following environment variables:CROWDIN_PROJECT_ID andCROWDIN_PERSONAL_TOKEN.

After defining the environment variables in your GitHub Actions, your localization files will be synchronized with Crowdin every time you push a new commit to themain branch.

.├── README.md# README file├── .github# GitHub folder├── .husky# Husky configuration├── .storybook# Storybook folder├── .vscode# VSCode configuration├── migrations# Database migrations├── public# Public assets folder├── scripts# Scripts folder├── src│   ├── app# Next JS App (App Router)│   ├── components# Reusable components│   ├── features# Components specific to a feature│   ├── libs# 3rd party libraries configuration│   ├── locales# Locales folder (i18n messages)│   ├── models# Database models│   ├── styles# Styles folder│   ├── templates# Templates folder│   ├── types# Type definitions│   └── utils# Utilities folder├── tests│   ├── e2e# E2E tests, also includes Monitoring as Code│   └── integration# Integration tests├── tailwind.config.js# Tailwind CSS configuration└── tsconfig.json# TypeScript configuration

You can easily configure Next.js SaaS Boilerplate by searching the entire project forFIXME: to make quick customization. Here are some of the most important files to customize:

• public/apple-touch-icon.png,public/favicon.ico,public/favicon-16x16.png andpublic/favicon-32x32.png: your website favicon
• src/utils/AppConfig.ts: configuration file
• src/templates/BaseTemplate.tsx: default theme
• next.config.mjs: Next.js configuration
• .env: default environment variables

You have full access to the source code for further customization. The provided code is just an example to help you start your project. The sky's the limit 🚀.

In the source code, you will also findPRO comments that indicate the code that is only available in the PRO version. You can easily remove or replace this code with your own implementation.

To modify the database schema in the project, you can update the schema file located at./src/models/Schema.ts. This file defines the structure of your database tables using the Drizzle ORM library.

After making changes to the schema, generate a migration by running the following command:

npm run db:generate

This will create a migration file that reflects your schema changes. The migration is automatically applied during the next database interaction, so there is no need to run it manually or restart the Next.js server.

The project follows theConventional Commits specification, meaning all commit messages must be formatted accordingly. To help you write commit messages, the project usesCommitizen, an interactive CLI that guides you through the commit process. To use it, run the following command:

npm run commit

One of the benefits of using Conventional Commits is the ability to automatically generate aCHANGELOG file. It also allows us to automatically determine the next version number based on the types of commits that are included in a release.

The project is integrated with Stripe for subscription payment. You need to create a Stripe account and you also need to install the Stripe CLI. After installing the Stripe CLI, you need to login using the CLI:

stripe login

Then, you can run the following command to create a new price:

npm run stripe:setup-price

After running the command, you need to copy the price ID and paste it insrc/utils/AppConfig.ts by updating the existing price ID with the new one.

In your Stripe Dashboard, you are required to configure your customer portal settings athttps://dashboard.stripe.com/test/settings/billing/portal. Most importantly, you need to save the settings.

In your.env file, you need to update theNEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY with your own Stripe Publishable key. You can find the key in your Stripe Dashboard. Then, you also need to create a new file named.env.local and add the following environment variables in the newly created file:

STRIPE_SECRET_KEY=your_stripe_secret_keySTRIPE_WEBHOOK_SECRET=your_stripe_webhook_secret

You get theSTRIPE_SECRET_KEY from your Stripe Dashboard. TheSTRIPE_WEBHOOK_SECRET is generated by running the following command:

npm run dev

You'll find in your terminal the webhook signing secret. You can copy it and paste it in your.env.local file.

All unit tests are located alongside the source code in the same directory, making them easier to find. The project uses Vitest and React Testing Library for unit testing. You can run the tests with the following command:

npm runtest

The project uses Playwright for integration and end-to-end (E2E) testing. You can run the tests with the following commands:

npx playwright install# Only for the first time in a new environmentnpm run test:e2e

In the local environment, visual testing is disabled, and the terminal will display the message[percy] Percy is not running, disabling snapshots.. By default, visual testing only runs in GitHub Actions.

The App Router folder is compatible with the Edge runtime. You can enable it by adding the following linessrc/app/layouts.tsx:

exportconstruntime='edge';

For your information, the database migration is not compatible with the Edge runtime. So, you need to disable the automatic migration insrc/libs/DB.ts:

awaitmigrate(db,{migrationsFolder:'./migrations'});

After disabling it, you are required to run the migration manually with:

npm run db:migrate

You also require to run the command each time you want to update the database schema.

During the build process, database migrations are automatically executed, so there's no need to run them manually. However, you must defineDATABASE_URL in your environment variables.

Then, you can generate a production build with:

$ npm run build

It generates an optimized production build of the boilerplate. To test the generated build, run:

$ npm run start

You also need to defined the environment variablesCLERK_SECRET_KEY using your own key.

This command starts a local server using the production build. You can now openhttp://localhost:3000 in your preferred browser to see the result.

The project usesSentry to monitor errors. In the development environment, no additional setup is needed: NextJS SaaS Boilerplate is pre-configured to use Sentry and Spotlight (Sentry for Development). All errors will automatically be sent to your local Spotlight instance, allowing you to experience Sentry locally.

For production environment, you'll need to create a Sentry account and a new project. Then, innext.config.mjs, you need to update theorg andproject attributes inwithSentryConfig function. Additionally, add your Sentry DSN tosentry.client.config.ts,sentry.edge.config.ts andsentry.server.config.ts.

Next.js SaaS Template relies onCodecov for code coverage reporting solution. To enable Codecov, create a Codecov account and connect it to your GitHub account. Your repositories should appear on your Codecov dashboard. Select the desired repository and copy the token. In GitHub Actions, define theCODECOV_TOKEN environment variable and paste the token.

Make sure to createCODECOV_TOKEN as a GitHub Actions secret, do not paste it directly into your source code.

The project uses Pino.js for logging. In the development environment, logs are displayed in the console by default.

For production, the project is already integrated withBetter Stack to manage and query your logs using SQL. To use Better Stack, you need to create aBetter Stack account and create a new source: go to your Better Stack Logs Dashboard > Sources > Connect source. Then, you need to give a name to your source and select Node.js as the platform.

After creating the source, you will be able to view and copy your source token. In your environment variables, paste the token into theLOGTAIL_SOURCE_TOKEN variable. Now, all logs will automatically be sent to and ingested by Better Stack.

The project usesCheckly to ensure that your production environment is always up and running. At regular intervals, Checkly runs the tests ending with*.check.e2e.ts extension and notifies you if any of the tests fail. Additionally, you have the flexibility to execute tests from multiple locations to ensure that your application is available worldwide.

To use Checkly, you must first create an account ontheir website. After creating an account, generate a new API key in the Checkly Dashboard and set theCHECKLY_API_KEY environment variable in GitHub Actions. Additionally, you will need to define theCHECKLY_ACCOUNT_ID, which can also be found in your Checkly Dashboard under User Settings > General.

To complete the setup, update thecheckly.config.ts file with your own email address and production URL.

Next.js SaaS Starter Kit includes a built-in bundle analyzer. It can be used to analyze the size of your JavaScript bundles. To begin, run the following command:

npm run build-stats

By running the command, it'll automatically open a new browser window with the results.

The project is already configured with Drizzle Studio to explore the database. You can run the following command to open the database studio:

npm run db:studio

Then, you can openhttps://local.drizzle.studio with your favorite browser to explore your database.

If you are VSCode user, you can have a better integration with VSCode by installing the suggested extension in.vscode/extension.json. The starter code comes up with Settings for a seamless integration with VSCode. The Debug configuration is also provided for frontend and backend debugging experience.

With the plugins installed in your VSCode, ESLint and Prettier can automatically fix the code and display errors. The same applies to testing: you can install the VSCode Vitest extension to automatically run your tests, and it also shows the code coverage in context.

Pro tips: if you need a project wide-type checking with TypeScript, you can run a build withCmd +Shift +B on Mac.

Everyone is welcome to contribute to this project. Feel free to open an issue if you have any questions or find a bug. Totally open to suggestions and improvements.

Licensed under the MIT License, Copyright © 2026

SeeLICENSE for more information.

Add your logo here

Made with ♥ byCreativeDesignsGuru

Looking for a custom boilerplate to kick off your project? I'd be glad to discuss how I can help you build one. Feel free to reach out anytime atcontact@creativedesignsguru.com!