AI Index / Database-as-a-service platforms / History

Database-as-a-service platforms — AI Recommendation History

What AI assistants recommended for database-as-a-service platforms, date by date. Every ranking we publish is frozen the day it publishes, so this is a record of what was said — not a re-computation of what today's data would say about the past.

Record: 26 dated snapshots · Aug 14, 2026 – Sep 8, 2026

Answer archive Methodology Data studies JSON

What changed

Computed by comparing each dated snapshot with the one before it. Share moves smaller than 1pp are treated as noise and left out — the same threshold that suppresses trend arrows on the ranking.

Sep 8, 2026vs Sep 7, 2026

No change above the noise floor.

Sep 7, 2026vs Sep 6, 2026

No change above the noise floor.

Sep 6, 2026vs Sep 5, 2026

No change above the noise floor.

Sep 5, 2026vs Sep 4, 2026

No change above the noise floor.

Sep 4, 2026vs Sep 3, 2026

No change above the noise floor.

Sep 3, 2026vs Sep 2, 2026

No change above the noise floor.

Sep 2, 2026vs Sep 1, 2026

No change above the noise floor.

Sep 1, 2026vs Aug 31, 2026

Methodology change: extraction rules 4-7 → 7 between these dates. Differences below may reflect the rule change rather than a change in what AI recommends — see the methodology changelog.

▲ INAzure entered the top 10 (#11 → #6)
▼ OUTDigitalOcean left the top 10 (#9 → #14)
▲Azure moved #11 → #6
▼DigitalOcean moved #9 → #14
▲PostgreSQL moved #2 → #1
▼Neon moved #1 → #2
▲Supabase moved #4 → #3
▼MySQL moved #3 → #4
▼PlanetScale moved #6 → #7
▼MongoDB moved #7 → #8
▼CockroachDB moved #8 → #9
▲Azure +19.1pp (23.8% → 42.9%)
▼DigitalOcean -14.3pp (28.6% → 14.3%)
▼PlanetScale -11.5pp (50.8% → 39.3%)
▼MongoDB -7.2pp (42.9% → 35.7%)
▼MySQL -7.1pp (71.4% → 64.3%)
▼Vitess -5.6pp (27% → 21.4%)
▼CockroachDB -5.2pp (30.2% → 25%)
▼AWS -4pp (68.3% → 64.3%)
▼Supabase -3.5pp (71.4% → 67.9%)
▲PostgreSQL +2pp (73% → 75%)

Aug 31, 2026vs Aug 30, 2026

No change above the noise floor.

Aug 30, 2026vs Aug 29, 2026

No change above the noise floor.

Aug 29, 2026vs Aug 28, 2026

No change above the noise floor.

Aug 28, 2026vs Aug 27, 2026

▲Neon moved #2 → #1
▼PostgreSQL moved #1 → #2
▲MySQL moved #4 → #3
▼Supabase moved #3 → #4
▼PostgreSQL -3.8pp (76.8% → 73%)
▼MongoDB -3.5pp (46.4% → 42.9%)
▼CockroachDB -1.9pp (32.1% → 30.2%)
▼Supabase -1.8pp (73.2% → 71.4%)
▼DigitalOcean -1.8pp (30.4% → 28.6%)
▼AWS -1.3pp (69.6% → 68.3%)
▼PlanetScale -1pp (51.8% → 50.8%)

Aug 27, 2026vs Aug 26, 2026

Methodology change: extraction rules 4 → 4-7 between these dates. Differences below may reflect the rule change rather than a change in what AI recommends — see the methodology changelog.

▲PostgreSQL moved #4 → #1
▼MySQL moved #1 → #4
▲Neon moved #3 → #2
▼Supabase moved #2 → #3
▲CockroachDB moved #9 → #8
▼DigitalOcean moved #8 → #9
▼DigitalOcean -9.6pp (40% → 30.4%)
▼PlanetScale -8.2pp (60% → 51.8%)
▼MySQL -5.7pp (77.1% → 71.4%)
▲PostgreSQL +5.4pp (71.4% → 76.8%)
▼Vitess -4.6pp (31.4% → 26.8%)
▼MongoDB -2.2pp (48.6% → 46.4%)
▼CockroachDB -2.2pp (34.3% → 32.1%)
▼AWS -1.8pp (71.4% → 69.6%)
▼Supabase -1.1pp (74.3% → 73.2%)

Aug 26, 2026vs Aug 25, 2026

▲MySQL moved #2 → #1
▼Supabase moved #1 → #2
▲PostgreSQL moved #5 → #4
▼AWS moved #4 → #5
▲Vitess +6.4pp (25% → 31.4%)
▲MySQL +4.2pp (72.9% → 77.1%)
▼CockroachDB -3.2pp (37.5% → 34.3%)
▲DigitalOcean +2.5pp (37.5% → 40%)
▲PlanetScale +1.7pp (58.3% → 60%)
▼AWS -1.5pp (72.9% → 71.4%)
▲Neon +1.4pp (72.9% → 74.3%)

Aug 25, 2026vs Aug 24, 2026

No change above the noise floor.

Aug 24, 2026vs Aug 23, 2026

No change above the noise floor.

Aug 23, 2026vs Aug 22, 2026

▲Supabase moved #2 → #1
▼MySQL moved #1 → #2
▲AWS moved #5 → #4
▼PostgreSQL moved #4 → #5
▲Supabase +1.5pp (73.5% → 75%)
▲AWS +1.5pp (71.4% → 72.9%)
▼DigitalOcean -1.3pp (38.8% → 37.5%)
▲MongoDB +1pp (46.9% → 47.9%)

Aug 22, 2026vs Aug 21, 2026

▲ INVitess entered the top 10 (#12 → #10)
▼ OUTAzure SQL left the top 10 (#10 → #11)
▲MySQL moved #4 → #1
▼PostgreSQL moved #1 → #4
▲Vitess moved #12 → #10
▲AWS moved #6 → #5
▼PlanetScale moved #5 → #6
▲DigitalOcean moved #9 → #8
▼CockroachDB moved #8 → #9
▼Azure SQL moved #10 → #11
▲AWS +21.4pp (50% → 71.4%)
▲DigitalOcean +7.4pp (31.4% → 38.8%)
▲MySQL +3.5pp (70% → 73.5%)
▲PlanetScale +3.5pp (55.7% → 59.2%)
▲MongoDB +2.6pp (44.3% → 46.9%)
▲Supabase +2.1pp (71.4% → 73.5%)
▲Neon +2.1pp (71.4% → 73.5%)
▼CockroachDB -1.9pp (38.6% → 36.7%)
▼Azure SQL -1.9pp (24.3% → 22.4%)
▲Vitess +1.6pp (22.9% → 24.5%)

Aug 21, 2026vs Aug 20, 2026

No change above the noise floor.

Aug 20, 2026vs Aug 19, 2026

No change above the noise floor.

Aug 19, 2026vs Aug 18, 2026

No change above the noise floor.

Aug 18, 2026vs Aug 17, 2026

No change above the noise floor.

Aug 17, 2026vs Aug 16, 2026

No change above the noise floor.

Aug 16, 2026vs Aug 15, 2026

No change above the noise floor.

Aug 15, 2026vs Aug 14, 2026

No change above the noise floor.

The ranking, date by date

Top 10 on each archived date, exactly as published. Cite a date and it stays true: snapshots are append-only, and a correction appends a new revision rather than overwriting the original.

Sep 8, 202628 sampled answers · window 2026-08-11 – 2026-09-08 · rules v7

#1PostgreSQL75%
#2Neon75%
#3Supabase67.9%
#4MySQL64.3%
#5AWS64.3%
#6Azure42.9%
#7PlanetScale39.3%
#8MongoDB35.7%
#9CockroachDB25%
#10Vitess21.4%

Sep 7, 202628 sampled answers · window 2026-08-10 – 2026-09-07 · rules v7

#1PostgreSQL75%
#2Neon75%
#3Supabase67.9%
#4MySQL64.3%
#5AWS64.3%
#6Azure42.9%
#7PlanetScale39.3%
#8MongoDB35.7%
#9CockroachDB25%
#10Vitess21.4%

Sep 6, 202628 sampled answers · window 2026-08-09 – 2026-09-06 · rules v7

#1PostgreSQL75%
#2Neon75%
#3Supabase67.9%
#4MySQL64.3%
#5AWS64.3%
#6Azure42.9%
#7PlanetScale39.3%
#8MongoDB35.7%
#9CockroachDB25%
#10Vitess21.4%

Sep 5, 202628 sampled answers · window 2026-08-08 – 2026-09-05 · rules v7

#1PostgreSQL75%
#2Neon75%
#3Supabase67.9%
#4MySQL64.3%
#5AWS64.3%
#6Azure42.9%
#7PlanetScale39.3%
#8MongoDB35.7%
#9CockroachDB25%
#10Vitess21.4%

Sep 4, 202628 sampled answers · window 2026-08-07 – 2026-09-04 · rules v7

#1PostgreSQL75%
#2Neon75%
#3Supabase67.9%
#4MySQL64.3%
#5AWS64.3%
#6Azure42.9%
#7PlanetScale39.3%
#8MongoDB35.7%
#9CockroachDB25%
#10Vitess21.4%

Sep 3, 202628 sampled answers · window 2026-08-06 – 2026-09-03 · rules v7

#1PostgreSQL75%
#2Neon75%
#3Supabase67.9%
#4MySQL64.3%
#5AWS64.3%
#6Azure42.9%
#7PlanetScale39.3%
#8MongoDB35.7%
#9CockroachDB25%
#10Vitess21.4%

Sep 2, 202628 sampled answers · window 2026-08-05 – 2026-09-02 · rules v7

#1PostgreSQL75%
#2Neon75%
#3Supabase67.9%
#4MySQL64.3%
#5AWS64.3%
#6Azure42.9%
#7PlanetScale39.3%
#8MongoDB35.7%
#9CockroachDB25%
#10Vitess21.4%

Sep 1, 202628 sampled answers · window 2026-08-04 – 2026-09-01 · rules v7

#1PostgreSQL75%
#2Neon75%
#3Supabase67.9%
#4MySQL64.3%
#5AWS64.3%
#6Azure42.9%
#7PlanetScale39.3%
#8MongoDB35.7%
#9CockroachDB25%
#10Vitess21.4%

Aug 31, 202663 sampled answers · window 2026-08-03 – 2026-08-31 · rules v4-7

#1Neon74.6%
#2PostgreSQL73%
#3MySQL71.4%
#4Supabase71.4%
#5AWS68.3%
#6PlanetScale50.8%
#7MongoDB42.9%
#8CockroachDB30.2%
#9DigitalOcean28.6%
#10Vitess27%

Aug 30, 202663 sampled answers · window 2026-08-02 – 2026-08-30 · rules v4-7

#1Neon74.6%
#2PostgreSQL73%
#3MySQL71.4%
#4Supabase71.4%
#5AWS68.3%
#6PlanetScale50.8%
#7MongoDB42.9%
#8CockroachDB30.2%
#9DigitalOcean28.6%
#10Vitess27%

Aug 29, 202663 sampled answers · window 2026-08-01 – 2026-08-29 · rules v4-7

#1Neon74.6%
#2PostgreSQL73%
#3MySQL71.4%
#4Supabase71.4%
#5AWS68.3%
#6PlanetScale50.8%
#7MongoDB42.9%
#8CockroachDB30.2%
#9DigitalOcean28.6%
#10Vitess27%

Aug 28, 202663 sampled answers · window 2026-07-31 – 2026-08-28 · rules v4-7

#1Neon74.6%
#2PostgreSQL73%
#3MySQL71.4%
#4Supabase71.4%
#5AWS68.3%
#6PlanetScale50.8%
#7MongoDB42.9%
#8CockroachDB30.2%
#9DigitalOcean28.6%
#10Vitess27%

Aug 27, 202656 sampled answers · window 2026-07-30 – 2026-08-27 · rules v4-7

#1PostgreSQL76.8%
#2Neon75%
#3Supabase73.2%
#4MySQL71.4%
#5AWS69.6%
#6PlanetScale51.8%
#7MongoDB46.4%
#8CockroachDB32.1%
#9DigitalOcean30.4%
#10Vitess26.8%

Aug 26, 202635 sampled answers · window 2026-07-29 – 2026-08-26 · rules v4

#1MySQL77.1%
#2Supabase74.3%
#3Neon74.3%
#4PostgreSQL71.4%
#5AWS71.4%
#6PlanetScale60%
#7MongoDB48.6%
#8DigitalOcean40%
#9CockroachDB34.3%
#10Vitess31.4%

Aug 25, 202648 sampled answers · window 2026-07-28 – 2026-08-25 · rules v4

#1Supabase75%
#2MySQL72.9%
#3Neon72.9%
#4AWS72.9%
#5PostgreSQL70.8%
#6PlanetScale58.3%
#7MongoDB47.9%
#8DigitalOcean37.5%
#9CockroachDB37.5%
#10Vitess25%

Aug 24, 202648 sampled answers · window 2026-07-27 – 2026-08-24 · rules v4

#1Supabase75%
#2MySQL72.9%
#3Neon72.9%
#4AWS72.9%
#5PostgreSQL70.8%
#6PlanetScale58.3%
#7MongoDB47.9%
#8DigitalOcean37.5%
#9CockroachDB37.5%
#10Vitess25%

Aug 23, 202648 sampled answers · window 2026-07-26 – 2026-08-23 · rules v4

#1Supabase75%
#2MySQL72.9%
#3Neon72.9%
#4AWS72.9%
#5PostgreSQL70.8%
#6PlanetScale58.3%
#7MongoDB47.9%
#8DigitalOcean37.5%
#9CockroachDB37.5%
#10Vitess25%

Aug 22, 202649 sampled answers · window 2026-07-25 – 2026-08-22 · rules v4

#1MySQL73.5%
#2Supabase73.5%
#3Neon73.5%
#4PostgreSQL71.4%
#5AWS71.4%
#6PlanetScale59.2%
#7MongoDB46.9%
#8DigitalOcean38.8%
#9CockroachDB36.7%
#10Vitess24.5%

Aug 21, 202670 sampled answers · window 2026-07-24 – 2026-08-21 · rules v4

#1PostgreSQL71.4%
#2Supabase71.4%
#3Neon71.4%
#4MySQL70%
#5PlanetScale55.7%
#6AWS50%
#7MongoDB44.3%
#8CockroachDB38.6%
#9DigitalOcean31.4%
#10Azure SQL24.3%

Aug 20, 202670 sampled answers · window 2026-07-23 – 2026-08-20 · rules v4

#1PostgreSQL71.4%
#2Supabase71.4%
#3Neon71.4%
#4MySQL70%
#5PlanetScale55.7%
#6AWS50%
#7MongoDB44.3%
#8CockroachDB38.6%
#9DigitalOcean31.4%
#10Azure SQL24.3%

Aug 19, 202670 sampled answers · window 2026-07-22 – 2026-08-19 · rules v4

#1PostgreSQL71.4%
#2Supabase71.4%
#3Neon71.4%
#4MySQL70%
#5PlanetScale55.7%
#6AWS50%
#7MongoDB44.3%
#8CockroachDB38.6%
#9DigitalOcean31.4%
#10Azure SQL24.3%

Aug 18, 202670 sampled answers · window 2026-07-21 – 2026-08-18 · rules v4

#1PostgreSQL71.4%
#2Supabase71.4%
#3Neon71.4%
#4MySQL70%
#5PlanetScale55.7%
#6AWS50%
#7MongoDB44.3%
#8CockroachDB38.6%
#9DigitalOcean31.4%
#10Azure SQL24.3%

Aug 17, 202670 sampled answers · window 2026-07-20 – 2026-08-17 · rules v4

#1PostgreSQL71.4%
#2Supabase71.4%
#3Neon71.4%
#4MySQL70%
#5PlanetScale55.7%
#6AWS50%
#7MongoDB44.3%
#8CockroachDB38.6%
#9DigitalOcean31.4%
#10Azure SQL24.3%

Aug 16, 202670 sampled answers · window 2026-07-19 – 2026-08-16 · rules v4

#1PostgreSQL71.4%
#2Supabase71.4%
#3Neon71.4%
#4MySQL70%
#5PlanetScale55.7%
#6AWS50%
#7MongoDB44.3%
#8CockroachDB38.6%
#9DigitalOcean31.4%
#10Azure SQL24.3%

Aug 15, 202670 sampled answers · window 2026-07-18 – 2026-08-15 · rules v4

#1PostgreSQL71.4%
#2Supabase71.4%
#3Neon71.4%
#4MySQL70%
#5PlanetScale55.7%
#6AWS50%
#7MongoDB44.3%
#8CockroachDB38.6%
#9DigitalOcean31.4%
#10Azure SQL24.3%

Aug 14, 202670 sampled answers · window 2026-07-17 – 2026-08-14 · rules v4

#1PostgreSQL71.4%
#2Supabase71.4%
#3Neon71.4%
#4MySQL70%
#5PlanetScale55.7%
#6AWS50%
#7MongoDB44.3%
#8CockroachDB38.6%
#9DigitalOcean31.4%
#10Azure SQL24.3%

Read any date directly

Every archived date is machine-readable at /api/index/database-as-a-service/as-of/<YYYY-MM-DD>, which returns the ranking as it stood, with the extraction version and revision it was published under. Dates before the record begins return no_record rather than a recomputation — we do not reconstruct history on demand and present it as what we said. See what the engines actually said.

[ORBATOR]