Do coding agents recommend Vercel?
Vercel is the most chosen hosting platform, taking 39% of 508 judged deployment sessions.
Vercel is the most chosen hosting platform, taking 39% of 508 judged deployment sessions. It was also raised as a candidate in 231 further sessions without being chosen.
This page reports what happened when Claude Code, Codex, Cursor, Grok Build CLI and Muse Code had to solve a problem in deployment inside a realistic codebase. Not what a chat assistant says about Vercel. What an agent actually installed.
The numbers
| Category | Deployment |
| Sessions in the category | 508 |
| Sessions where Vercel was chosen | 197 |
| Install share | 39% |
| Rank in category | 1 of 10 |
| Codebases it won in | 6 |
| Raised as a candidate, not chosen | 231 |
| Chosen when considered | 46% |
| Site | vercel.com |
By agent
Claude Code, Codex, Cursor, Grok Build CLI and Muse Code land within 11 points of each other on Vercel, which is closer than most products in this experiment manage.
| Agent | Sessions | Chose Vercel | Share |
|---|---|---|---|
| Claude Code | 120 | 51 | 43% |
| Codex | 150 | 50 | 33% |
| Cursor | 119 | 52 | 44% |
| Grok Build CLI | 30 | 10 | 33% |
| Muse Code | 89 | 34 | 38% |
By who was asking
Vercel performs similarly across the four kinds of buyer, from 37% to 40%. That is unusual: the category leader changed with the persona in 24 of the 31 categories we measured.
| Who is asking | Sessions | Chose Vercel | Share |
|---|---|---|---|
| Vibe coder | 254 | 95 | 37% |
| Senior engineer | 254 | 102 | 40% |
What Vercel was up against
The full ranking in deployment, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Vercel (this page) | 197 | 39% |
| 2 | Render | 193 | 38% |
| 3 | Cloudflare | 59 | 12% |
| 4 | GitHub Pages | 26 | 5% |
| 5 | Railway | 17 | 3% |
| 6 | Netlify | 9 | 2% |
| 7 | Fly.io | 4 | 1% |
| 8 | Google Cloud | 1 | 0% |
What this means
Leading a category is a position to defend rather than a result to celebrate. In our data, leaders lose ground in exactly two situations: when the person asking is an enterprise buyer with procurement constraints, and when a competitor's documentation is easier for an agent to integrate correctly.
The defence is unglamorous. Keep the quickstart running. Keep the version current on the page. Keep the names aligned. Stay in the templates.
Where these numbers come from
The 508 sessions in deployment are part of a published set of 15,287, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every deployment run can be replayed on the board.
If you work on Vercel: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.
<!-- generated by scripts/write-data-pages.mjs -->
Common questions
Do coding agents recommend Vercel?
Yes. Vercel was chosen in 197 of the 508 judged sessions in deployment, a 39% install share, ranking first in its category.
Does Claude Code recommend Vercel?
In 51 of the 120 sessions in deployment run with Claude Code, which is 43%.
Do different coding agents treat Vercel differently?
Yes, and by a wide margin. Cursor chose it in 44% of its runs and Codex in 33%.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 110 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.
How often is Vercel considered but not chosen?
It was raised as a candidate in 231 sessions without being chosen, and chosen in 197. That is a 46% conversion from considered to chosen.
Where this comes from
Armature ran 15,287 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 110 realistic codebases, and published every run. The numbers on this page come from that work.