Template
Vercel's production-grade Turborepo template for Next.js SaaS apps: a monorepo with auth, database, payments, email, analytics and docs already wired together, created with one command.
Every entry that names it, newest first, from every log it was used in.
next-forge is an MIT-licensed template from Vercel for starting a SaaS product as a Turborepo monorepo. It creates several apps, including the main app, a marketing site, an API, email templates, docs and a Storybook, plus shared code for a design system, the database and more. It comes set up with Clerk for authentication, Stripe for payments, Resend for email, PostHog and Google Analytics, Sentry and BetterStack for monitoring, and Arcjet for security, along with SEO, feature flags, cron jobs, file storage and internationalization. The docs start a project with npx next-forge@latest init, which asks for a project name and whether to use npm, pnpm, yarn or bun (pnpm dlx, yarn dlx and bun x start it too). The quickstart says only Clerk and a PostgreSQL database are required to boot; features that need other keys degrade or show warnings until you add them. We think it fits a builder who knows they are making a SaaS with accounts and billing and would rather start from choices someone already fitted together than connect each service by hand over the first weekend. A caution: it is opinionated by design. Each service it ships with needs its own account and keys before that part works, and a monorepo of six apps is a lot of structure for a small experiment or a single landing page.
The log is the half nobody can write on their own: an entry lands here the moment somebody names this tool in one. Attach it from the composer’s + menu.
Nobody has said anything about next-forge yet.
Nobody has rated next-forge yet. What it is like to build with is the part no download count can tell anyone.