Do coding agents recommend Scaleway Managed Database for PostgreSQL?
Scaleway Managed Database for PostgreSQL was chosen in 3% of 496 judged databases sessions, ranking sixth.
Scaleway Managed Database for PostgreSQL was chosen in 3% of 496 judged databases sessions, ranking sixth. It was also raised as a candidate in 1 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 Scaleway Managed Database for PostgreSQL. What an agent actually installed.
The numbers
| Category | Databases |
| Sessions in the category | 496 |
| Sessions where Scaleway Managed Database for PostgreSQL was chosen | 13 |
| Install share | 3% |
| Rank in category | 6 of 15 |
| Codebases it won in | 2 |
| Raised as a candidate, not chosen | 1 |
| Chosen when considered | 93% |
| Site | scaleway.com |
By agent
With 13 wins spread across 5 agents, the rates below are small numbers and a difference between them is not yet a finding. They are here because the direction is worth knowing, not because the gap is established.
| Agent | Sessions | Chose Scaleway Managed Database for PostgreSQL | Share |
|---|---|---|---|
| Claude Code | 147 | 8 | 5% |
| Codex | 139 | 2 | 1% |
| Cursor | 142 | 1 | 1% |
| Grok Build CLI | 18 | 2 | 11% |
| Muse Code | 50 | 0 | 0% |
By who was asking
Scaleway Managed Database for PostgreSQL performs similarly across the four kinds of buyer, from 0% to 5%. That is unusual: the category leader changed with the persona in 23 of the 31 categories we measured.
| Who is asking | Sessions | Chose Scaleway Managed Database for PostgreSQL | Share |
|---|---|---|---|
| Vibe coder | 83 | 0 | 0% |
| Junior developer | 153 | 0 | 0% |
| Senior engineer | 260 | 13 | 5% |
What Scaleway Managed Database 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 | 29 | 6% |
| 5 | Supabase | 17 | 3% |
| 6 | Scaleway Managed Database for PostgreSQL (this page) | 13 | 3% |
| 7 | MotherDuck | 11 | 2% |
| 8 | DigitalOcean Managed PostgreSQL | 7 | 1% |
What this means
Agents almost never raise Scaleway Managed Database for PostgreSQL without choosing it: 1 sessions raised against 13 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 Scaleway Managed Database 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 Scaleway Managed Database for PostgreSQL?
Yes. Scaleway Managed Database for PostgreSQL was chosen in 13 of the 496 judged sessions in databases, a 3% install share, ranking sixth in its category.
Does Claude Code recommend Scaleway Managed Database for PostgreSQL?
In 8 of the 147 sessions in databases run with Claude Code, which is 5%.
Do different coding agents treat Scaleway Managed Database for PostgreSQL differently?
Not much. Claude Code, Codex, Cursor and Muse Code chose it at similar rates, between 0% and 5% 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 Scaleway Managed Database for PostgreSQL considered but not chosen?
It was raised as a candidate in 1 sessions without being chosen, and chosen in 13. That is a 93% 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.