| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Managed relational databases | Data platform | 12% | 2 of 82 | 21% | 39 | accepted challenger | ▲+3Since September 2026: 11% → 14%, +3 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| AIOps platforms | IT operations and endpoint | 4% | 10 of 93 | 0% | 2 | under 10 labels · led by New Relic at 17% |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| Managed databases | 11% | 14% | ▲+3Since September 2026: 11% → 14%, +3 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 3 → 2 of 82 |
| AIOps | 0% | 2% | newNew since September 2026: not ranked then, 2% now. | New this edition | Rank 10 of 93, 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 | 0 | 0 | 1 | 1 | 2 |
| GPT-5.4 mini | 1 | 2 | 1 | 0 | 4 |
| Gemini 3.5 Flash | 3 | 0 | 0 | 1 | 4 |
| Perplexity Sonar | 1 | 1 | 0 | 0 | 2 |
| Grok 4.20 | 0 | 0 | 0 | 0 | 0 |
| Mistral Small | 1 | 0 | 1 | 1 | 3 |
| DeepSeek V4 Flash | 0 | 0 | 2 | 1 | 3 |
| Llama 4 Maverick | 2 | 1 | 0 | 0 | 3 |
| Qwen 3.7 Flash | 0 | 0 | 2 | 2 | 4 |
| Kimi K2 | 1 | 2 | 0 | 1 | 4 |
| GLM 4.7 FlashX | 2 | 0 | 0 | 0 | 2 |
| MiniMax M2.5 | 1 | 1 | 1 | 0 | 3 |
| GPT-6 Luna | 0 | 1 | 1 | 1 | 3 |
| Muse Glimmer 30B | 2 | 1 | 1 | 0 | 4 |
Verbatim evidence the judge attached to positive labels.
“a recommended hosted SQL database could be PostgreSQL with a cloud-managed service like AWS Aurora, as it balances capability, cost, and operational simplicity” Llama 4 Maverick · Managed databases · paraphrase 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
“is Amazon Relational Database Service (RDS) or Amazon Aurora, as they are fully managed relational database services” Llama 4 Maverick · Managed databases · direct prompt · first choice
“Go with Amazon Aurora. Its tight integration with AWS... make it the top performance-tier option on AWS.” Gemini 3.5 Flash · Managed databases · comparative 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.
“Experts advise caution or avoidance for production environments where stable performance is critical.” Mistral Small · Managed databases · negative prompt · hard negative
“Aurora uses internal optimizations and sometimes proprietary features ... that can make migrating back to standard MySQL/Postgres difficult” Qwen 3.7 Flash · Managed databases · negative prompt · soft negative
“While Aurora is popular, be cautious about: Complex pricing - I/O charges can escalate unpredictably” Kimi K2 · Managed databases · negative prompt · soft negative
“not Aurora unless you have a demonstrated need for its different performance or scaling characteristics” GPT-6 Luna · Managed databases · paraphrase 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 102 of the 107 answers that named Amazon Aurora and are not a share of its labels.
284 of the 341 domain citations in answers naming Amazon Aurora 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.
What Amazon Aurora's own pages state, read September 28, 2026: aws.amazon.com, aws.amazon.com/pricing, aws.amazon.com/security, aws.amazon.com/products, aws.amazon.com/s3/customers. A claimed page can correct any of them.
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 Aurora'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 Aurora, 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 Aurora by email, built from the raw record of the edition. It shows:
Amazon Aurora is among the products AI models recommend 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.