| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Streaming platforms | Data platform | 2% | 10 of 98 | 24% | 33 | accepted challenger | =heldSince September 2026: 2% → 2%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Telemetry pipelines | IT operations and endpoint | 0% | 82 of 124 | 0% | 1 | under 10 labels · led by OpenTelemetry Collector at 37% |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| Streaming | 2% | 2% | =heldSince September 2026: 2% → 2%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 10 of 98, unchanged |
| Telemetry pipelines | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 82 of 124, 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 | 1 | 0 | 0 | 1 |
| GPT-5.4 mini | 1 | 0 | 1 | 0 | 2 |
| Gemini 3.5 Flash | 0 | 0 | 1 | 1 | 2 |
| Perplexity Sonar | 0 | 0 | 1 | 1 | 2 |
| Grok 4.20 | 0 | 1 | 1 | 0 | 2 |
| Mistral Small | 0 | 0 | 2 | 0 | 2 |
| DeepSeek V4 Flash | 0 | 1 | 1 | 0 | 2 |
| Llama 4 Maverick | 0 | 0 | 1 | 0 | 1 |
| Qwen 3.7 Flash | 0 | 1 | 2 | 2 | 5 |
| Kimi K2 | 0 | 1 | 1 | 0 | 2 |
| GLM 4.7 FlashX | 0 | 1 | 1 | 1 | 3 |
| MiniMax M2.5 | 0 | 1 | 2 | 1 | 4 |
| GPT-6 Luna | 0 | 1 | 1 | 1 | 3 |
| Muse Glimmer 30B | 0 | 2 | 0 | 1 | 3 |
Verbatim evidence the judge attached to positive labels.
“For most mid-market B2B companies, I'd choose: 1. Azure Event Hubs if you're already in Azure” GPT-5.4 mini · Streaming · direct prompt · first choice
“Cloud-native options (MSK, Event Hubs, Kinesis) if you're already committed to a cloud provider” Kimi K2 · Streaming · scale prompt · alternative
“Azure Event Hubs if you prefer a fully managed serverless posture and are already in that cloud” Muse Glimmer 30B · Streaming · direct prompt · alternative
“Microsoft's managed event ingestion service, designed to ingest millions of events per second” Muse Glimmer 30B · Streaming · 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.
“Services like Amazon Kinesis, Azure Event Hubs, and Google Pub/Sub are convenient "walled gardens."” Qwen 3.7 Flash · Streaming · negative prompt · hard negative
“AWS Kinesis, Azure Event Hubs (Vendor lock-in)” Gemini 3.5 Flash · Streaming · negative prompt · hard negative
“Kafka compatibility varies by tier; Microsoft says full compatibility requires Premium or Dedicated, and some features are limited or in preview.” GPT-6 Luna · Streaming · negative prompt · soft negative
“cautious if you want portability or low operational lock-in, since they are cloud-specific managed services” Perplexity Sonar · Streaming · 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 83 of the 99 answers that named Azure Event Hubs and are not a share of its labels.
284 of the 284 domain citations in answers naming Azure Event Hubs 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.
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 Azure Event Hubs'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 Azure Event Hubs, 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 Azure Event Hubs by email, built from the raw record of the edition. It shows: