From the experiment

Do coding agents recommend Azure Database for PostgreSQL Flexible Server?

Azure Database for PostgreSQL Flexible Server was chosen in 9% of 496 judged databases sessions, ranking second.

Published September 28, 2026 Updated September 29, 2026 Read as Markdown

Azure Database for PostgreSQL Flexible Server was chosen in 9% of 496 judged databases sessions, ranking second. It was also raised as a candidate in 27 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 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

CategoryDatabases
Sessions in the category496
Sessions where Azure Database for PostgreSQL Flexible Server was chosen45
Install share9%
Rank in category2 of 15
Codebases it won in1
Raised as a candidate, not chosen27
Chosen when considered63%
Siteazure.microsoft.com

By agent

Claude Code, Codex, Cursor and Muse Code land within 6 points of each other on Azure Database for PostgreSQL Flexible Server, which is closer than most products in this experiment manage. Grok Build CLI ran fewer than 30 sessions here, too few to compare.

AgentSessionsChose Azure Database for PostgreSQL Flexible ServerShare
Claude Code1471812%
Codex139107%
Cursor14296%
Grok Build CLI18211%
Muse Code50612%

By who was asking

Azure Database for PostgreSQL Flexible Server does much better with one kind of buyer than another. It won 17% of sessions asked as senior engineer and 0% of those asked as junior developer.

Who is askingSessionsChose Azure Database for PostgreSQL Flexible ServerShare
Vibe coder8300%
Junior developer15300%
Senior engineer2604517%

What Azure Database for PostgreSQL Flexible Server was up against

The full ranking in databases, from the same sessions:

#ProductRuns wonShare
1Neon31664%
2Azure Database for PostgreSQL Flexible Server (this page)459%
3Azure SQL Database418%
4Amazon RDS for PostgreSQL296%
5Supabase173%
6Scaleway Managed Database for PostgreSQL133%
7MotherDuck112%
8DigitalOcean Managed PostgreSQL71%

What this means

Agents almost never raise Azure Database for PostgreSQL Flexible Server without choosing it: 27 sessions raised against 45 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 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 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 45 of the 496 judged sessions in databases, a 9% install share, ranking second in its category.

Does Claude Code recommend Azure Database for PostgreSQL Flexible Server?

In 18 of the 147 sessions in databases run with Claude Code, which is 12%.

Do different coding agents treat Azure Database for PostgreSQL Flexible Server differently?

Not much. Claude Code, Codex, Cursor and Muse Code 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 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 Azure Database for PostgreSQL Flexible Server considered but not chosen?

It was raised as a candidate in 27 sessions without being chosen, and chosen in 45. That is a 63% 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.

Read next

All library pages