Recommendations · open-entity · rec-database-oltp-01
What is the best database for a new transactional web application?
0.00
Divergence
1.00
Avg stability
0%
Refusal rate
3
Models
Where each model stands
ChatGPTPostgreSQL×100%
ClaudePostgreSQL×100%
GeminiPostgreSQL×100%
ChatGPT modal PostgreSQL [PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL] · stability 1.00
- 1 PostgreSQL 0.95 The answer's short answer: "for most new transactional web applications, a managed PostgreSQL ... is the best choice."
- 2 PostgreSQL 0.95 The answer opens with: 'for almost every new transactional web application, start with PostgreSQL (managed...)' and the 'Recommended options by use case' lists PostgreSQL as the general-purpose choice.
- 3 PostgreSQL 0.95 “Short answer: in almost all cases the best default is PostgreSQL (managed if you don’t want to run infra yourself).” — recommends PostgreSQL as the default for transactional web apps.
- 4 PostgreSQL 0.95 The answer's short answer: "For most new transactional web applications, a managed PostgreSQL (e.g., Amazon RDS/Aurora Postgres, Google Cloud SQL, Neon, Supabase, Heroku Postgres) is the best choice.", recommending managed Postgres as the default.
- 5 PostgreSQL 0.96 The answer opens: “Short answer: for almost every new transactional web app, pick PostgreSQL (hosted as a managed service ...).”
Claude modal PostgreSQL [PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL] · stability 1.00
- 1 PostgreSQL 0.95 The answer explicitly states 'Start with PostgreSQL' as the primary recommendation, calling it 'Most recommended' and noting it's best for 'most transactional apps' with 'excellent ACID compliance, reliable transactions' and 'room to grow.'
- 2 PostgreSQL 0.95 Default choice: PostgreSQL - Best all-around option for most cases with strong ACID guarantees, excellent relational data modeling, and the recommendation to 'Start with PostgreSQL unless you have a specific reason not to.'
- 3 PostgreSQL 0.95 The answer explicitly states 'My recommendation for most new apps: PostgreSQL — it's battle-tested, feature-rich, and you won't outgrow it quickly. Start here unless you have specific constraints pushing you elsewhere.' It also highlights PostgreSQL as 'Most common choice for new web apps' and the primary recommendation for transactional applications with strong ACID guarantees.
- 4 PostgreSQL 0.92 The answer explicitly states 'Start with PostgreSQL' as its recommendation for most cases, describing it as 'often the safest choice' that 'scales with your needs, has excellent ACID guarantees, and rarely becomes a bottleneck as you grow.'
- 5 PostgreSQL 0.95 The answer explicitly states 'For most transactional web applications, PostgreSQL is the safest choice' and recommends it as the 'Strong Default' with multiple advantages listed (ACID compliance, reliability, cost-effectiveness). It further advises startups to 'Start with PostgreSQL' as the primary recommendation.
Gemini modal PostgreSQL [PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL] · stability 1.00
- 1 PostgreSQL 1.00 The answer states that 'the default, industry-standard recommendation is PostgreSQL' and advises to 'Start with PostgreSQL' on Day 1.
- 2 PostgreSQL 1.00 The answer directly names PostgreSQL as the best choice, stating: 'For 90% of new transactional web applications today, the best default choice is PostgreSQL.'
- 3 PostgreSQL 1.00 For 95% of new transactional web applications, the best default choice is PostgreSQL.
- 4 PostgreSQL 1.00 The answer directly states that 'the single best, most widely recommended database today is PostgreSQL' and names it the 'default winner'.
- 5 PostgreSQL 1.00 The answer states: 'For 90% of new transactional web applications, the best default choice is PostgreSQL.'
Change over time
No change from the prior run — every model's modal stance held.
Every stance label is a derived judgment over the model's free-text answer, kept auditable against the original transcript in the run's raw data. Method: /methodology.