Multi-tenant workspaces
Users create workspaces, invite teammates and manage roles. Scope filters run in the data layer, so every query is tenant-scoped by default. You do not have to remember it in each new route.
Everything a SaaS needs before it has a single customer: auth, billing, workspaces, a typed API and a dashboard shell, assembled on the Next.js App Router and ready to build on.
Used by 1000+ developers
These are the defaults. Every one of them is swappable.
| Layer | Choice | Why |
|---|---|---|
| Database | PostgreSQL + Drizzle ORM | Typed schema, migrations and seeding. Run it locally, on Supabase, or on Neon. |
| Authentication | Better Auth | Email and password, social login, magic links, 2FA, passkeys, SSO and email verification. |
| Billing | Stripe | Subscriptions, tiered, metered and usage-based pricing, entitlements and grandfathering. |
| API | tRPC | End-to-end type safety, React Query integration, permissions and roles. |
| UI | Chakra UI + Saas UI | A themeable token system with pre-built components and Storybook stories. |
| React Email + Resend | Transactional templates you can edit, or bring your own SMTP provider. | |
| Testing | Playwright + Vitest | End-to-end and unit tests, running in GitHub Actions. |
The parts every SaaS needs before its first customer, built into the Next.js kit.
Users create workspaces, invite teammates and manage roles. Scope filters run in the data layer, so every query is tenant-scoped by default. You do not have to remember it in each new route.
Subscriptions, tiered plans, metered and usage-based pricing, entitlements. Your pricing config syncs to Stripe, so you maintain it in one place.
Navigation, data tables, filters, forms and empty states. The parts that take a week to build properly and drift out of sync when you do not.
Full type coverage and one set of patterns give an agent something to conform to. The tests catch it when it does not.
An agent will scaffold sign-in this afternoon. The question is what your tenth feature looks like, and whether you would notice it getting something wrong.
| Area | Generated from a prompt | In the kit |
|---|---|---|
| Auth | A working email and password flow. | Social login, magic links, 2FA, passkeys, SSO, email verification, session handling. Tenant scoping runs in the data layer. |
| Billing | A Stripe checkout link. | Subscriptions, tiered, metered and usage-based pricing, entitlements, grandfathering, webhooks. This is where billing bugs cost you money. |
| Multi-tenancy | A workspaces table and a foreign key. | Actor-based access control and scope filters on every query. Tenant isolation holds even when someone forgets. |
| Conventions | Whatever it picked this session. | One set of patterns. Your tenth feature looks like your first. |
| Knowing it works | Code that looks right. | Types and end-to-end tests in CI that fail when it is not. |
Server components prefetch the same tRPC queries the client uses and hand the data over on hydration. Pages render with data on first paint, and there is still only one API to maintain.
Auth providers, analytics, CMSes and payment SDKs ship a Next.js adapter before anything else. Whatever you add next, there is a documented path.
Most React developers have shipped a Next.js app, and coding agents know its APIs well. New people, and new agents, are productive on day one.
The dev server runs on Turbopack, so it starts quickly and changes show up almost instantly. That tight loop matters even more when an agent is making a dozen edits a minute.
The Metadata API sets titles, descriptions and Open Graph tags per route. Your marketing pages and your app live in one project, with no extra SEO libraries.
Vercel funds the framework and employs members of the React core team, so it is not going anywhere. Deploy there and you get preview deployments for every pull request out of the box.
Next.js 16 with the App Router, server components and streaming. The kit tracks new releases, with migration docs when something changes.
Pick the framework your team knows. Choose Next.js for its ecosystem and familiarity. Choose TanStack Start for simpler, explicit APIs, end-to-end type safety and a faster development loop.
No. One-time purchase, lifetime access to the repo and its updates. $200 for an individual licence, $400 for a team of up to 10 developers. Unlimited projects either way.
Yes. Both licences cover unlimited self-hosted projects, including work you deliver to clients.
No. It is a digital download, so we do not offer refunds. Read through the docs and try the open source packages first to check it is a good fit.
Every release includes migration docs, so your agents can apply upstream improvements to your codebase. It is a starting point, not a dependency, so you choose what to take and when.
One-time purchase with lifetime access. Unlimited self-hosted projects.