Vercel Is Building a Platform, Not a Tool

Vercel used to be the place you deployed Next.js apps. That's no longer the full story.

In a single release cycle — capped by Vercel Ship 2026 — the company shipped Vercel Container Registry, Dockerfile support, Private Blob going GA, a Security Dashboard in private beta, Sandbox custom images, FUSE-based filesystems, and an expanded Vercel Agent now in public beta. Add AI Gateway routing rules, Claude Sonnet 5 access, and a Shopify Hydrogen rebuild, and you have something that looks a lot less like a deployment tool and a lot more like a full-stack cloud.

This matters for founders making infrastructure bets right now. The tradeoff used to be: opinionated simplicity (Vercel) versus raw control (AWS, GCP, self-hosted). That gap is closing fast. Vercel is absorbing the control surface without abandoning the developer experience that made it popular.

The Konsistent launch — enforcing code style for both agents and humans — is the tell. When a platform starts caring about what runs *inside* your repo, not just what deploys from it, the relationship has changed. You're not just a customer. You're inside an ecosystem.

For teams building products on Vercel today, the question isn't whether it's capable enough. It's whether consolidating this much of your stack onto one vendor is a strategy or a dependency.