Zero-configuration support for NestJS
By Steven Van ·
NestJS backends run on Fluid compute with Active CPU pricing by default, scaling automatically with traffic.
NestJS apps can now deploy to Vercel with zero configuration, running as a Vercel Function. Backends use Fluid compute with Active CPU pricing by default, so a NestJS app scales up and down automatically based on traffic and only charges for the compute it uses.
NestJS deployments also get:
- Preview deployments that test changes in a copy of production infrastructure
- Instant Rollback to recover from breaking changes in milliseconds
- Vercel Firewall, a multi-layered security system against threats
- Secure Compute, for private links between the backend and other clouds
To deploy, the app's entrypoint file needs one of a set of recognised names, such as src/main.ts or index.ts. Apps can be deployed by connecting a Git repository or running vc deploy, and run locally with vercel dev.
Vercel
The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.
View Vercel →