Multi-factor authentication
Users enroll an authenticator app and are challenged for a code at sign-in.
Pick the framework first; the SaaS features are the same across kits. These are the questions that actually decide it.
Choose the Next.js SaaS starter kit. It is the flagship: Next.js 16 App Router, React Server Components, Server Actions, and Cache Components. It comes with Supabase, or with Better Auth on the Next.js Drizzle SaaS starter kit or the Next.js Prisma SaaS starter kit.
Choose the TanStack Start boilerplate. File-based routing that is type-safe end to end through TanStack Router, server functions instead of Server Actions, and a Vite and Nitro build that runs on any Node host. Drizzle, Prisma, or Supabase variants.
Choose the React Router SaaS starter kit. React Router 8 with Supabase, using the loader and action model Remix popularized. Remix itself merged into React Router, which the Remix SaaS boilerplate page explains.
Choose the React Native SaaS starter kit. An Expo app next to the Next.js web app in one monorepo, sharing one Supabase project and the same RLS policies. Checkout stays on the web to avoid app store commission.
Still weighing Next.js against TanStack Start? Read our TanStack Start vs Next.js comparison. Choosing an auth provider? See the Better Auth SaaS starter kit.
Four React SaaS boilerplates, one SaaS layer: pick the framework your team already knows. All of them use React 19, TypeScript, Tailwind CSS 4, Shadcn UI, and a Turborepo monorepo.
| Kit | Framework | Data layer | Auth | Best for |
|---|---|---|---|---|
| Next.js + Supabase | Next.js 16 App Router | Supabase Postgres, RLS | Supabase Auth | Most B2B SaaS; the flagship kit |
| Next.js + Drizzle | Next.js 16 App Router | Any Postgres via Drizzle | Better Auth | Teams that want SQL-like queries and no BaaS |
| Next.js + Prisma | Next.js 16 App Router | Postgres via Prisma 7 | Better Auth | Teams already fluent in Prisma |
| TanStack Start | TanStack Start, Vite, Nitro | Drizzle, Prisma, or Supabase | Better Auth or Supabase Auth | Type-safe routing, no Next.js |
| React Router 8 | React Router 8 | Supabase Postgres, RLS | Supabase Auth | Remix users, loader/action fans |
| React Native (Expo) | Expo + Next.js monorepo | Supabase Postgres, RLS | Supabase Auth | SaaS that needs native mobile apps |
The parts an AI agent can scaffold in an afternoon but rarely gets right: tenant isolation, billing webhooks, and role checks. Your agent builds your product on top of them.
Feature coverage differs slightly per kit, and the React Native app keeps checkout on the web. Each kit's landing page and docs list what it ships. For the architecture behind the team model, read our guide to multi-tenant SaaS architecture.
You buy a kit by data stack, not by framework. The Supabase license covers Next.js 16, React Router 8, and TanStack Start. The Drizzle and Prisma licenses cover Next.js 16 and TanStack Start. The React Native kit is a variant of the Next.js Supabase kit.
Every license is a one-time payment with lifetime updates and unlimited projects. Pro is for one developer; Teams covers up to five collaborators. The license terms have the details, including client work.
Inside MakerKit





> Add a projects table scoped to team accounts
Context your harness loads
Root rules first, then the folder the agent works in
Products built on MakerKit
AmplefoundAI-organic growth agent
GondlaThe first content engine designed for Hybrid Search Visibility
ConvoQualitative Research At Scale
QA.techShip faster with AI agents that create and run your QA tests
ReplybossFind relevant posts on X. Grow faster and sell more.
ReplenoInventory management for craft & small businessesNext.js 16, TanStack Start, React Router 8, or React Native with Expo next to the Next.js Supabase app. Components, forms, hooks, and Shadcn UI look the same in each. What changes is how data reaches the page.
Password, magic link, passkeys, OAuth and multi-factor authentication, with the emails that go with them.
Users enroll an authenticator app and are challenged for a code at sign-in.
Templates written in JSX with React Email, sent through Resend or Nodemailer (SMTP).
Password, magic link and social sign-in, configured per environment.
Opt-in sign-in with Face ID, Touch ID, Windows Hello or a security key. No password to phish.
Passwordless sign-in: users get a one-time link by email instead of typing a password.
The multi-tenant SaaS boilerplate parts: auth, billing, teams with roles, and a super admin that can impersonate or ban users and teams, plus the screens your customers use to manage them.
Roles map to permissions that your code and your database policies both check.
Users change plans, update payment methods and download invoices without a support ticket.
Users belong to several teams and switch between them, or work in their personal account.
Flat, per-seat and metered subscriptions through Stripe Checkout, with webhooks that keep plans and seats in sync with your database.
Billing, email, CMS and monitoring sit behind interfaces, so changing provider is configuration, not a rewrite.
Every UI string comes from translation files, so adding a language is content work.
Rules, an MCP server, skills and strict checks keep generated code in the kit’s patterns.
AGENTS.md files at the root and in each package teach coding agents the kit’s conventions.
Strict TypeScript and linting across the monorepo, so type errors surface before your users find them.
Gives Claude Code, Cursor, Codex and Gemini structured access to the kit: database, components, translations, checks and PRDs.
Tests for authentication, team accounts and invitations, written with page objects you can extend.
The full source lives in your repository. Nothing is hidden behind a package you cannot edit.
Slash commands for the work agents get wrong. /rls-review writes cross-tenant attacks as PgTAP tests and runs them; /reviewer reviews the diff and /bug-hunt sweeps the codebase.
The parts nobody lists until they are missing: content, deployment, documentation, and people to ask when you get stuck.
The setup, stack, and tooling are decided, so your first commit is a product feature.
Clone the repository, install dependencies, and start the dev server: the full SaaS runs locally, not a demo shell.
Built on Next.js 16 or TanStack Start, with React 19, Zod 4, Shadcn UI, Tailwind CSS 4, and TypeScript 7 (Go). Upgrades land through the public changelog.
Strict TypeScript, Oxlint, and oxfmt configured across the monorepo. The Rust-based Oxc toolchain keeps lint and format feedback fast as the codebase grows.
Password, magic link, passkey, and social sign-in, plus MFA, with the email flows that go with them.
Secure email/password authentication with built-in password reset, email verification, and account recovery flows.
Passwordless sign-in: users click a link in their inbox and skip the password entirely.
WebAuthn passkeys: users sign in with Face ID, Touch ID, Windows Hello, or a hardware security key. Phishing-resistant, with nothing to reset.
Google, GitHub, Facebook, X, Discord, and many more OAuth providers ready to configure.
TOTP-based MFA to protect your users' accounts, with enrollment and challenge screens included.
Personal and team accounts, invitations, and role-based access control, modeled in the database rather than bolted on in app code.
Full B2B multi-tenancy support. Let customers create workspaces, manage teams, and collaborate securely.
Email-based invitation system with role assignment. Onboard team members with a single link.
Granular role-based access control (RBAC). Define custom roles and permissions that match your product's needs.
Subscriptions with Stripe and other providers, including per-seat and metered billing, for personal and team accounts.
Stripe Checkout handles cards, Apple Pay, Google Pay, and other payment methods.
Self-service subscription management. Customers update payment methods, view invoices, and cancel without opening a support ticket.
Per-seat, usage-based, flat-rate subscriptions, or one-time purchases. Plans live in one billing schema that checkout and the pricing table both read.
Manage your users, organizations, and build your own internal tooling within the app.
See users, organizations, and subscriptions in one dashboard, restricted to super admins.
Explore, impersonate users, ban/delete accounts, all without touching the database.
Screens for every flow, built from the same Shadcn UI components you will use for your own features.
A landing page template with hero, features, pricing, and call-to-action sections to adapt to your product.
Dashboard demo components with charts, ready to wire to your own data.
Every Shadcn UI component pre-installed and themed. Browse, copy, and customize from our built-in dev tools.
A pricing table generated from your billing config: change a price in one place and the page follows.
Get found by your target audience with blog, documentation, changelog, and more.
A blog for product updates and SEO content, with per-post metadata and sitemap entries.
Reduce support load and improve user onboarding with the built-in documentation. Educate users and drive traffic to your product.
Keep users engaged with product updates. Announce features, fixes, and improvements in a dedicated changelog.
Comprehensive monitoring and testing tools to help you keep your SaaS running smoothly.
Pre-configured end-to-end tests for critical user flows. Ship with confidence, catch regressions before your users do.
Plug-and-play support for Sentry, PostHog, Signoz, and more. Monitor errors, track analytics, and debug production issues.
Ask me and the MakerKit community on Discord about setup, kit-related issues, and how the codebase fits together.
Developers and founders on the kits, the docs and the support. Every quote links to the original post.
just wanna say thanks to @gc_psk for building @makerkit_dev . it is such an overpowered template. like finally we have a really good one with active development, good docs and now even cursorrules/windsurfrules to just sit down and see ai agents do the stuff. truly mindblowing.

Built and maintained full-time by Giancarlo, a software engineer with almost 15 years of experience at startups and enterprises. Support questions reach me directly.
My favorite so far is @gc_psk and @makerkit_dev ship cursor rules along with updates to the framework. That's been really useful to pull in new version (via git remote) and things stay in sync.
Just started using MakerKit and it's a total game-changer. 🚀 Wish I had this when I was building Phishr. Instant team management and billing? Insane.
Second that! Giancarlo provides amazing support!! 😄
You need to check @makerkit_dev by @gc_psk — it’s the best I’ve seen so far. It’s feature complete, plenty examples, amazing docs, great Discord community, the dude provides support even days after his weeding (which is crazy!) I’m not affiliated in every way, just a happy cx.
Honestly @makerkit_dev is great. More for B2B products but really clean and well documented.
Amazing! @gc_psk has built a masterpiece with this one!
I just stumbled upon @makerkit_dev (and you!), it's impressive, I thought it was a big team behind how many features I saw (and I've been working in software a long time!) I was just looking for a free boilerplate, but the lifetime licence makes it a no brainer. Thank you!
I would have totally agreed with you until… I found @makerkit_dev last year. This is by far, the best boilerplate I found those past years. The dev is pushing new features and updates almost every week. His documentation (specially migrating to Next 15) is the best I’ve seen.
Makerkit is a gem for makers, if I was not building a desktop app I would be using it for sure, maybe for my next project
I landed on MakerKit after getting into boilerplates with ShipFast. Much better.
1000% recommend buying a good boilerplate (or making your own) I use @makerkit_dev it's so good I had an affiliate link, but I can't find it at the moment
For anyone who wants to build their own SaaS, I recommend trying out @makerkit_dev. Thanks to @gc_psk for creating such a fantastic tool that makes building websites a breeze! #SaaS #buildinpublic
We loved the product since when Giancarlo released the first version, and are building upon it ever since for all of our products. Highly recommended for all indie makers out there.
Solid and battle tested boilerplate with an amazing community and support.
React renders the UI. Everything a paying customer touches behind it is infrastructure you would build before your first feature. With AI coding tools, that is still 49-81 hours of senior developer time, including fixing the patterns AI got wrong.
Hours with Claude Code or Cursor · bar shows the range on a 0–25h scale
Estimates for a senior developer building from scratch with Claude Code or Cursor at $150/hour, including 15-25 hours refactoring AI-generated patterns. Read the methodology
Next.js, TanStack Start, React Router, or React Native: one SaaS architecture, React 19 throughout.
MakerKit is a React SaaS boilerplate available on Next.js 16, TanStack Start, and React Router 8, all on React 19, TypeScript, Tailwind CSS 4, and Shadcn UI, plus a React Native (Expo) variant of the Next.js Supabase kit for iOS and Android. Each web kit ships authentication, subscription billing, multi-tenant teams with roles, a super admin, and a marketing site.
Teams, roles, and invitations are part of the schema. Supabase kits enforce access with Postgres RLS; Better Auth kits with organization-scoped authorization policies.
AGENTS.md and CLAUDE.md files at the root and in each package, rules for Claude Code, Cursor, Codex, and Gemini, and an MCP server your agent can call.
Per-seat, metered, and one-off billing with webhook handling, behind a gateway that switches providers through configuration.
Pay once, then pull new features, fixes, and framework upgrades into your repository with git. Maintained full-time since 2022.
Questions go to me on Discord, the person who writes and maintains the kits.
Each kit has its own documentation, from installation to production. The Next.js Supabase kit alone has more than 170 pages.
Without MakerKit: Auth, billing, and teams built from scratch with AI tools: 49-81 hours including rework
With MakerKit: Day one is a product feature, built on patterns documented for your agent
Without MakerKit: Tenancy checks written by hand in each handler, and easy to miss in one
With MakerKit: Access rules live in the data layer: RLS policies or organization-scoped policies
Without MakerKit: A template snapshot ages with the framework it was built on
With MakerKit: Framework upgrades ship to your repository, maintained since 2022
Without MakerKit: UI templates stop at the screens
With MakerKit: The backend ships too: auth, billing webhooks, admin, and E2E tests
One-time purchase: lifetime license, continuous updates, unlimited projects of your own.
Questions about licensing?
Read the MakerKit license terms and the MakerKit FAQ, or contact me.
Not a client-only one. A SaaS needs server code for auth sessions, billing webhooks, and database access, so every kit uses a full-stack React framework. If you like Vite, the TanStack Start kit builds with Vite and Nitro.
Next.js if you want the largest ecosystem and the flagship kit. TanStack Start if you want end-to-end type-safe routing and a portable Node server. React Router 8 if you prefer loaders and actions or are migrating from Remix. Add the React Native kit when you need native mobile apps.
The core is the same: authentication with MFA, subscription billing, personal and team accounts with roles and invitations, and a super admin panel. Details differ by stack, for example Supabase kits enforce tenant isolation with Postgres RLS while the Better Auth kits check permissions in the application layer.
Yes. You should be comfortable with components, hooks, and TypeScript, plus the basics of your chosen framework. The kits handle auth, billing, and multi-tenancy, but your product features are React code you or your AI agent write.
Yes. Each kit ships AGENTS.md and CLAUDE.md rules so agents follow the kit's conventions, and an MCP server that lets agents inspect your database schema, run migrations, and manage environment variables.
MakerKit only ships React kits. If your team works in another framework, this is not the right fit.
Yes. Licenses include unlimited projects. A Pro license is for one developer; the Teams license lets up to five collaborators access the code.
Generally no, once access to the code is redeemed, because source code cannot be returned. Read the docs and the free Lite kit first if you want to evaluate the architecture.
Next.js, TanStack Start, React Router, or Expo: whichever you choose, auth, billing, and teams ship ready and stay maintained. Get lifetime access and build the part that is yours.
Browse the React SaaS boilerplate docs