Do coding agents recommend Azure Database for PostgreSQL Flexible Server?
Azure Database for PostgreSQL Flexible Server was chosen in 3% of 732 judged databases sessions, ranking fourth. Measured with Claude Code, Codex and Cursor.
Azure Database for PostgreSQL Flexible Server was chosen in 3% of 732 judged databases sessions, ranking fourth. It was also raised as a candidate in 1 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 | 732 |
| Sessions where Azure Database for PostgreSQL Flexible Server was chosen | 21 |
| Install share | 3% |
| Rank in category | 4 of 19 |
| Codebases it won in | 1 |
| Raised as a candidate, not chosen | 1 |
| Chosen when considered | 95% |
| Site | azure.microsoft.com |
By agent
Claude Code, Codex and Cursor agree closely on Azure Database for PostgreSQL Flexible Server, choosing it at rates within 0 points of each other.
| Agent | Sessions | Chose Azure Database for PostgreSQL Flexible Server | Share |
|---|---|---|---|
| Claude Code | 380 | 10 | 3% |
| Codex | 181 | 6 | 3% |
| Cursor | 171 | 5 | 3% |
By who was asking
Azure Database for PostgreSQL Flexible Server does much better with one kind of buyer than another. It won 88% of sessions asked as enterprise team and 0% of those asked as senior engineer.
| Who is asking | Sessions | Chose Azure Database for PostgreSQL Flexible Server | Share |
|---|---|---|---|
| Vibe coder | 417 | 0 | 0% |
| Junior developer | 163 | 0 | 0% |
| Senior engineer | 113 | 0 | 0% |
| Enterprise team | 24 | 21 | 88% |
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 | 334 | 46% |
| 2 | Supabase | 269 | 37% |
| 3 | Turso | 48 | 7% |
| 4 | Azure Database for PostgreSQL Flexible Server (this page) | 21 | 3% |
| 5 | Firebase | 17 | 2% |
| 6 | Google Sheets | 10 | 1% |
| 7 | Netlify Forms | 6 | 1% |
| 8 | Formspree | 4 | 1% |
What this means
Agents almost never raise Azure Database for PostgreSQL Flexible Server without choosing it: 1 sessions raised against 21 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 732 sessions in databases 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 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 21 of the 732 judged sessions in databases, a 3% install share, ranking fourth in its category.
Does Claude Code recommend Azure Database for PostgreSQL Flexible Server?
In 10 of the 380 sessions in databases run with Claude Code, which is 3%.
Do different coding agents treat Azure Database for PostgreSQL Flexible Server differently?
Not much. Claude Code, Codex and Cursor chose it at similar rates, between 3% and 3% of their runs.
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 Azure Database for PostgreSQL Flexible Server considered but not chosen?
It was raised as a candidate in 1 sessions without being chosen, and chosen in 21. That is a 95% 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.