Every category where a model named Azure Event Hubs for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.

Category	Function	Share	Rank	Negative rate	Labels	Quadrant
Streaming platforms	Data platform	2%	10 of 78	19%	27	accepted challenger

Movement

This is the first edition on this tier, so no move can be computed for Azure Event Hubs yet. From the next edition this section shows, per buyer segment, whether its share moved by more than the measured noise floor.

By model

How each model treated Azure Event Hubs across every prompt where it was named for a mid-market B2B company. Twelve models, six prompts per category.

Model	First choice	Alternative	Mention	Negative	Labels
Claude Haiku 4.5	0	1	1	0	2
GPT-5.4 mini	0	1	1	0	2
Gemini 3.5 Flash	0	1	0	0	1
Perplexity Sonar	0	1	0	1	2
Grok 4.1 Fast	0	1	1	1	3
Mistral Small	0	0	1	0	1
DeepSeek V4 Flash	0	2	1	1	4
Llama 4 Maverick	0	0	0	1	1
Qwen 3.7 Flash	1	1	2	0	4
Kimi K2	0	2	1	0	3
GLM 4.7 FlashX	0	0	1	1	2
MiniMax M2.5	0	1	1	0	2

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.

FramingLabels by classFirst choices

Direct6 labels1

Paraphrase11 labelsNone

Comparative19 labelsNone

Budget-constrained6 labels2

Scale-constrained18 labelsNone

Negative18 labelsNone

First choiceAlternativeMentionNegative78 labels in all, every segment counted; 3 of the 3 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

“Start with your cloud provider's native tool (Kinesis/Event Hubs)” Qwen 3.7 Flash · Streaming · direct prompt · first choice

“A high-throughput telemetry ingestion service with Kafka protocol compatibility” Gemini 3.5 Flash · Streaming · comparative prompt · alternative

“Microsoft's option with a free tier available for development and testing.” Claude Haiku 4.5 · Streaming · budget prompt · alternative

“Already on GCP or Azure → Pub/Sub or Event Hubs respectively” DeepSeek V4 Flash · Streaming · comparative prompt · alternative

And against it

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.

“be especially careful with platforms that force a major architectural mismatch, such as using Azure Event Hubs, Google Pub/Sub, Apache Pulsar, or NATS JetStream” Perplexity Sonar · Streaming · negative prompt · soft negative

“Don't get locked into a proprietary API (Kinesis, Azure Event Hubs without Kafka endpoint).” DeepSeek V4 Flash · Streaming · negative prompt · soft negative

“Verdict: CAUTION (Vendor Lock-in & Cost)” GLM 4.7 FlashX · Streaming · negative prompt · soft negative

“it may be limited to Azure environments” Llama 4 Maverick · Streaming · negative prompt · soft negative

Named alongside

The products named in the same answers as Azure Event Hubs, over the 78 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and Azure Event Hubs was named but was not.

ProductSame answerTook the first choice insteadHead to head

Confluent Cloud65 of 7830Not in the top three

Apache Kafka60 of 7824Not in the top three

Google Cloud Pub/Sub60 of 780Not in the top three

Amazon Kinesis Data Streams56 of 781Not in the top three

Redpanda54 of 784Not in the top three

Apache Pulsar46 of 780Not in the top three

Amazon MSK41 of 782Not in the top three

Aiven for Apache Kafka18 of 782Not in the top three

RabbitMQ17 of 780Not in the top three

NATS JetStream12 of 780Not in the top three

A head-to-head page exists where both products are in a category's top three. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named Azure Event Hubs. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, four of the twelve in this edition, so these counts come from 58 of the 78 answers that named Azure Event Hubs and are not a share of its labels.

Domains cited

devopsschool.com35

automq.com28

confluent.io28

guideflow.com27

gartner.com20

risingwave.com20

blobstreaming.org15

gravitee.io14

redpanda.com14

kai-waehner.de13

214 of the 214 domain citations in answers naming Azure Event Hubs came from somebody else's page.

Pages cited

devopsschool.com/blog/top-10-event-streaming-platforms-features-pros-cons-comparison33

guideflow.com/blog/event-streaming-software27

automq.com/blog/top-10-event-streaming-platforms-confluent-msk-redpanda-alternatives21

gartner.com/reviews/market/event-stream-processing20

blobstreaming.org/notes/event-streaming-platforms-202615

gravitee.io/blog/best-event-streaming-solutions14

eltherion.com/blog/event-streaming-architecture-kafka-kinesis-pulsar11

risingwave.com/blog/best-event-stream-processing-platforms-202611

Pages are listed as the models cited them.

Names read as Azure Event Hubs

What the judge wrote, as written, with how often. The vendor table decides that these count as Azure Event Hubs; a claim can dispute any of them.

Event Hubs 1Microsoft Azure Event Hubs 1

Is this your product?

Claim this page

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.

It does not get any change to labels, shares or verdicts, any preview, or any say over which quotes appear. A verification link goes to your work email; an address at azure.cn is approved on the spot, any other address is reviewed by hand.

Your name and company appear on the claimed page, or the company alone if you ask below. A title and a LinkedIn address appear there too if you give them, and are left off if you do not. Your email address is never published.