Vercel Just Ate Your Backend

On June 30, 2026, Vercel shipped four products in one day. Read them separately and you see feature updates. Read them together, and the company just turned itself into a different kind of business.

The four: Vercel Services (run multiple frameworks in one project), VCR — Vercel Container Registry (an OCI-compliant image registry), Run any Dockerfile on Vercel (Dockerfile.vercel is now a first-class citizen), and Vercel Sandbox custom images (boot a sandbox from your own root filesystem). (vercel.com/blog/dockerfile-on-vercel, vercel.com/blog/vercel-services-run-full-stack-on-vercel, vercel.com/changelog/introducing-vcr-vercel-container-registry)

Vercel is no longer selling you a frontend platform. It just shipped the missing pieces to host your entire backend. The line between "deploy tool" and "cloud" just got blurry.

What "full stack on Vercel" actually means

For years, the standard Vercel-plus-backend pattern looked like this: Next.js on Vercel, a Go or Python service on Railway or Fly, a database on Neon, secrets in .env, and CORS rules held together with prayer.

Vercel Services breaks that pattern. You declare multiple services in vercel.json — a Next.js frontend, a FastAPI backend, a worker — and Vercel handles builds, routing, internal traffic, and atomic rollbacks for the whole graph. Services talk to each other over a private network. The frontend reaches the backend through BACKEND_INTERNAL_URL, an env var Vercel injects at deploy. No public routing. No CORS. (vercel.com/blog/vercel-services-run-full-stack-on-vercel)

The dashboard now shows a service graph, not a list of deployments. Logs filter by service. vercel dev runs the whole stack locally. This is the workflow you had to glue together yourself last year. Vercel just absorbed the glue.