| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Data catalogs and governance | Data platform | 0% | 12 of 83 | 9% | 11 | accepted challenger |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 1 | 0 | 1 |
| GPT-5.4 mini | 0 | 0 | 0 | 0 | 0 |
| Gemini 3.5 Flash | 0 | 0 | 1 | 0 | 1 |
| Perplexity Sonar | 0 | 0 | 0 | 0 | 0 |
| Grok 4.1 Fast | 0 | 0 | 0 | 0 | 0 |
| Mistral Small | 0 | 1 | 1 | 0 | 2 |
| DeepSeek V4 Flash | 0 | 0 | 2 | 0 | 2 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 0 | 0 | 1 | 1 |
| Kimi K2 | 0 | 1 | 0 | 0 | 1 |
| GLM 4.7 FlashX | 0 | 1 | 1 | 0 | 2 |
| MiniMax M2.5 | 0 | 0 | 1 | 0 | 1 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 0 | 0 | 0 | 0 |
Verbatim evidence the judge attached to positive labels.
“If you need a fully managed solution and can budget for usage, consider Microsoft Purview or AWS Glue.” Mistral Small · Data catalogs · budget prompt · alternative
“Serverless, tight AWS integration, low operational overhead” Kimi K2 · Data catalogs · comparative prompt · alternative
“AWS Glue Data Catalog (Best for AWS Users)” GLM 4.7 FlashX · Data catalogs · budget prompt · alternative
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.
“Who to be cautious with: AWS Glue/Data Zone, Azure Purview, Google Cloud Dataplex.” Qwen 3.7 Flash · Data catalogs · negative 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 28 of the 31 answers that named AWS Glue Data Catalog and are not a share of its labels.
120 of the 120 domain citations in answers naming AWS Glue Data Catalog came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read October 5, 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.
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 AWS Glue Data Catalog's own pages state, read October 5, 2026: aws.amazon.com/blogs/database/create-an-aws-glue-data-catalog-with-aws-dms, aws.amazon.com/blogs/big-data/use-aws-glue-data-catalog-views-to-analyze-data, aws.amazon.com/blogs/big-data/introducing-aws-glue-data-catalog-usage-metrics-for-api-usage, aws.amazon.com/blogs/big-data/cross-account-aws-glue-data-catalog-access-with-amazon-athena, aws.amazon.com/blogs/big-data/query-cross-account-aws-glue-data-catalogs-using-amazon-athena. 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 AWS Glue Data Catalog'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 AWS Glue Data Catalog, 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 AWS Glue Data Catalog by email, built from the raw record of the edition. It shows: