Vercel uses eve as a shared platform for agents across support, sales, engineering, and daily operations. Its launch account described more than 100 agents in production. That figure counts deployed agents; it does not state how many workers ran simultaneously on one task.

What is Vercel eve?

eve is an open-source framework for defining, running, and operating agents. Vercel says employees had already shipped hundreds of internal agents and apps, each with its own version of scheduling, state, tools, permissions, and monitoring. eve turns those recurring needs into a standard platform.

An eve agent is a directory of files. The code, instructions, tools, skills, smaller agents, channels, and schedules live together and can be reviewed in source control. Durable workflows save checkpoints, so a long run can survive a crash or deployment. Generated code runs in an isolated sandbox. OpenTelemetry, an industry standard for recording what software did, exposes each step. Evals, or repeatable checks of agent behavior, can run locally or in continuous integration (CI), the automated build-and-test process for proposed code.

This is agentic infrastructure: the shared machinery that lets many agents operate without every team rebuilding identity, execution, memory, observability, and release controls.

How does Vercel use eve internally?

Vercel says eve is the framework it builds and runs its own agents on. Its launch account names more than 100 agents in production. Examples include d0 for internal questions, a lead agent for sales, Athena for revenue operations, Vertex for support, and coding-related agents such as draft0 and V.

The examples show how one agent platform can support different kinds of business work. Each named agent has its own purpose and success criteria. Vercel's outcome figures are company reports with different populations and acceptance rules, so they should be read individually.

How do permissions and human approval work?

The open framework can pause an action for a person's approval without keeping compute running. Vercel's managed stack adds private-by-default internal apps, employee identity, short-lived task-scoped connections to services, and audit trails. The launch material describes connections to systems such as Slack, GitHub, Snowflake, Salesforce, and Linear.

eve itself is Apache-2.0 open source. Some identity, connectivity, and hosting controls are managed Vercel services and were in beta or private beta when announced. Teams adopting the open framework would still need to supply those services or equivalent controls.

What does eve look like as a software factory?

Vercel Labs publishes an eve Software Factory Template called Foreman. A classifier routes work, an analyst researches it, an implementer changes code, and an independent reviewer inspects the pushed branch. Red CI can send work back through the loop. A person reviews, marks the pull request ready, and merges it.

Each Foreman role has its own agent and sandbox. The reviewer inspects the proposed change separately from the implementer's private reasoning. Public evidence does not show that Vercel's own engineering organization runs Foreman internally; the repository establishes a reference design built on eve.

How does Vercel describe safe operation?

Vercel's safety writing says green CI is insufficient. An engineer should understand and own agent output. It describes canary releases, which expose a change to a small audience first, plus rollback, runtime verification, executable skills and guardrails, static checks, production-like end-to-end tests, read-only verifier agents, and defect measures.

Some of that language describes current capabilities and some describes investment direction. Support for a control does not prove that every internal eve agent uses it.

What can teams share across different agents?

Several agent workflows can share the same services for storing progress, running code in isolation, supplying credentials, and recording actions. Definitions can live in reviewable files, and evals can run alongside ordinary tests. Teams can also reuse their existing preview, approval, release, and rollback process.

The eve repository identified the framework as beta in the September 1, 2026 source window. Its conventions and APIs may change. Vercel's platform-wide agent deployment statistics describe all customers on Vercel and need to remain separate from its internal agent count.