Vercel Adds Container Registry, Raises Function Limit to 5GB

Vercel shipped an OCI-compliant container registry this week, letting Dockerfile-based servers run on Fluid compute, per Vercel's blog.

That matters for solo builders and small teams. Vercel Functions can now package up to 5GB for Node.js and Python, a 20x jump from the old 250MB cap, still in public beta.

That ceiling used to send you looking for a container host. A chunky ML dependency, a headless browser, a big native binary. Now they fit inside a single Vercel Function.

The registry didn't launch alone. Vercel Services also went GA this week, running a Next.js frontend and a FastAPI backend on shared infrastructure in one project.

v0 shipped Design Systems 2.0 the same week, generating UI from a team's own components and fonts instead of generic output.

Yes, but the old pitch was frontend and functions, leave containers to someone else. Vercel just erased that line on its own.

What I'd test first

I'm not moving my Slack bot and dashboard off Fly. That machine works fine already. For a new full-stack project this week, though, I'd deploy it on Vercel end to end. I'd watch two things. What a 5GB function costs under real traffic, and how Fluid compute cold starts compare to a Fly machine that never sleeps.

Convenience is real. So is the bill.