| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Data virtualization | Data platform | 0% | 73 of 99 | 43% | 7 | under 10 labels · led by Denodo at 28% |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 1 | 0 | 0 | 1 |
| GPT-5.4 mini | 0 | 0 | 0 | 0 | 0 |
| Gemini 3.5 Flash | 0 | 0 | 0 | 0 | 0 |
| Perplexity Sonar | 0 | 0 | 1 | 0 | 1 |
| Grok 4.1 Fast | 0 | 1 | 0 | 1 | 2 |
| Mistral Small | 0 | 0 | 0 | 0 | 0 |
| DeepSeek V4 Flash | 0 | 0 | 0 | 0 | 0 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 0 | 0 | 0 | 0 |
| Kimi K2 | 0 | 0 | 0 | 1 | 1 |
| GLM 4.7 FlashX | 0 | 0 | 1 | 0 | 1 |
| MiniMax M2.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 0 | 0 | 1 | 1 |
Verbatim evidence the judge attached to positive labels.
“outshines others with its high-speed performance... However, it is mostly focused on SAP-related workflows” Claude Haiku 4.5 · Data virtualization · comparative prompt · alternative
“In-memory speed, ERP/operational data federation. Real-time analytics.” Grok 4.1 Fast · Data virtualization · comparative 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.
“Users note a steep learning curve for SAP HANA Cloud, which may require specialized training to navigate effectively.” Muse Glimmer 30B · Data virtualization · negative prompt · soft negative
“Steep learning curve requiring specialized training - Prohibitive cost for smaller organizations” Kimi K2 · Data virtualization · negative prompt · soft negative
“Lower ratings often due to complexity in non-virtualization features; avoid if not already in ecosystem.” Grok 4.1 Fast · Data virtualization · 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 21 of the 22 answers that named SAP HANA and are not a share of its labels.
101 of the 101 domain citations in answers naming SAP HANA 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 SAP HANA's own pages state, read October 5, 2026: sap.com/registration/free-migration-sap-hana-cloud.html, sap.com/products/technology-platform/hana-cloud-sap-hana-application-migration.html, sap.com/products/technology-platform/build-code-generation-of-sap-hana-applications.html, sap.com/registration/trials/sap-hana-cloud/tye.html, sap.com/products/data-cloud/hana/what-is-sap-hana.html. 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 SAP HANA'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 SAP HANA, 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 SAP HANA by email, built from the raw record of the edition. It shows: