Do coding agents recommend AWS Lambda?
AWS Lambda is the most chosen serverless platform, taking 24% of 476 judged serverless compute sessions.
AWS Lambda is the most chosen serverless platform, taking 24% of 476 judged serverless compute sessions. It was also raised as a candidate in 221 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 serverless compute inside a realistic codebase. Not what a chat assistant says about AWS Lambda. What an agent actually installed.
The numbers
| Category | Serverless compute |
| Sessions in the category | 476 |
| Sessions where AWS Lambda was chosen | 114 |
| Install share | 24% |
| Rank in category | 1 of 14 |
| Codebases it won in | 6 |
| Raised as a candidate, not chosen | 221 |
| Chosen when considered | 34% |
| Site | aws.amazon.com |
By agent
The agents treat AWS Lambda very differently. Codex chose it in 47% of its sessions in this category and Claude Code in 8%, a spread of 39 points. Grok Build CLI ran fewer than 30 sessions here, too few to compare.
| Agent | Sessions | Chose AWS Lambda | Share |
|---|---|---|---|
| Claude Code | 120 | 9 | 8% |
| Codex | 144 | 67 | 47% |
| Cursor | 119 | 22 | 18% |
| Grok Build CLI | 22 | 6 | 27% |
| Muse Code | 71 | 10 | 14% |
A single blended install share would report the midpoint and hide both ends. If most of your users run Claude Code, your real position here is 8%, not 24%.
By who was asking
AWS Lambda does much better with one kind of buyer than another. It won 33% of sessions asked as enterprise team and 5% of those asked as vibe coder.
| Who is asking | Sessions | Chose AWS Lambda | Share |
|---|---|---|---|
| Vibe coder | 60 | 3 | 5% |
| Junior developer | 119 | 14 | 12% |
| Senior engineer | 177 | 57 | 32% |
| Enterprise team | 120 | 40 | 33% |
What AWS Lambda was up against
The full ranking in serverless compute, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | AWS Lambda (this page) | 114 | 24% |
| 2 | Vercel Functions | 110 | 23% |
| 3 | Built in-house (no product adopted) | 88 | 18% |
| 4 | Azure Functions | 59 | 12% |
| 5 | Cloudflare Workers | 30 | 6% |
| 6 | Google Cloud Run | 14 | 3% |
| 7 | Inngest | 8 | 2% |
| 8 | Fly.io | 8 | 2% |
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 476 sessions in serverless compute 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 serverless compute run can be replayed on the board.
If you work on AWS Lambda: 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 AWS Lambda?
Yes. AWS Lambda was chosen in 114 of the 476 judged sessions in serverless compute, a 24% install share, ranking first in its category.
Does Claude Code recommend AWS Lambda?
In 9 of the 120 sessions in serverless compute run with Claude Code, which is 8%.
Do different coding agents treat AWS Lambda differently?
Yes, and by a wide margin. Codex chose it in 47% of its runs and Claude Code in 8%.
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 AWS Lambda considered but not chosen?
It was raised as a candidate in 221 sessions without being chosen, and chosen in 114. That is a 34% 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.