vercel/next-forge

Production-grade Turborepo template for Next.js apps.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 33 minutes ago
Added to GitGenius on September 8th, 2026
Created on January 2nd, 2023
Open Issues & Pull Requests: 33 (+0)
GitHub issues: Enabled
Number of forks: 713
Total Stargazers: 7,669 (+0)
Total Subscribers: 24 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.4 hours
Mean response time: 21.6 days
90th percentile: 55.4 days
Tracked items: 215

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 4% of issues opened in the past year have been closed. Three people close 88% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 17
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 220 days
Stale 30+ days: 13
Stale 90+ days: 9

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (107)
  • released (87)
  • enhancement (64)
  • documentation (16)
  • help wanted (9)
  • needs repro (7)
  • blocked (3)
  • question (3)

Most active issues this week

Detailed Description

next-forge is a production-grade Turborepo template for Next.js applications.

The template addresses the challenge of setting up a modern SaaS application from scratch by providing a comprehensive, pre-configured foundation that integrates essential services and tooling. It combines a monorepo structure with multiple applications (marketing site, main app, API, documentation, email templates, and Storybook) alongside reusable packages for authentication, database access, design systems, payments, analytics, observability, security, and other common SaaS features. The approach emphasizes minimal configuration by bundling opinionated choices around tools like Clerk for authentication, Stripe for payments, Prisma for database access, and Sentry for error tracking, all working together within a Turborepo setup.

Developers building SaaS products should consider next-forge when they want to avoid the repetitive work of integrating multiple services and establishing project structure. It suits teams starting new applications who value having sensible defaults already in place rather than assembling components individually. The template is particularly valuable for those who want type safety throughout their stack, dark mode support in the design system, and built-in support for features like feature flags, webhooks, real-time collaboration, and internationalization. It provides working examples across multiple deployment targets and includes a demo environment showing the marketing site, application, component library, and API in action.

Development activity shows consistent engagement with the codebase through regular updates and maintenance of the integrated services and tooling. The project maintains active support for its dependencies and demonstrates responsiveness to the needs of teams adopting the template for production applications.