You have a server in a container. Maybe it's a Go service, a Rails app, a Spring Boot API, or a web server behind nginx. It speaks HTTP. It listens on a port. It just needs somewhere to run. Add a file to your project, a
Here is a small HTTP server in Go, listening on : main.go A minimal HTTP server that reads its port from $PORT and answers every request. Add a file that builds it into a small image and runs it: Dockerfile.vercel A two-
A container on Vercel is a first-class citizen. It runs on the same platform, and the same compute, as your frontend and the rest of your services on Vercel. - A preview deployment for every push: Every commit gets its o
A container is only as good as the time it takes to answer its first request. 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.
Our first platform let you deploy a Dockerfile with a single command. That was a decade ago, and the idea was right, but the infrastructure to make it great didn't exist yet. We've spent the years since building the prim
Your backend now ships the way your frontend does: one push, one preview, one platform. We can't wait to see what you build. Read the docs or deploy an example to get started.
