MakerKit is a collection of production-ready SaaS starter kits built with React, TypeScript, and modern backend options including Supabase, Drizzle ORM, and Prisma.
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 a simple landing page, 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:
| Kit | Database/Backend | Auth | Best For |
|---|---|---|---|
| Next.js + Drizzle | Any Postgres (self-hosted) | Better Auth | Maximum flexibility, self-hosting |
| Next.js + Prisma | Any Postgres (self-hosted) | Better Auth | Teams familiar with Prisma |
| Next.js + Supabase | Supabase | Supabase Auth | Supabase ecosystem users |
| React Router + Supabase | Supabase | Supabase Auth | React Router preference |
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 just need a landing page or simple site
- 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:
- Authentication: Sign up, sign in, password reset, email verification, OAuth providers, and optional MFA
- Multi-tenancy: Personal accounts, team/organization accounts, or hybrid mode (like GitHub)
- Role-Based Access Control: Built-in RBAC with support for custom per-tenant roles
- Billing: Stripe integration with subscriptions, usage-based billing, and customer portal
- Super Admin Dashboard: Manage users, organizations, impersonate accounts for debugging
- Marketing Pages: Landing page, blog, documentation, changelog, and legal pages
- 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
- Firebase: NoSQL with real-time database, integrated Google Cloud services
Don't worry too much about picking "wrong". You have access to all kits with your license. Try them and see which codebase clicks for you.
Common Pitfalls
Based on supporting thousands of customers, here are the most common mistakes I see:
- Underestimating the learning curve. Expect 2-3 days to understand the codebase structure before you're productive. Don't schedule a launch for the day after purchase.
- 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.
- 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're building something very simple. If you just need a landing page with a waitlist, MakerKit is overkill. Use a simpler template or build from scratch.
- 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.
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:
- Learning curve to understand the codebase structure (2-3 days typically)
- 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:
- Get a license: Buy a license to access all kits
- Pick your stack: Drizzle for maximum flexibility, Prisma for familiar tooling, or Supabase if you're invested in that ecosystem
- Clone, configure, and deploy: the kits are designed to be production-ready within hours, not weeks
Frequently Asked Questions
Which MakerKit kit should I choose?
Can I switch kits later?
Do I need to know TypeScript?
What's the difference between Drizzle and Prisma kits?
Is MakerKit good for AI-assisted development?
What if I'm learning React?
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
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.