Deploy any Dockerfile to Vercel without setup

Summary

Eliminates container registry setup, Kubernetes cluster management, and guessing at concurrency limits. Stateless container processes integrate with preview deployments and observability dashboards you already use for frontends.

Why it matters

Eliminates container registry setup, Kubernetes cluster management, and guessing at concurrency limits. Stateless container processes integrate with preview deployments and observability dashboards you already use for frontends.

Sources

1. 1.Add a `Dockerfile.vercel` file to your project, and Vercel builds, stores, deploys, and autoscales the image on Fluid compute, so you pay only for the CPU your code uses
2. 2.Active CPU pricing: Fluid compute bills for the time your code is actually running, so an idle server, parked on a slow query or an upstream API, isn't burning CPU while it waits
3. 3.When Vercel builds your image, it stores it as an optimized boot image, a compressed snapshot of the container's disk tuned for fast startup
4. 4.The only rule is that your server listens on `$PORT`, which defaults to `80`