| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Managed relational databases | Data platform | 45% | 1 of 82 | 23% | 70 | endorsed leader | ▲+7Since September 2026: 35% → 42%, +7 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| DDI and IP address management | Network and edge | 0% | 32 of 115 | 0% | 1 | under 10 labels · led by BlueCat Micetro at 15% |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| Managed databases | 35% | 42% | ▲+7Since September 2026: 35% → 42%, +7 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 1 of 82, unchanged |
| DDI and IPAM | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 32 of 115, unchanged |
Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.
The floor is 11 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 4 | 0 | 1 | 1 | 6 |
| GPT-5.4 mini | 4 | 0 | 0 | 1 | 5 |
| Gemini 3.5 Flash | 0 | 2 | 2 | 1 | 5 |
| Perplexity Sonar | 3 | 0 | 1 | 2 | 6 |
| Grok 4.20 | 2 | 1 | 1 | 2 | 6 |
| Mistral Small | 0 | 0 | 2 | 1 | 3 |
| DeepSeek V4 Flash | 2 | 1 | 1 | 1 | 5 |
| Llama 4 Maverick | 2 | 1 | 0 | 1 | 4 |
| Qwen 3.7 Flash | 2 | 1 | 2 | 0 | 5 |
| Kimi K2 | 4 | 0 | 0 | 2 | 6 |
| GLM 4.7 FlashX | 2 | 2 | 1 | 1 | 6 |
| MiniMax M2.5 | 3 | 0 | 1 | 1 | 5 |
| GPT-6 Luna | 2 | 0 | 1 | 0 | 3 |
| Muse Glimmer 30B | 4 | 0 | 0 | 2 | 6 |
Verbatim evidence the judge attached to positive labels.
“Amazon RDS, for example, supports MySQL, PostgreSQL, MariaDB, SQL Server, Oracle, and Amazon Aurora, and automates provisioning, patching, backups, and failover.” Llama 4 Maverick · Managed databases · comparative prompt · first choice
“Pick AWS RDS/Aurora for broadest engine breadth and ecosystem maturity, and for cloud-native Aurora performance with MySQL/PostgreSQL compatibility.” Muse Glimmer 30B · Managed databases · comparative prompt · first choice
“The top managed relational database services are Amazon RDS, Google Cloud SQL, Azure SQL Database, and Oracle Autonomous Database” Perplexity Sonar · Managed databases · comparative prompt · first choice
“The best managed relational database service for a mid-market B2B company is Amazon Relational Database Service (RDS) or Amazon Aurora” Llama 4 Maverick · Managed databases · direct prompt · first choice
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“Some models explicitly recommend avoiding RDS for production core systems unless absolutely necessary.” Mistral Small · Managed databases · negative prompt · hard negative
“are cautious with AWS RDS SQL Server for point-in-time restore expectations and with any RDS engine for globally distributed strong-consistency writes” Muse Glimmer 30B · Managed databases · negative prompt · soft negative
“It is widely used and legitimate, but multiple sources note that it can carry premium instance pricing, hidden ancillary costs” Perplexity Sonar · Managed databases · negative prompt · soft negative
“Traditional cloud giants (like AWS RDS, Google Cloud SQL, or Azure SQL) are excellent, but they can easily lead to "bill shock"” Gemini 3.5 Flash · Managed databases · budget prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 168 of the 189 answers that named Amazon RDS and are not a share of its labels.
567 of the 626 domain citations in answers naming Amazon RDS came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
| Kind | Pages | Last 90 days | 2025-10 to 2026-09 | Latest | Categories named |
|---|---|---|---|---|---|
| Blog | 27,117 | undated | API gateways, ETL | ||
| Glossary or explainer | 6,521 | undated | ETL, MFA | ||
| Case study | 2,476 | 0 | 2019-03-01 | WAF, Observability | |
| Webinar or virtual event | 2,057 | 16 | 2026-07-01 | Streaming, API gateways | |
| Comparison | 1,521 | 0 | 2025-09-01 | Object storage, ETL | |
| Conference or event | 1,482 | 0 | 2025-11-01 | Vector databases | |
| Report or ebook | 1,090 | 16 | 2026-09-01 | WAF, NoSQL | |
| Podcast or video | 351 | undated | ETL | ||
| Template or tool | 150 | 0 | 2025-05-01 | ||
| News or press | 34 | undated |
As the event pages on aws.amazon.com state them, read September 28, 2026.
Every page aws.amazon.com exposes, subdomains included. Kind is read from the address and title. The last 90 days, the latest date and the twelve months count pages by when they were published, from the site's feeds, a date in the address, or the page's own publication date, read from up to a hundred of its most recently changed pages; a page that says only when it last changed is counted in its kind but not in when, so the recent counts are a floor, and a kind none of whose pages gives a publication date reads undated. Of its titles that name a category, most name ETL (168); 0 name its categories the models place it in. An event counts as online when its address or title says so (webinar, on demand, virtual or online summit); a conference, summit, trade show, expo or roadshow that does not say so is counted as a conference or event, which on a vendor's site is mostly in person. Read September 28, 2026.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Amazon RDS's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Amazon RDS, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Amazon RDS by email, built from the raw record of the edition. It shows:
AI models recommend Amazon RDS first in Managed relational databases this edition. Each badge says so in the buyer's words, names the edition, and links to the standing. The next edition issues a new badge; this one stays true as a record of October 2026.
Badges read on light and dark pages. Alt text carries the claim, the category, the edition and the index, so it stays a citation where the image does not load.