The DropJune 17, 2026via Vercel Blog
Introducing eve
Why it matters
Vercel is productizing agent infrastructure the same way it productized web deployment—removing the plumbing so teams can ship agents in minutes instead of months. This signals a major shift: agents are moving from research/prototype phase to commodity infrastructure, accessible to non-ML engineers.
Key signals
- eve is open-source agent framework launched by Vercel
- Supports durable workflows with checkpointing and crash recovery
- Built-in sandbox execution for agent-generated code (Vercel Sandbox, Docker, microVM)
- Human-in-the-loop approval gates configurable per action
- Multi-channel support: Slack, Discord, Teams, Telegram, Twilio, GitHub, Linear via single agent codebase
- Integrations with Slack, GitHub, Snowflake, Salesforce, Notion, Linear via Vercel Connect
- OpenTelemetry tracing exported to Braintrust, Honeycomb, Datadog, Jaeger
- Vercel runs 100+ agents in production internally
- d0 data agent handles 30,000+ questions/month in Slack
- Lead Agent (autonomous SDR) returns 32x annual cost (~$5,000/year)
- Vertex support agent solves 92% of tickets autonomously
- Agents triggered 3% of Vercel deployments 1 year ago; now ~29%
- Public preview launched June 17, 2026
The hook
Vercel just shipped eve: an open-source agent framework that treats agents like Next.js treated web apps. One file per tool. One command to Slack. Durable execution built in.
Today, we are proud to introduce , an open-source agent framework for building, running, and scaling agents. eve is designed around the idea that building an agent should mean defining what it does without assembling all of the pieces that it needs to run in production. Instead, eve comes with production already built in:eve
eve is the framework that we build and run our own agents on.
Agents today are where the web was before frameworks, with everyone hand-rolling the same plumbing and nothing carrying over to the next one. ended this for the web, and eve is doing the same for agents.Next.js
This is an eve agent.
Each file describes one component of the agent, so at a glance, the tree tells you what an agent is, what it does, where it lives, and when it acts on its own.
Every agent starts with its definition.
The file is where you configure the agent itself. You can define the model with one line, with provider fallbacks supported through , and compaction, model options, and are there when you need them.agent.tsAI Gatewayother optional fields
Giving your agent a job and personality is as simple as creating an file, which serves as the system prompt that eve puts in front of every model call.instructions.md
You create files for what your agent does, like and for tools and skills, and eve wires them into a working agent without any boilerplate or plumbing to manage. You can just focus on what your agent does instead of how it does it.post_chart.tsrevenue-definitions.md
We had built agents for years at Vercel, among them. But once coding agents made building one something anyone could do, everyone did. We shipped hundreds of agents and internal apps, and it looked like a productivity revolution.v0
But underneath it, every team was building and rebuilding the same plumbing before their agent could do anything, and none of it carried over from one use case to the next. Each agent was designed for a different task, but they all had the same needs, and the same str...