Markets · bedrock market · provisional

Streaming (Apache Kafka protocol)

Shape market (the kafka wire protocol re-served; convergence by imitation, proxies mediate). The Kin Score Market layer reads each provider in its market: who it integrates with, how deep those integrations go, and where the market publishes its own structure. Methodology.

24providers measured

17 (70.8%)declare their own

3 (12.5%)covered by others only

4 (16.7%)undeclared

15declare compatibility (report only, not weighted)

0in-market workflows shown

Provisional. Provisional and unweighted: the Market layer is not part of the composite or agent readiness. Leader lists are read within a position, never as one ranking. A provider that declares nothing we can read is shown as undeclared, with no number: we never infer integrations.

Where this market publishes its structure

Providers' own Kafka compatibility pages and protocol/feature tables (fetched, saved under evidence/compatibility/) machine-readable
Providers' own contracts naming the Kafka protocol (info/tags/path descriptions) machine-readable
AWS, Azure and Google Cloud marketplace listings (distribution, reported beside) machine-readable
JS-rendered pages (Upstash Kafka docs, VAST Event Broker, Bufstream product page) not machine-readable: client-rendered or redirected; no text without a browser
Conformance test running the Apache Kafka client compatibility suite against each endpoint not machine-readable: no register exists; not built

Own = declares at least one integration itself; covered = visible only because an aggregator, standards body, regulator or partner contract names it; distribution-only = listed only on cloud marketplaces it sells through, a channel reported beside, never counted as its own declared integrations; undeclared = nothing we can read, so no number; declares_compatibility = providers with a `compatible` shape vote, report only (kin, 2026-10-13): never counted as own, never in depth or position.

Taxonomy how this market maps onto apis.io

Derived 2026-10-23 from the 24 providers in this market we could resolve in the catalog. The percentage is the share of those providers carrying each one; it describes the market, not the tag or industry. Tag groups have no page of their own yet, so they are listed unlinked.

Tags	Real-Time 33%, Apache Kafka 33%, Open Source 29%, Streaming 29%, Event Streaming 29%, Messaging 25%, Database 25%, Kafka 25%
Tag groups	Event Streaming 62%, Real-Time 33%, Database 33%, Media 29%, Messaging 25%, Kubernetes 25%, Event-Driven 25%, Infrastructure 21%
Industries	Developer Tools & DevOps 54%, Data & Analytics 50%, Telecommunications & Connectivity 29%
Areas	Database 25%, Serverless 12%, Gateway 12%
Capabilities	Information Technology Management 50%, Cybersecurity Management 33%

share of resolved cohort carrying it; tags >=0.20 & >=3 members (max 12, junk dropped), tag_groups >=0.20 (cooccurrence, non-cross-cutting; max 8), industries >=0.20 (max 6), areas >=0.10 (max 6; areas are keyword-matched and sparse), capabilities L1 >=0.20 (max 8); derive-market-taxonomy.py

Leaders by position (provisional)

Provisional: grouped by position, depth compared within a position only. Distribution (cloud marketplaces) and iPaaS bridges are counted beside position, never inside it. Unknown-builder listings are left out of position shares and counted here.

gravity 1 · other companies invest to build on it

Provider	Depth	Integrations	In / out	Unknown builder	Distribution	iPaaS bridge	Mix
Kong	56.2	39	11 / 28	0	0	0	partner-built 41%, standard 37%, builds-on-platform 22%

builds-on 7 · publishes apps on other platforms' stores

Provider	Depth	Integrations	In / out	Distribution	iPaaS bridge	Mix
Confluent	53.7	16	0 / 16	4	1	ipaas-bridge 6%, standard 31%, builds-on-platform 38%, distribution 25%
Redpanda	46.6	9	0 / 9	2	0	standard 11%, builds-on-platform 67%, distribution 22%
Conduktor	46.0	4	0 / 4	1	0	builds-on-platform 75%, distribution 25%
VAST Data	45.5	8	0 / 8	3	0	standard 25%, builds-on-platform 38%, distribution 38%
Upstash	45.0	10	0 / 10	0	1	ipaas-bridge 10%, standard 10%, covered 20%, builds-on-platform 60%
Aiven	44.8	10	0 / 10	2	0	standard 20%, covered 10%, builds-on-platform 50%, distribution 20%
Aklivity	17.2 thin	1	0 / 1	0	0	builds-on-platform 100%

covered 4 · reached mainly through aggregators

Provider	Depth	Integrations	In / out	iPaaS bridge	Mix
Apache Kafka	56.0	3	0 / 3	0	contract 33%, covered 67%
AWS Kinesis	44.4	5	0 / 5	1	ipaas-bridge 20%, standard 20%, covered 60%
Oracle Database	34.5 thin	2	0 / 2	0	standard 50%, covered 50%
Google Cloud Pub/Sub	19.4 thin	1	0 / 1	0	covered 100%

standard 5 · listed by a voluntary standard's own directory

Provider	Depth	Integrations	In / out	Distribution	iPaaS bridge	Mix
Oracle	72.2	41	0 / 41	3	4	ipaas-bridge 10%, contract 7%, standard 45%, covered 5%, builds-on-platform 26%, distribution 7%
IBM	70.6	60	0 / 60	6	0	contract 6%, standard 49%, builds-on-platform 34%, distribution 11%
NATS	59.4	5	0 / 5	0	0	standard 60%, builds-on-platform 40%
CoreWeave	53.3	9	0 / 9	0	0	standard 67%, covered 11%, builds-on-platform 22%
Gravitee	37.9	18	0 / 18	1	0	standard 57%, builds-on-platform 29%, distribution 14%

mixed 3 · no single mode dominates

Provider	Depth	Integrations	In / out	Distribution	iPaaS bridge	Mix
RabbitMQ	42.5	5	0 / 5	2	0	standard 20%, covered 20%, builds-on-platform 20%, distribution 40%
Heroku	40.8	11	0 / 11	2	2	ipaas-bridge 18%, standard 18%, covered 27%, builds-on-platform 18%, distribution 18%
Azure Event Hubs	37.6	3	0 / 3	0	1	ipaas-bridge 33%, standard 33%, covered 33%

undeclared 4 · declares nothing we can read: no number

Provider	Depth	Integrations	In / out	Unknown builder	Distribution	iPaaS bridge
Amazon MSK	undeclared	-	-	-	-	-
Apache Pulsar	undeclared	-	-	-	-	-
Streambased	undeclared	-	-	-	-	-
WarpStream	undeclared	-	-	-	-	-

Shape adoption report only — not weighted

Report only, not weighted (Kin, 2026-10-13): `compatible` edges are shape votes (the provider re-serves the anchor's contract). They are shown here and as 'declares compatibility' on a provider, and are excluded from depth, position and the own/covered declaration until they hold across four weekly snapshots.

Pattern: imitation, with mediation beside. Shape gravity (counted by company, one edge per provider, the best evidence kept): 9. Convergence in the cohort: 10 of 14 (71.4%) — cohort members (minus the anchor's family, mediators and rival shapes) with at least one compatible edge to the shape, read from evidence.

kafka-protocol anchor Apache Kafka · 9 adopters, 10 declared by the provider

By degree: full 5, declared-subset 4, declared-unqualified 1. By evidence: own-docs 10.

Provider	Degree	Evidence	Supported share
Aiven	full	own-docs	-
Amazon MSK	full	own-docs	-
Confluent	full	own-docs	-
Heroku	full	own-docs	-
IBM	full	own-docs	-
Oracle	declared-subset	own-docs	0.073
Oracle Database	declared-subset	own-docs	0.024
Redpanda	declared-subset	own-docs	0.171
WarpStream	declared-subset	own-docs	0.537
Azure Event Hubs	declared-unqualified	own-docs	-

Mediation (in front of the shape, never adopters): Kong, Gravitee, Conduktor, Aklivity
Rival shapes (own contracts, not re-served): Apache Pulsar, RabbitMQ, NATS, AWS Kinesis, Google Cloud Pub/Sub
In the cohort, declaring nothing we can read: CoreWeave, VAST Data, Upstash, Streambased
Evidence ladder: conformance-register > own-docs > own-contract > own-blog > ae-structural. Degrees: full | declared-subset | declared-unqualified | interoperable-subset | same-vocabulary-own-path.

Snapshot timeline 2 weekly snapshot(s); nothing is weighted until it holds across four

Date	Providers	Declared by the provider	Per shape (gravity / declared)
2026-10-15	10	10	kafka-protocol 10 / 10
2026-10-17	10	10	kafka-protocol 10 / 10

Generated 2026-10-24 from API Evangelist's own files; nothing on this page is a model's judgement. Provisional and unweighted; not part of the Kin Score composite or agent readiness. Read the Market layer methodology. Disagree with an edge? Every edge cites its evidence and can be corrected through the normal correction path.