Do coding agents recommend Amazon RDS for PostgreSQL?
Amazon RDS for PostgreSQL was chosen in 6% of 496 judged databases sessions, ranking fourth.
Amazon RDS for PostgreSQL was chosen in 6% of 496 judged databases sessions, ranking fourth. It was also raised as a candidate in 192 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 databases inside a realistic codebase. Not what a chat assistant says about Amazon RDS for PostgreSQL. What an agent actually installed.
The numbers
| Category | Databases |
| Sessions in the category | 496 |
| Sessions where Amazon RDS for PostgreSQL was chosen | 29 |
| Install share | 6% |
| Rank in category | 4 of 15 |
| Codebases it won in | 2 |
| Raised as a candidate, not chosen | 192 |
| Chosen when considered | 13% |
| Site | aws.amazon.com |
By agent
Claude Code, Codex, Cursor and Muse Code land within 9 points of each other on Amazon RDS for PostgreSQL, which is closer than most products in this experiment manage. Grok Build CLI ran fewer than 30 sessions here, too few to compare.
| Agent | Sessions | Chose Amazon RDS for PostgreSQL | Share |
|---|---|---|---|
| Claude Code | 147 | 6 | 4% |
| Codex | 139 | 15 | 11% |
| Cursor | 142 | 6 | 4% |
| Grok Build CLI | 18 | 1 | 6% |
| Muse Code | 50 | 1 | 2% |
By who was asking
Amazon RDS for PostgreSQL performs similarly across the four kinds of buyer, from 0% to 11%. That is unusual: the category leader changed with the persona in 23 of the 31 categories we measured.
| Who is asking | Sessions | Chose Amazon RDS for PostgreSQL | Share |
|---|---|---|---|
| Vibe coder | 83 | 0 | 0% |
| Junior developer | 153 | 0 | 0% |
| Senior engineer | 260 | 29 | 11% |
What Amazon RDS for PostgreSQL was up against
The full ranking in databases, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Neon | 316 | 64% |
| 2 | Azure Database for PostgreSQL Flexible Server | 45 | 9% |
| 3 | Azure SQL Database | 41 | 8% |
| 4 | Amazon RDS for PostgreSQL (this page) | 29 | 6% |
| 5 | Supabase | 17 | 3% |
| 6 | Scaleway Managed Database for PostgreSQL | 13 | 3% |
| 7 | MotherDuck | 11 | 2% |
| 8 | DigitalOcean Managed PostgreSQL | 7 | 1% |
What this means
This is an integration problem, not a presence problem. Agents raised Amazon RDS for PostgreSQL in 192 sessions and chose it in 29, so it reaches the shortlist and then loses. Something at the last step is costing the session, and in our data that is usually a quickstart that does not run when pasted, documentation describing an interface that changed, or a package name that does not match the product name.
That is the cheaper of the two problems to have. The reason is written down in each losing transcript.
Where these numbers come from
The 496 sessions in databases are part of a published set of 15,051, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.
Every databases run can be replayed on the board.
If you work on Amazon RDS for PostgreSQL: 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 Amazon RDS for PostgreSQL?
Yes. Amazon RDS for PostgreSQL was chosen in 29 of the 496 judged sessions in databases, a 6% install share, ranking fourth in its category.
Does Claude Code recommend Amazon RDS for PostgreSQL?
In 6 of the 147 sessions in databases run with Claude Code, which is 4%.
Do different coding agents treat Amazon RDS for PostgreSQL differently?
Not much. Claude Code, Codex, Cursor and Muse Code chose it at similar rates, between 2% and 11% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 92 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 Amazon RDS for PostgreSQL considered but not chosen?
It was raised as a candidate in 192 sessions without being chosen, and chosen in 29. That is a 13% conversion from considered to chosen.
Where this comes from
Armature ran 15,051 judged sessions with Claude Code, Codex, Cursor, Grok Build CLI and Muse Code inside 92 realistic codebases, and published every run. The numbers on this page come from that work.