next-forge

next-forge is a production-grade Turborepo template for Next.js apps. Build SaaS with a structured monorepo foundation, separate apps, shared packages, and opinionated defaults.

Autres

Visiter le Site Web

Overview

next-forge is a production-grade Turborepo template for Next.js apps. It provides a monorepo starting point for new SaaS projects, with a focus on shipping quickly without giving up a structured codebase.

The template is designed around separate apps and shared packages, so teams can keep product surfaces independent while still reusing common code. The docs describe it as a comprehensive, opinionated foundation with minimal configuration and a workflow that favors clear boundaries between apps and packages.

What next-forge includes

Monorepo foundation with Turborepo

Start from a production-grade Next.js monorepo rather than assembling routing, shared code, and tooling from scratch.

Independent apps

Run multiple self-contained apps in one repository, with recommended subdomains and separate environment variables for each app.

Shared packages

Keep shared code in packages such as the database layer, which centralizes schema, migrations, middleware, hooks, components, and environment exports.

Workspace boundary checks

Use Turborepo boundaries to help catch workspace violations with `bun run boundaries`.

Prebuilt app templates

Ship with app templates for web, API, email, docs, studio, and Storybook, each focused on a different part of the product stack.

Opinionated toolchain

Use a documented setup that includes Next.js Server Actions, Prisma, Resend, Clerk, shadcn/ui, BaseHub, Storybook, and other tools already wired into the template.

Common ways to use next-forge

Start a new SaaS project
Use the template when you want to launch a new SaaS product with a ready-made web app, API, docs, and supporting tooling instead of assembling each piece manually.
Organize multiple apps in one repo
Use the monorepo layout when several products or surfaces need shared packages but still need to remain deployable as separate apps.
Build product infrastructure
Use the API, email, and studio apps together when a product needs backend endpoints, transactional email templates, and a database editor in the same codebase.
Ship and maintain a product surface
Use the docs, web, and Storybook apps when you need a public site, maintainable documentation, and isolated component previews for frontend work.
Keep a large repo structured
Use the boundary checks and app-specific environment conventions when you want a disciplined repository structure that helps avoid accidental cross-app coupling.

Pros and Cons

Pros

Covers a broad starter stack with web, API, email, docs, studio, and Storybook apps.
Uses a monorepo structure that supports shared code across apps and packages.
Provides documented boundaries and environment variable conventions for app separation.
Includes concrete project-specific tooling choices rather than only an empty scaffold.

Cons

The docs emphasize opinionated defaults, so teams that want a blank-slate setup may need to replace or rework some choices.
The source material does not include a pricing page with plan details, so availability and commercial terms are not spelled out on the site pages provided.

FAQ

Why doesn’t next-forge use tRPC?

next-forge uses Next.js Server Actions instead of tRPC because the project favors a native Next.js approach with tighter framework integration and less complexity.

Why were those tools chosen as the defaults?

The default tools were chosen by the project author based on experience using them in production applications. The docs say those defaults may change over time as tools and preferences evolve.

Why is `suppressHydrationWarning` used on the `html` tag?

The documentation says the `suppressHydrationWarning` on each `html` tag follows the recommendation from `next-themes` to avoid theme-related hydration warnings caused by determining theme on the client side.

Why are there dependencies that appear unused?

The FAQ says some dependencies are present to prevent Turbopack warnings about packages that are used but not installed in the project itself, which could otherwise fail in production.

Can teams extend or adapt the template structure?

Yes. The structure docs say each app and package should be self-contained, and the repository includes a contributing guide and documentation pages for working with the template.

Quick Facts

Category: Developer Tool
Platform: Next.js monorepo template
Monorepo manager: Turborepo
Pricing: No pricing details published on the provided pages
Source domain: next-forge.com
Primary use: Starting a SaaS app with a structured Next.js base