Vercel adds zero-configuration deploys for NestJS
NestJS apps now deploy on Vercel without a build command or output directory, running as a single Fluid compute function with automatic scaling.
Vercel announced zero-configuration support for NestJS on 17 October. NestJS joins Express, FastAPI, Flask and Hono as frameworks Vercel can detect and deploy without you setting a build command or output directory: it reads the project, finds the server entry point, compiles it and applies the right build settings itself.
A deployed NestJS app runs as a single Vercel Function on Fluid compute, with Active CPU pricing by default, so you pay for compute used rather than for an idle server. You get response streaming, preview deployments, Instant Rollback and observability without extra setup, the same as Vercel’s other supported backend frameworks.
Why it matters: NestJS is a common choice for structured Node.js APIs, and until now deploying one to Vercel meant writing your own build configuration or reaching for a separate host. This removes that step entirely, which matters if you’re choosing between Vercel and a dedicated Node host for a new backend.
The caveat: this is Vercel-specific zero-config detection, not a NestJS feature. Moving the app to another platform still means configuring the build yourself.