What exactly is Vercel eve?
Vercel shipped `eve` on June 17, 2026 — an open-source, filesystem-first TypeScript framework for building, running, and scaling agents. The positioning is explicit: what Next.js did for web pages, eve does for agents. Guillermo Rauch put it plainly at launch: an agent is just a directory. Drop an `instructions.md` in `agent/` and you have a running agent with no boilerplate, no configuration maps, no framework registration required.
The directory structure does the wiring for you. `tools/` holds what the agent can do. `skills/` holds domain knowledge as markdown. `subagents/` defines who it delegates to. `channels/` exposes the agent on Slack, Discord, Teams, Telegram, GitHub, Linear, or any custom surface via a small adapter file. `schedules/` handles cron-style background tasks. Vercel runs the whole thing on its existing infrastructure, so deployments look identical to any other Vercel project.
The internal proof of concept is credible. Vercel already runs over 100 agents in production on eve. One — an autonomous SDR internally called Lead Agent — costs roughly $5,000 per year to run and returns 32 times that. Another, a data analyst agent named d0, handles more than 30,000 Slack questions a month scoped to each asker's own data permissions. These are not demos; they are the actual motivation for open-sourcing the framework.
Why now? The agent-deployment inflection point
A year ago, agents triggered less than 3% of deployments on Vercel. That number is now around 29%, with Vercel expecting agents to account for half of all deployments before long. That shift matches a broader pattern: as of June 2026, AI coding tools are moving from autocomplete and AI IDEs into engineered agent workflows. The scaffolding around the model matters more than the model itself at this point.
For SaaS builders specifically, this means the question has changed. It used to be 'which model do I use?' Now it is 'which harness do I run it in, and does my stack natively support agent execution?' Eve answers both questions for teams already on Vercel and Next.js, which is most indie SaaS teams building in 2026.
Eve connects at launch to Slack, GitHub, Snowflake, Salesforce, Notion, and Linear, plus anything reachable over OAuth, an API key, or an MCP server. Vercel Connect handles OAuth consent and token refresh automatically. Sessions persist across channels — a workflow started in Slack can continue on the web — which is the kind of stateful behavior that previously required custom infrastructure to build.