How to choose a SaaS boilerplate: 7 questions to answer before you buy

By Charanjit Singh · Updated 9 Oct 2026

Disclosure: Top Boilerplates is run by the maker of IndieKit, which appears in this guide. It is described from the same listing record as every other kit here and isn't ranked first.

Most boilerplate comparisons line up feature checklists: auth, billing, email, dark mode. Almost every paid kit ticks those boxes, so the checklist rarely decides anything. What actually decides whether a starter saves you weeks or costs you weeks is a handful of structural choices that are hard to undo once you've built on top of them. These are the questions we ask about every SaaS kit we list, with real examples from the SaaS directory.

1. Do you need organizations and teams on day one?

Multi-tenancy - users belonging to an organization, with roles, invitations and per-organization billing - touches almost every table and route. Adding it later means rewriting queries, permissions and billing at the same time. If you're building B2B, filter for it first and treat everything else as secondary.

The difference shows up clearly in listings. SaaSBold is aimed at single-tenant B2C and prosumer apps and has no multi-tenancy, which is fine for that audience and a retrofit project for a B2B one. MakerKit and supastarter are built around organizations from the start. Vercel's free Next.js SaaS Starter has owner/member roles but nothing beyond that. If you're unsure, the multi-tenant collection is the narrower list.

2. Can you read the code before you pay?

Several popular kits keep their repository private until purchase, including ShipFast, supastarter, MkSaaS and Achromatic. That isn't a red flag on its own, but it means a live demo and the docs are all you can evaluate, and refund terms matter more. ShipFast, for example, doesn't offer refunds once repository access is granted.

Kits with a free or open tier let you test the actual codebase first: MakerKit has a usable free tier, IndieKit has an MIT-licensed free version alongside its paid Pro, and fully open options like Open SaaS and Next Forge can be cloned today.

3. What does the license let you do?

License terms are the part buyers skip and later regret. Some examples from our listings: MakerKit's Pro license bars client and agency work and bars open-sourcing your build; ShipFlutter lets you own the code but prohibits derivative works and resale; supastarter's license covers exactly one framework version, so switching frameworks later means another purchase. If you build for clients, ship open-source, or might change frameworks, read the license page before the feature page.

4. Is it tied to one host or vendor?

Some kits are built around a specific platform and are excellent if you've already chosen it. TanStarter is bound to Cloudflare D1, R2 and Workers - moving it to Postgres or Vercel is most of the work. Supabase-first kits like useSAASkit and Nextbase assume Supabase for auth and data. Neither is wrong; just make sure the platform is a decision you made, not one the starter made for you. If owning your infrastructure matters, start from the self-hostable collection.

5. Is the architecture heavier than your product?

A Turborepo monorepo or a microservices backend is the right call for some teams and pure overhead for a single app. Next Forge splits web, app, API and docs into separate apps; Ultimate Backend ships a NestJS microservices/CQRS setup. Both are well built, and both add moving parts you'll maintain forever. If you're one or two people shipping one product, a single-app starter is usually faster to change.

6. Is it actually maintained?

Feature lists don't age; dependencies do. Look for a public commit history or a changelog with recent dates. Listings on this site show a freshness indicator wherever we could verify a last commit or changelog date. Be cautious where neither exists - TanStack Starter Kit, for instance, has a private repo and no changelog, so there's no way to judge maintenance before buying.

7. Does billing match how you'll charge?

Stripe is the default, but if you sell internationally a merchant of record (Paddle, Lemon Squeezy, Polar) handles sales tax for you. Some kits support several providers - SaaSBold covers Stripe, Paddle and Lemon Squeezy; supastarter supports Stripe, Lemon Squeezy, Polar and Dodo Payments. Also check whether the kit models your pricing shape: per-seat, per-organization, or usage credits (Achromatic ships Stripe credits for metered AI features).

The kits mentioned, side by side

Once you've answered these, the shortlist is usually two or three kits. Compare those on their own pages - each listing has a best-for and skip-if verdict, the verified stack, and links to the demo and docs.