Vercel agents now trigger 29% of its deployments

Agents now trigger 29 percent of deployments on Vercel's platform, up from under 3 percent a year ago, per Guillermo Rauch's August 3 post.

Not a self-reported productivity number. It's a platform-wide count of who's pushing the deploy button across Vercel's customer base. That's a 10x jump in twelve months, on a metric that's hard to fake.

Rauch's post described @v, an internal agent handling operations across finance, comms, docs, marketing, engineering, and business analytics. It's seeded by skills the team writes, then self-improves, with per-user memories and personalized schedules. Rauch closed by extrapolating to agents running whole companies someday, which I'd discount.

The d0 data analyst fields more than 30,000 questions a month, each one scoped to the asker's own permissions. An autonomous SDR costs about $5,000 a year, returns 32x, and is maintained part-time by one engineer.

Athena took Vercel's RevOps team six weeks to build with no engineers involved. Vertex resolves 92 percent of support tickets unaided.

The substrate is copyable

All of it runs on Eve, the TypeScript agent framework Vercel open-sourced at Ship 26 on June 17. Skills and instructions are plain markdown files, and Vercel Sandbox policy-gates what data each agent can touch and what leaves. Each agent is a directory of files mapped to capabilities.

Cursor put out a matching number the same week. Cloud agents authored roughly 10 percent of merged pull requests in December, climbing past 50 percent by publication. No boot times or concurrency figures came with it, so I'd treat that 50 percent as self-reported.

The setup runs on Ubuntu VMs instead of local Macs, with a custom CLI called anydev starting every service.

Every figure here comes from the company selling the agent. Vercel's 92 percent ticket resolution deserves the same skepticism: a r/SaaS thread on AI contact centers tells a messier story than vendor deflection numbers do.