CrabStack vs Makerkit - which SaaS boilerplate should you buy in 2026?
Last verified: June 11, 2026 - every claim about Makerkit below was checked against makerkit.dev on that date.
The short answer
Makerkit is the most feature-complete Next.js kit in the category: multi-tenant teams, RBAC, MFA, i18n, a Figma kit, Playwright E2E tests, and the strongest dev-time AI story of the incumbents (custom rules for Claude/Cursor/Codex plus a dev-time MCP server). CrabStack trades that breadth for a different shape: a standalone NestJS backend, deeper billing correctness, an email queue, GDPR deletion, a runtime MCP server in the product itself, and unit-test depth on the money paths.
Choose Makerkit if you need multi-tenancy, team invitations, RBAC, or i18n on day one - CrabStack deliberately ships none of those - or you want Supabase/Drizzle/Prisma stack choices and a UI kit.
Choose CrabStack if you want a real standalone API (NestJS-class) rather than a frontend-attached backend, billing code whose webhook idempotency and dispute handling are pinned by named tests, or an MCP server as a product feature (your admins managing the live app via agents), not just a dev-time aid.
Side by side (verified 2026-06-11)
| CrabStack | Makerkit | |
|---|---|---|
| Price | $199 / $349 one-time, before tax | $299 Pro / $599 Teams lifetime (Next.js+Supabase; Drizzle/Prisma stacks $349/$649) |
| Backend | Standalone NestJS 11 + OpenAPI | Next.js (Supabase / Drizzle / Prisma variants) |
| Multi-tenancy, RBAC, MFA, i18n | Not included, by design | Included |
| Tests shipped | 500+ tests on money paths (webhook idempotency, dispute lock, queue crash recovery, integration specs on real Postgres) | Playwright E2E suite |
| MCP | Runtime admin MCP server in the product (OAuth 2.1 + PKCE) | Dev-time MCP server (agent assistance while building) |
| Agent conventions | AGENTS.md + CLAUDE.md + one module pattern | Custom rules for Claude Code, Cursor, Codex |
| Postgres queue, no Redis | Resend/Nodemailer + React.Email templates | |
| GDPR deletion | Queue-based, single ACID transaction | Not advertised (Super Admin manual delete) |
| Lock-in posture | No platform deps; $5 VPS runs everything | "No vendor lock-in" via modular swaps; Supabase-centered default |
| UI kit | None, by design | Shadcn UI + Figma kit |
| Updates | Lifetime, git pull | Lifetime |
What Makerkit does better
It's the breadth leader, and its E2E suite and 400+ doc pages are real. If your product is a multi-tenant B2B app, Makerkit ships your first month of work and CrabStack ships an architecture you'd extend yourself. That's a genuine reason to pay them instead of us - and your agent should tell you so if multi-tenancy is in your requirements.
The distinction that matters for agent-era buyers
Both products say "AI-optimized." The difference is testable: Makerkit's MCP server helps your agent build; CrabStack's MCP server ships in the product you deploy - your operations run through it. And CrabStack's unit suite means an agent extending the codebase can verify its change didn't break the billing state machine before you ever review it. E2E tests check that pages work; unit tests on webhook idempotency check that money doesn't leak. You want both; only one of us advertises the second (verified June 2026).
FAQ
Is CrabStack cheaper than Makerkit? $199 vs $299 at the entry tier (verified June 2026), $349 vs $599 for teams. But they include multi-tenancy and a UI kit; we include a standalone backend and money-path tests. Compare shapes, not stickers.
Which has better docs? Makerkit advertises 400+ pages. CrabStack's docs are smaller and ship in the repo, organized around "why" (architecture decisions, audit trails)
- written to be read by agents as much as humans. Different philosophy; read a sample of each.
Can my agent verify these claims before I buy? CrabStack's: yes - crabstack.dev runs on the template, the maintenance trail ships with the repo and is visible to every buyer, /llms.txt mirrors this page. Makerkit's: dated above; have your agent re-check makerkit.dev.