Next.js SaaS boilerplate vs starter kit

Both products are Next.js 15 App Router apps with a user, a password hash, a plan column, and Stripe customer and subscription ids. They are not the same size.

Boilerplate

The Next.js SaaS Boilerplate is the smaller base. Prisma uses SQLite. You get accounts, a dashboard, and billing hooks. Use it when you want the shape and will replace the database and the mail path yourself. The layout is described in Next.js SaaS boilerplate architecture.

Complete kit

The Complete SaaS Starter Kit uses PostgreSQL. The webhook updates plan from checkout.session.completed, customer.subscription.updated, and customer.subscription.deleted, and it sends a short email when Checkout completes. That path is the one in building a SaaS with Next.js, Stripe, and PostgreSQL.

What neither one is

Neither kit is multi-tenant. Neither includes an AI chat or a marketplace. Those are separate products. If you only need Checkout, the portal, and webhooks, the Stripe Subscription Starter is the narrower package. Its schema matches the user columns above, on SQLite.

What changes in the files

Both apps use the App Router. The boilerplate is the smaller tree: auth helpers, a dashboard page, and one Checkout route. The Complete kit adds the customer portal route, the webhook that writes plan, a mail adapter, Docker Compose for PostgreSQL, and paid-route checks. That is why it costs more and why it takes longer to read.

If you already have an app and only need billing, do not start from either of these. Use the Stripe Subscription Starter and copy the three /api/stripe/ handlers.

Pick one

A boilerplate is a starting shape. A starter kit is a starting shape plus the boring production paths already wired. Designyff sells both so you can pick the amount of infrastructure you actually want.

Want the Complete kit already built? Open the Complete SaaS Starter Kit. For the short path, open the boilerplate.