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

Refusal rate

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.90 The answer's short/default recommendation: "Use PostgreSQL ... for a new transactional web application unless you have clear requirements forcing a different choice."
2 PostgreSQL 0.95 "Short answer: For most new transactional web applications, start with PostgreSQL (preferably a managed service...)"
3 PostgreSQL 0.96 The answer begins: 'Short answer: in most cases a relational database — specifically PostgreSQL (managed or self-hosted) — is the best starting point for a new transactional web application.'
4 PostgreSQL 0.95 The answer's short answer: 'For most new transactional web apps, use PostgreSQL (typically a managed cloud service...)' and repeated recommendations to start with managed PostgreSQL for MVPs.
5 PostgreSQL 0.95 "Short answer: for almost any new transactional web application you should start with a managed relational ACID database — most commonly PostgreSQL (managed on RDS/Aurora, Cloud SQL, Azure DB, Neon, etc.)."

Claude modal PostgreSQL [PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL] · stability 1.00

1 PostgreSQL 0.95 The answer explicitly states PostgreSQL as 'Most Common Choice' and 'Best for: Most transactional applications,' and concludes with 'My recommendation: Start with PostgreSQL unless you have specific constraints.'
2 PostgreSQL 0.95 The answer explicitly states 'Most Common Choice: PostgreSQL' and concludes 'Start with PostgreSQL unless you have specific reasons otherwise. It's battle-tested, free, and handles growth well.' This is presented as the primary recommendation for transactional web applications.
3 PostgreSQL 0.95 The answer explicitly states 'Most Common Choice: PostgreSQL' and 'Start with PostgreSQL unless you have specific reasons otherwise. It handles transactions well, scales reasonably, and won't box you in early.'
4 PostgreSQL 0.95 The answer explicitly states 'Start with PostgreSQL' as the recommendation for most new web applications, positioning it as the 'Most Popular Choice' with excellent ACID compliance and describing it as 'powerful enough to grow with you and won't force a migration later.'
5 PostgreSQL 0.95 The answer explicitly states 'Default recommendation: Start with PostgreSQL — it's battle-tested, feature-rich, and scales well' and lists it as '(Most Common Recommendation)' with the note that it is 'Best for: Most transactional apps, especially if you need relational data integrity'

Gemini modal PostgreSQL [PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL, PostgreSQL] · stability 1.00

1 PostgreSQL 1.00 The assistant states that 'the clear consensus best choice today is PostgreSQL' and advises to 'Start with PostgreSQL on a managed provider'.
2 PostgreSQL 1.00 The text states that 'the best default choice is PostgreSQL' and summarizes in the verdict to 'Start with PostgreSQL.'
3 PostgreSQL 1.00 The answer directly states that 'For 95% of new transactional web applications, the best choice is PostgreSQL' and summarizes with 'Pick PostgreSQL.'
4 PostgreSQL 1.00 The answer directly states that 'the clear industry-standard choice is PostgreSQL' and describes it as the safest, most flexible, and most future-proof starting decision.
5 PostgreSQL 1.00 The assistant declares that 'For a vast majority of new transactional web applications, the undisputed default choice is PostgreSQL' and finishes with 'The Verdict: 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.