# Zero-configuration support for NestJS

By Steven Van · 2025-10-17

NestJS backends run on Fluid compute with Active CPU pricing by default, scaling automatically with traffic.

NestJS apps can now deploy to [Vercel](<https://creatorstoolbox.com/tools/vercel>) [with zero configuration](<https://vercel.com/docs/frameworks/backend/nestjs>), 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](<https://www.google.com/s2/favicons?domain=vercel.com&sz=128>)

Vercel

The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.

[View Vercel →](<https://creatorstoolbox.com/tools/vercel>)

[Original source](<https://vercel.com/docs/frameworks/backend/nestjs>)

[Read Zero-configuration support for NestJS on Creators Toolbox](<https://creatorstoolbox.com/blog/vercel-zero-configuration-support-for-nestjs>)

---
Canonical source: https://creatorstoolbox.com/blog/vercel-zero-configuration-support-for-nestjs