Vercel adds deployment of a plain Dockerfile via the Container preset
Vercel can now deploy a plain Dockerfile when no other framework is detected. It selects the Container preset, builds the Dockerfile, and routes all traffic to the resulting image. The Container runtime is in beta, runs on Vercel Functions, and is billed with Active CPU pricing.
Why it matters
Builders with a containerized app that Vercel does not auto-detect can deploy it without a framework preset. If another framework such as Django is detected, that framework takes precedence, so teams need to choose a framework or set the container framework explicitly. Multi-service projects are configured through vercel.json services with a per-service Dockerfile.
Who should care
Developers deploying containerized web apps or APIs on Vercel, and teams running multi-service projects.
What you can do
If you have a containerized app, add a Dockerfile at the project root, confirm Vercel detects no other framework, and deploy; if detection picks another framework, run vercel project update --framework container.