The Next.js SaaS boilerplate catalogue (Starter, AI, Core, Agency)
Most 'Next.js SaaS boilerplate' pitches try to be every template at once and end up being a generic shell with a long feature list. BoilerlyKit takes the opposite bet: four focused templates, each with an opinionated stack for a specific buyer profile. The point of this catalogue page is to help you pick the one that matches your product, not to upsell you on the most expensive one.
SaaSForge Starter, the minimal content + landing site
SaaSForge Starter ($59) is the smallest template: Next.js 16, React 19, TypeScript, Tailwind v4, shadcn/ui, MDX blog, MDX docs, oklch theme tokens, Supabase Auth (magic link + Google), and a polished landing page. Under 6k lines of app code. The intent is that you can read it end-to-end in an afternoon.
Pick Starter when you need a content site, a personal portfolio, an OSS docs site, or a SaaS landing page where the product itself lives somewhere else. It is also the cheapest way to start a project that will grow into one of the other tiers, the design system and config layout match across all four.
SaaSForge AI, assistants, RAG, credits, Stripe
SaaSForge AI ($259) is the heaviest of the four because AI products carry the most moving parts. Streaming chat against Claude and OpenAI, document upload with PDF/text extraction, embeddings in Postgres via pgvector, retrieval scoped to user workspaces, a credit metering system tied to real token usage, Stripe subscriptions with webhook lifecycle handling, and a setup-validation dashboard so the first deploy is boring.
Pick AI when your product is an assistant, a document Q&A tool, an AI writing app, or any SaaS where the LLM is part of the value. The credit economy is the bit you would otherwise spend a sprint inventing badly.
SaaSForge Core, B2B multi-tenant with RBAC and audit
SaaSForge Core ($199) is the B2B template. Workspaces are the tenancy boundary in Postgres with RLS policies, four-role RBAC (Owner/Admin/Member/Viewer), Stripe subscriptions with three tiers, Resend-powered invitations, TOTP 2FA, SAML SSO hooks for Okta/Azure AD/Google Workspace, API keys with masking, inbound and outbound webhooks, audit logs on mutations, support impersonation, and optional IP allowlisting.
Pick Core when your buyer is a procurement reviewer or an IT security team. The enterprise-shaped questions (Where is isolation enforced? Is SSO supported? Are audit logs immutable?) all have first-class answers in the codebase.
SaaSForge Agency, multilingual marketing site with CMS
SaaSForge Agency ($229) is the outlier of the four because it is a marketing site, not a SaaS app. Next.js 16, Directus 11 self-hosted CMS, three locales (EN, FR, ES) via next-intl, services, case studies, portfolio, blog, industry-specific landing pages, contact form with Resend, and Docker Compose for the CMS stack. Tailwind v3 here (the only template not on v4).
Pick Agency when you run an agency or freelance practice and want a white-label marketing template to drop on every client engagement. Also a fit for marketing sites where editors need a real CMS rather than MDX files.
How they compose, Starter as the substrate
All four share the same design system (oklch tokens), the same config-first approach (`src/config/`), and the same SEO surface (metadata, OG, sitemap, RSS, JSON-LD). Upgrading from Starter to Core means adding workspaces and billing on top of the shell you already learned; it does not mean throwing the project away.
There is no single-codebase 'all four in one' option because the four buyer profiles want different things. A content-site buyer does not want Stripe webhooks in their repo; a B2B buyer does not want Directus. Splitting the templates keeps each one small enough to actually read.