About Makerkit

What we build

MakerKit builds production-ready SaaS starter kits for TypeScript developers. Every kit ships the parts of a SaaS application that are genuinely hard to get right and easy to get wrong: secure multi-tenancy, team accounts with roles and permissions, subscription billing that handles upgrades and seats, and an authentication layer that supports OAuth and MFA out of the box.

The kits are available for Next.js, TanStack Start, React Router and React Native, with Supabase, Drizzle or Prisma as the data layer. You can compare them on the documentation home, or read about each one from the homepage.

Why it exists

Most SaaS applications solve the same problems before they solve their own. Tenancy, billing, permissions and account management take weeks to build, months to harden, and years to regret if the foundations are wrong. AI coding agents have made it faster than ever to scaffold a prototype, but a prototype is not the same thing as a codebase you can charge money on top of and still maintain in two years.

MakerKit exists to give that foundation away as source you own. Each kit is a one-time purchase with lifetime updates — not a subscription, and not a hosted service. You clone it, you own it, and there is no vendor in your runtime path.

Built for agent-assisted development

Every current kit ships an MCP server and agent rules files (AGENTS.md and CLAUDE.md) so that Claude Code, Cursor, Codex and Gemini work inside the codebase with the correct conventions rather than guessing at them. The setup guides live in the documentation for each kit.

Who runs MakerKit

MakerKit is built and maintained by Giancarlo Buomprisco, a software engineer who has been shipping and maintaining production SaaS applications for over a decade. Development happens in the open on GitHub, and customers get direct access to the team through a private Discord community.

Get in touch

Pre-sales questions are usually answered on the FAQ. For anything else, use the contact page or email info@makerkit.dev. Licence terms are set out in the terms of the licence, and our privacy policy explains how we handle data.