GenerateSaaS

Introduction

Production-ready SaaS boilerplate - a Next.js frontend on a shared Hono backend, with every feature gated by a flag in @repo/config.

GenerateSaaS is a production-ready SaaS boilerplate: a Next.js 16 frontend (apps/web) on a shared Hono backend (@repo/api), with every feature gated by a flag in the config object (packages/config/src/index.ts). These pages ship inside your project as AI-agent context, so every config key, package name, and path cited here is real.

Features

Each capability is a @repo/* package behind its own config flag.

Auth & access

Billing

Messaging

Storage & data

Backend & platform

Content & growth

Integrations

AI & ops

Config flags gate everything

Most features are a discriminated union - { enabled: false } | { enabled: true; ... } - read by both the frontend and the backend, so flipping one flag moves routes, sidebar entries, UI, and API surface together.

Flag stateBehavior
enabled: trueFeature renders, its routes mount, its @repo/* package runs.
enabled: falseUI hidden, routes skipped, backend paths short-circuit - no setup needed, no dead code to remove.

On by default: storage (s3), notifications, adminNotifications, apiKeys, apiDocs, performanceMonitor. Set from your init answers: payment, email, observability, tenancy.multiTenant, docs, desktop, mobile, ai, revenueSharing. Off by default: waitlist, sms, newsletter, captcha, contentApi, mcpServer - set their env vars and flip the flag to turn one on.

Not every flag is enabled-shaped. apiDocs and waitlist are plain booleans, tenancy toggles on multiTenant, and analytics / support / affiliate activate by the presence of a provider key. email has no off switch - you only pick its provider.

Getting started

On this page