Do coding agents recommend Azure Database for PostgreSQL Flexible Server?
Azure Database for PostgreSQL Flexible Server was chosen in 8% of 356 judged databases sessions, ranking third. Measured with Claude Code, Codex and Cursor.
Azure Database for PostgreSQL Flexible Server was chosen in 8% of 356 judged databases sessions, ranking third. It was also raised as a candidate in 21 further sessions without being chosen.
This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in databases inside a realistic codebase. Not what a chat assistant says about Azure Database for PostgreSQL Flexible Server. What an agent actually installed.
One thing to read first: every one of those wins came from a single codebase. That is a result about one repository rather than about databases in general, and the splits below cannot separate the two. Treat them as a description of that repository.
The numbers
| Category | Databases |
| Sessions in the category | 356 |
| Sessions where Azure Database for PostgreSQL Flexible Server was chosen | 29 |
| Install share | 8% |
| Rank in category | 3 of 14 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 21 |
| Chosen when considered | 58% |
| Site | azure.microsoft.com |
By agent
The three agents land within 6 points of each other on Azure Database for PostgreSQL Flexible Server, which is closer than most products in this experiment manage.
| Agent | Sessions | Chose Azure Database for PostgreSQL Flexible Server | Share |
|---|---|---|---|
| Claude Code | 129 | 16 | 12% |
| Codex | 103 | 6 | 6% |
| Cursor | 124 | 7 | 6% |
By who was asking
Azure Database for PostgreSQL Flexible Server does much better with one kind of buyer than another. It won 15% of sessions asked as senior engineer and 0% of those asked as junior developer.
| Who is asking | Sessions | Chose Azure Database for PostgreSQL Flexible Server | Share |
|---|---|---|---|
| Vibe coder | 60 | 0 | 0% |
| Junior developer | 106 | 0 | 0% |
| Senior engineer | 190 | 29 | 15% |
What Azure Database for PostgreSQL Flexible Server was up against
The full ranking in databases, from the same sessions:
| # | Product | Runs won | Share |
|---|---|---|---|
| 1 | Neon | 236 | 66% |
| 2 | Azure SQL Database | 35 | 10% |
| 3 | Azure Database for PostgreSQL Flexible Server (this page) | 29 | 8% |
| 4 | Amazon RDS for PostgreSQL | 17 | 5% |
| 5 | Supabase | 10 | 3% |
| 6 | MotherDuck | 7 | 2% |
| 7 | Scaleway Managed Database for PostgreSQL | 7 | 2% |
| 8 | Aiven | 5 | 1% |
What this means
Agents almost never raise Azure Database for PostgreSQL Flexible Server without choosing it: 21 sessions raised against 29 chosen. When it gets considered, it usually wins. The constraint is how rarely it gets considered at all, which is a presence problem: templates, framework integrations and pages that answer the configuration and production questions agents actually search for.
Where these numbers come from
The 356 sessions in databases are part of a published set of 5,292, 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 Azure Database for PostgreSQL Flexible Server: 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 Azure Database for PostgreSQL Flexible Server?
Yes. Azure Database for PostgreSQL Flexible Server was chosen in 29 of the 356 judged sessions in databases, a 8% install share, ranking third in its category.
Does Claude Code recommend Azure Database for PostgreSQL Flexible Server?
In 16 of the 129 sessions in databases run with Claude Code, which is 12%.
Do different coding agents treat Azure Database for PostgreSQL Flexible Server differently?
Not much. The three agents chose it at similar rates, between 6% and 12% of their runs.
How was this measured?
Real coding agents at pinned versions were run in sandboxes inside 51 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 Azure Database for PostgreSQL Flexible Server considered but not chosen?
It was raised as a candidate in 21 sessions without being chosen, and chosen in 29. That is a 58% conversion from considered to chosen.
Where this comes from
Armature ran 5,292 judged sessions with Claude Code, Codex and Cursor inside 51 realistic codebases, and published every run. The numbers on this page come from that work.