Spin up a production-ready Next.js web app with testing, linting, and CI already configured.
Deploy a Next.js application to AWS with ECS, CloudFront, and Redis using the included Terraform config.
Build and document UI components in isolation using the pre-configured Storybook setup.
Automate dependency updates and changelog generation for a team's Next.js project.
One-click Vercel deploy for basic use, AWS infrastructure requires Terraform and a configured AWS account.
Next Enterprise is a starter template for building web applications with Next.js, aimed at teams working on business-critical projects. It is maintained by Blazity, a group of developers who specialize in Next.js at scale. The project exists because most Next.js templates either target individual developers with too much complexity, or lack the structure that larger teams need. This template tries to hit the middle ground: a ready-to-go foundation with practical tools preselected and preconfigured. The template bundles Next.js 15 with the App Directory pattern, Tailwind CSS v4 for styling, TypeScript with strict settings, and ESLint plus Prettier for code consistency. Testing is covered by Vitest for unit tests, React Testing Library for component tests, and Playwright for end-to-end tests. Storybook is included for building and documenting UI components in isolation. Environment variables are managed with T3 Env, and dependency updates are automated via Renovate Bot. On the deployment side, the template supports one-click deploy to Vercel. For teams that need custom infrastructure, it includes Terraform-based configuration for AWS, covering a containerized deployment with ECS, a load balancer, CloudFront for static assets, Redis for caching, and a web application firewall. More cloud provider options are described as coming soon. The project uses GitHub Actions for automated workflows, including bundle size tracking and performance checks. It targets a perfect Lighthouse score out of the box. Conventional commits and Semantic Release are included for structured changelog generation. The template is under the MIT license and is actively maintained by three named contributors at Blazity. If the team needs deeper documentation on architectural decisions, deployment steps, or the reasoning behind tool choices, the project points to a separate docs site at docs.blazity.com.
← blazity on gitmyhub — every repo by this author, as a profile.
Verify against the repo before relying on details.