The DropJune 18, 2026via Vercel Blog

The Agent Stack

Why it matters

Vercel is positioning itself as the infrastructure layer for agent development, releasing a complete open-source framework (eve) and toolkit that abstracts away model routing, workflow durability, sandboxing, and multi-platform deployment—solving the fragmentation problem that forces teams to either lock into a single vendor or stitch together disparate solutions.

Key signals

  • eve framework launched in public beta (open-source, opinionated agent implementation)
  • Five core SDKs: AI SDK, AI Gateway, Workflow SDK, Vercel Sandbox, Chat SDK, Vercel Connect
  • AI Gateway routes across hundreds of models from single endpoint with no vendor markup
  • Vercel Sandbox provides isolated microVMs with Docker support and credential injection
  • Vercel Connect in public beta supporting Slack, GitHub, Snowflake, Salesforce, Notion, Linear + OAuth
  • Chat SDK enables single agent deployment across 12+ channels from one codebase
  • Workflow SDK provides durability, state persistence, and checkpointing for multi-step agent runs
  • SERHANT and FLORA cited as production customers running agents on the stack
  • Vercel leveraging existing infrastructure from billion preview deployments and 6M daily builds

The hook

Vercel just shipped the full Agent Stack. One framework. Five SDKs. Everything developers need to build production agents without vendor lock-in.

Agents are designed to do almost any kind of work, from answering support tickets to writing code. No matter how complex the workload, how long it runs, or how many turns it takes to complete, every agent needs three core capabilities to operate: Implementing these capabilities to build a complete agent forces developers to choose between vendor lock-in with a single provider API, stitching together solutions, or building abstractions themselves. The Agent Stack gives you all the building blocks you need to create and ship production-grade agents. Agents don't run on a single model. Every task has a different cost, latency, and capability tradeoff, and the right call depends on what the agent is doing. It needs one interface to reach any of them, a way to route between them, and a way to stream back to the user. gives an agent one interface to call any model, and routes across hundreds of them from a single endpoint.AI SDKAI Gateway Every lab exposes model calls through their own API. Streaming, tool calls, structured output, and the shape of the request all vary, so every provider you support adds another integration to build and maintain. is a single interface for building AI apps, agents, and frameworks. It is platform, framework, and model agnostic, and allows you to generate text, images, speech, video, and more.AI SDK Tokens are a production dependency now, the way bandwidth is for the web, and agents use different models per task. Integration across labs means separate keys and billing from providers that are expensive, rate-limited, and always changing. is the CDN for tokens, routing them on the global network we have run for over a decade. It routes each call through a single endpoint, fails over when a provider goes down, and tracks cost and usage across all of them. You pay the provider's price with no markup, and you can use your own keys.AI Gateway runs three models from a single key, sending market analysis to Claude, marketing copy to GPT, and i...

Get stories like this every Friday.

The 5 AI stories that matter — free, in your inbox.

Free forever. No spam.