Should you use Makerkit as your SaaS Boilerplate?

MakerKit is a collection of production-ready SaaS starter kits built with React, TypeScript, and modern backend options including Supabase, Drizzle ORM, and Prisma. If you're still weighing options, see how MakerKit stacks up against the other boilerplates.

MakerKit is the right SaaS boilerplate if you want to ship a production-ready SaaS in days instead of months, you're comfortable with React and TypeScript, and you need features like authentication, multi-tenancy, billing, and team management out of the box.

It's not the right choice if you need only a static landing page with no auth or database, you're unfamiliar with React, or you're building something that doesn't fit the B2B/B2C SaaS model.

After three and a half years of building MakerKit and working with over 3,000 customers, I want to give you an honest breakdown of whether it's right for your project.

What MakerKit Offers in 2026

MakerKit now offers four different kits across three technology stacks:

The Drizzle and Prisma kits are fully self-hosted with no PaaS dependency. Deploy anywhere: your own VPS, Cloudflare, Vercel, Railway, or Digital Ocean. The Supabase and Firebase kits integrate deeply with their respective platforms.

Tested with Next.js 16, React 19, and Better Auth in January 2026.

Decision Rules

Use MakerKit when:

• You're building a B2B SaaS with team/organization features
• You need auth, billing, and multi-tenancy out of the box
• You're comfortable with React and TypeScript
• You want AI-agent-friendly code with MCP Server support
• You want to ship fast AND scale later

Avoid MakerKit when:

• You need only a static landing page — no auth, no database, no billing
• You're not familiar with React
• Your product doesn't fit the subscription SaaS model

Who Should Use MakerKit

MakerKit works well for:

• Developers building B2B SaaS with team/organization features, role-based access, and per-seat or subscription billing
• Solo founders who want to skip months of boilerplate work and focus on their core product
• Teams already using React/Next.js who need a production-ready foundation
• Projects that need multi-tenancy with proper isolation, invitations, and member management
• Anyone who wants AI-agent-friendly code: MakerKit ships with its own MCP Server and extensive documentation designed for tools like Claude Code

What Comes Out of the Box

Every MakerKit kit includes:

1. Authentication: Sign up, sign in, password reset, email verification, OAuth providers, and optional MFA
2. Multi-tenancy: Personal accounts, team/organization accounts, or hybrid mode (like GitHub)
3. Role-Based Access Control: Built-in RBAC with support for custom per-tenant roles
4. Billing: Stripe integration with subscriptions, usage-based billing, and customer portal
5. Super Admin Dashboard: Manage users, organizations, impersonate accounts for debugging
6. Marketing Pages: Landing page, blog, documentation, changelog, and legal pages
7. Dev Tools: Environment variable validation, email preview, connectivity checks

The kits run on Next.js 16 with React 19 and include the latest versions of all dependencies.

What Tech Stack Should You Know

The minimum requirement is React and TypeScript. If you're not comfortable with these, MakerKit will be frustrating.

Beyond that, pick the kit that matches your existing knowledge:

• Drizzle ORM: SQL-like syntax, lightweight, maximum control over queries
• Prisma: Rich ecosystem, excellent migrations, more abstraction
• Supabase: Postgres with built-in auth, storage, and real-time features

Common Pitfalls

Based on supporting thousands of customers, here are the most common mistakes I see:

1. Skipping orientation. Plan a day to get your bearings in the codebase before scheduling a launch. This used to be a 2-3 day learning curve; AI agents have mostly flattened it, because the kit ships AGENTS.md files and an MCP Server that teach Claude Code and Cursor the conventions — the agent knows where things go, and your job is knowing what to ask for.
2. Skipping the documentation. MakerKit's docs cover edge cases you'll hit. Customers who read the relevant docs before coding save themselves hours of debugging.
3. Fighting the architecture. If you fundamentally disagree with how MakerKit structures routes, state, or components, you'll spend more time refactoring than building. Evaluate the codebase first.

When MakerKit Is NOT the Right Choice

Be honest with yourself about these scenarios:

• You don't need auth or a database. If all you need is a landing page with a waitlist, you don't need a SaaS kit at all — use a simple template. The moment you need sign-ups, billing, or a dashboard, that stops being true: MakerKit with team accounts disabled is a simple single-tenant app, already wired up.
• You're not familiar with React. MakerKit assumes React competence. If you're learning React while building a product under time pressure, you'll struggle. Either learn React first or choose a different technology.
• Your product doesn't fit the SaaS model. MakerKit is optimized for subscription-based products with user accounts, teams, and billing. If you're building an e-commerce store, a marketplace, or a content site, look elsewhere.

Is MakerKit Overkill for Solo Developers or Simple Apps?

No — and this objection deserves a direct answer because it comes up in every comparison thread.

MakerKit scales down as well as up. Team accounts, billing, and the other SaaS layers sit behind feature flags. Disable team accounts and you're running a single-tenant app with personal accounts, auth, and a marketing site — the same footprint as a "simple" starter, with the multi-tenant layer dormant instead of missing. When the first customer asks to invite a colleague, you flip a flag instead of scheduling the rewrite nobody budgets for.

The "deep codebase" is an asset in AI-assisted development, not a tax. The objection assumes a human reading the monorepo file by file. In 2026 you build with Claude Code or Cursor, and a structured Turborepo monorepo — clear package boundaries, AGENTS.md conventions in every workspace, an MCP Server — is exactly the environment coding agents do their best work in. Nx creator Victor Savkin and Vercel CEO Guillermo Rauch have both made this point publicly: agents thrive when the whole system — schema, API, UI, conventions — is visible in one repository. A flat "simple" codebase gives an agent less structure to work with, not less to learn.

What "overkill" would actually mean is paying a complexity cost you never recoup. With the flags off, there is no day-to-day cost — no team switcher in the UI, no organization logic in your way. The only honest version of the objection is price, and that's a different question with a clear answer: a $349 one-time license against the weeks of auth, billing, and admin work it replaces.

The Honest Trade-offs

Pros:

• Ships with features that would take months to build correctly (auth, billing, multi-tenancy, admin)
• Actively maintained with regular updates (Next.js 16, React 19, latest dependencies)
• AI-agent friendly with MCP Server and documentation designed for AI-assisted development
• Multiple deployment options from Vercel to self-hosted VPS
• Access to all five kits with one license

Cons:

• A real codebase to orient yourself in — though the AGENTS.md files and MCP Server mean AI agents navigate it for you, which has flattened what used to be a 2-3 day learning curve
• You're adopting someone else's architectural decisions (although, honestly, they're good decisions)
• Some customizations require understanding the full stack
• Commercial license cost (though it's a one-time purchase, which allows unlimited projects and has continuous updates)

Getting Started

If MakerKit sounds right for your project:

1. Get a license: Buy a license
2. Pick your stack: Drizzle for maximum flexibility, Prisma for familiar tooling, or Supabase if you're invested in that ecosystem
3. Clone, configure, and deploy: the kits are designed to be production-ready within hours, not weeks

Next Steps

Ready to evaluate? Browse the kit landing pages to see detailed feature breakdowns:

• Drizzle ORM Kit - Self-hosted, maximum flexibility
• Prisma Kit - Self-hosted, familiar tooling
• Next.js Supabase Kit - Supabase ecosystem
• React Router Supabase Kit - React Router alternative
• Next.js Firebase Kit - Firebase ecosystem (legacy)

Or start with the SaaS Starter Kit overview to compare all options, or dive into the free MakerKit course to see how it works before purchasing.