Vercel Ship 2026 bet the keynote on agents, but the quiet shipped wins matter more today

Vercel ran Ship 2026 in London on June 17 in front of more than 2,500 people. The keynote had one subject: agents. CEO Guillermo Rauch put it bluntly, saying “we are deploying software that can think.” Every launch bent toward that idea.

Here’s the honest split. The headline launches are real but mostly gated behind private or public betas, so for a developer opening a terminal today they’re a roadmap, not a tool. The smaller items Vercel shipped around the same window, feature flags, a Claude Design deploy path, and signed Blob URLs, are the ones you can actually wire into a project this afternoon. Below is what landed, what it does, and which ones are worth your attention now versus on the calendar.

What actually shipped at Ship 2026

The number behind all of it: Vercel says deploys triggered by coding agents rose from under 3% six months ago to past 50% today, a figure Rauch has also used to signal the company is IPO-ready. Whether you buy the framing or not, that shift is why the keynote looked the way it did. The platform is reorienting around the thing already generating half its traffic.

The agent stack: ambitious, mostly gated

eve is the centerpiece. It’s an open-source, TypeScript-native framework where, in Vercel’s words, “every agent is a directory you scaffold, run, and deploy with the commands you already use.” It ships with durable execution and sandboxing built in, and it compiles to ordinary Vercel Functions. That’s a genuinely interesting shape, because it models an agent as a deployable service rather than a notebook experiment.

Around it sits the enterprise layer. Vercel Connect (GA) hands an agent a temporary credential “scoped to the one task in front of it,” which is the right answer to the token-sprawl problem. Vercel Passport (Public Beta) puts internal apps behind your identity provider, private by default. Vercel Agent (Private Beta) watches production and opens fix PRs on its own, with a plan mode that gates permissions before it acts. Useful, but you can’t pull most of it today. Connect is the exception.

Vercel Services: the one with a date

The launch that drew the most developer chatter wasn’t an agent at all. Vercel Services, announced for July 1, makes backends first-class alongside frontends, so a service can talk to another service “without touching the public internet.” Vercel is pitching FastAPI, Flask, Express, and Hono support, plus a database marketplace spanning Aurora, DynamoDB, OpenSearch, and more.

That’s Vercel pushing past its frontend-host reputation into something closer to a full app platform. The fast-startup work that makes this practical is the same lineage we covered when Firecracker microVMs got browsers booting in subsecond time. It has a real ship date, which already puts it ahead of the betas above. Whether co-located services beat just running your own backend is the question to benchmark once it lands.

Vercel Flags: the one to actually use now

Vercel Flags went GA in April and is on every plan, so it predates the conference, but it’s the most useful thing in this whole roundup for a working team. Flags evaluate server-side through the Flags SDK, so there’s no client-side flicker or layout shift, and the company sums up the value plainly: “merging code sends a build to production, but the feature flags control whether users can see what changed.”

You define flags in code and deploy. They show up in the dashboard as drafts. There are first-class adapters for Next.js and SvelteKit, an OpenFeature provider for everything else, a vercel flags CLI, and a Flags Explorer in the toolbar for overriding values in your own browser without redeploying. If you’ve been hand-rolling a flag table in your database, this is the upgrade.

Claude Design deploys and signed Blob URLs

Two small but real conveniences round it out. The Claude Design integration adds Vercel as a send-to destination inside Claude Design at claude.ai/design: finish a design, hit Share, pick Vercel, and “Claude Design deploys the design as a new project in your connected Vercel account and returns a URL you can open and share.” It runs over the Vercel MCP server. For shipping a quick prototype URL it removes a step, though it’s a starting point, not a substitute for the hard work of turning generated UI into real code.

The other is signed Blob URLs in the Vercel CLI (5.14.5+). vercel blob presign mints a URL “scoped to one operation (get, head, put, or delete), one pathname, and a custom expiry of up to seven days,” with a --valid-for flag like 15m or 7d. It’s the unglamorous primitive every file-upload feature needs, and it means you can hand out scoped access without minting a full Blob token.

What this means for you

If you run a production app on Vercel, do two things this week and ignore the rest until it ships. Turn on Flags and move one risky feature behind a server-evaluated flag, because the no-flicker, no-extra-table win is immediate and free on your plan. Add vercel blob presign to any upload or share flow that’s currently leaning on a long-lived token. Both are GA, both take an afternoon.

Everything agent-flavored is worth tracking but not worth restructuring around yet: eve, the Vercel Agent, Passport, Bring Your Own Cloud on AWS. Most of it is private or public beta, and the 50%-of-deploys stat is Vercel’s number, measured on Vercel’s own traffic. Put Vercel Services on your July calendar, since that’s the launch with a date and the one that decides whether Vercel becomes your backend host too. My read: pilot Flags now, watch the agent stack from a safe distance until the betas open up.