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] · stability 1.00
- 1 PostgreSQL 0.95 “for the large majority of new transactional web applications, PostgreSQL (hosted/managed) is the best starting point.”
- 2 PostgreSQL 0.98 The answer's short answer states: 'for most new transactional web applications, a managed PostgreSQL ... is the best starting point.'
- 3 PostgreSQL 0.95 "For the large majority of new transactional web applications: use PostgreSQL (managed service such as Amazon RDS/Aurora, Google Cloud SQL, or Azure Database for PostgreSQL)."
Claude modal PostgreSQL [PostgreSQL, PostgreSQL, PostgreSQL] · stability 1.00
- 1 PostgreSQL 0.95 The answer explicitly states 'Start with PostgreSQL' as its default recommendation and labels it as the 'Most Popular Choice' that 'handles most scenarios well and rarely becomes a bottleneck.'
- 2 PostgreSQL 0.95 The answer explicitly states 'Start with PostgreSQL' as the recommendation for most cases, calling it 'the safe default' for transactional web applications and 'Most Common Choice' with 'excellent ACID compliance' and good scalability.
- 3 PostgreSQL 0.95 Default recommendation: PostgreSQL - ACID compliance, mature & stable, rich features, open source, excellent scaling. My suggestion for most cases: Start with PostgreSQL unless you have specific reasons otherwise.
Gemini modal PostgreSQL [PostgreSQL, PostgreSQL, PostgreSQL] · stability 1.00
- 1 PostgreSQL 1.00 The answer states that for 95% of new transactional web applications, the clear, industry-standard answer is PostgreSQL.
- 2 PostgreSQL 1.00 The answer identifies PostgreSQL as the clear, industry-standard default choice and concludes with 'The Verdict: Start with PostgreSQL'.
- 3 PostgreSQL 0.99 The assistant states that 'the undisputed default choice is PostgreSQL' and summarizes with 'Start with: 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.