SStatWharf
Menu

Best Streaming Data Platforms (2026): Top 7 Compared

Updated October 2026By StatWharf Editorial7 vendorsMethodology

Streaming data platforms store ordered streams of events and deliver them to many consumers in near real time. The seven products below fall into three groups. Confluent, Redpanda, Aiven and StreamNative sell managed services built on or compatible with the Apache Kafka protocol, and StreamNative also runs Apache Pulsar. Amazon Kinesis Data Streams, Azure Event Hubs and Google Cloud Pub/Sub are native services of the three large clouds. Prices are usage meters, not seats: capacity per hour, data per GB or TiB, and storage per GB-month. Pricing below was read from each vendor's own pricing page or price list in October 2026.

Order is not a ranking. How entries are ordered.

On this page
  1. Comparison table
  2. Vendor details
  3. Confluent
  4. Redpanda
  5. Amazon Kinesis Data Streams
  6. Azure Event Hubs
  7. Google Cloud Pub/Sub
  8. Aiven for Apache Kafka
  9. StreamNative
  10. How to choose
  11. Frequently asked questions
  12. Suggest a vendor

Compare at a glance

Select a vendor for details and sources. Scroll the table horizontally on smaller screens.

Streaming Data Platforms: vendor fit and recorded pricing
VendorConsider forPricing notesStandout
ConfluententerpriseEnterprises standardising on Kafka with managed connectors, Flink and governanceBasic from $0 (first eCKU free, then $0.14/eCKU-hour); Standard $0.75/eCKU-hour; plus $0.035-$0.05/GB ingress/egress and $0.08/GB-month storage Checked Oct 2026Four serverless cluster types, from Basic to Freight, on the Kora engine
RedpandaspecialistKafka API teams wanting a simpler engine, BYOC or Iceberg outputServerless metered on uptime, ingress, egress, partitions and storage; no unit rates published, estimator only; BYOC on annual commitment Checked Oct 2026Kafka-compatible engine with Redpanda Connect and an Agentic Data Plane
Amazon Kinesis Data StreamsenterpriseAWS-native teams feeding Lambda, Firehose and Managed FlinkUS East: on-demand $0.040/stream-hour + $0.08/GB in, $0.04/GB out; provisioned $0.015/shard-hour + $0.014 per million PUT units Checked Oct 2026Three capacity modes, from on-demand to shard-based provisioning
Azure Event HubsenterpriseAzure shops needing Kafka-compatible ingestion without running Kafka clustersEast US: Standard $0.03/throughput unit-hour + $0.028 per million ingress events; Premium $1.027/processing unit-hour; Dedicated $6.849/capacity unit-hour Checked Oct 2026Kafka, AMQP 1.0 and HTTPS endpoints on one managed service
Google Cloud Pub/SubenterpriseGoogle Cloud teams needing serverless messaging with direct BigQuery deliveryFirst 10 GiB/month free, then $40 per TiB throughput; BigQuery and Cloud Storage subscriptions $50 per TiB; storage $0.27/GiB-month; 1 KB minimum per request Checked Oct 2026Per-message delivery without partitions, plus BigQuery subscriptions
Aiven for Apache Kafkamid-marketTeams wanting open-source Kafka managed on several clouds with published plan pricesFree plan $0; Developer $35/month ($0.04/hour); Professional from $180/month; billed hourly, invoiced monthly; networking metered Checked Oct 2026Diskless topics on object storage alongside low-latency topics
StreamNativespecialistTeams running Apache Pulsar, or Kafka workloads that should land in lakehouse tablesServerless from $73/month (ETU meter); BYOC from $365/month (ETU); Dedicated from $505/month (CU/SU); billed monthly on usage Checked Oct 2026Pulsar and Kafka protocols over Ursa lakehouse-native storage

These comparisons draw on public product information, not hands-on testing of every tool. Source records identify available references and checks; missing evidence is marked. Buyer fit is an editorial assessment, not a measured performance score. How to use this research.

Streaming data platforms move events from the systems that create them to the systems that act on them, within milliseconds or seconds rather than in nightly batches. They keep an ordered, replayable log of events, such as orders, payments, sensor readings or database changes, so several applications can read the same stream at their own pace. Typical uses are real-time analytics, fraud signals, IoT telemetry, log pipelines, microservice communication and, increasingly, feeding AI agents with current data.

The seven platforms compared below split three ways. Confluent, Redpanda, Aiven and StreamNative sell managed services built on or compatible with the Apache Kafka protocol, and StreamNative also runs Apache Pulsar. Amazon Kinesis Data Streams, Azure Event Hubs and Google Cloud Pub/Sub are native services of the three largest clouds. Pricing in this category is metered, so the table quotes the meter units and rates published on each official pricing page or price list in October 2026. Entries with dated source checks appear first, which records research readiness, not product quality.

Related pages cover CDC tools and data integration platforms.

Vendor details and trade-offs

Confluent

enterpriseconfluent.io ↗
Consider forOrganisations that run Apache Kafka as a shared platform across teams and want connectors, Flink stream processing and governance from one vendor, because Confluent documents all of these as managed services on AWS, Azure and Google Cloud
Pricing notesUsage-based. Basic: first eCKU free, then $0.14 per eCKU-hour, $0.05 per GB ingress/egress. Standard: $0.75 per eCKU-hour, $0.035-$0.050 per GB. Enterprise: $1.75-$2.25 per eCKU-hour, $0.020-$0.050 per GB. Freight: $2.25 per eCKU-hour with a 2-eCKU minimum, $0.014-$0.030 per GB, $0.03 per GB-month storage. Storage on other types $0.08 per GB-month. Dedicated clusters are quoted by sales. Connect, Flink (CFU-minutes), Tableflow and Stream Governance are metered separately (checked Oct 2026)
Feature to evaluateServerless Kafka clusters on the Kora engine, with managed connectors, Apache Flink, Tableflow output to Iceberg and Delta Lake tables, and a separate WarpStream option for a customer's own cloud account

Confluent sells Confluent Cloud, a managed service, and Confluent Platform, a self-managed distribution. IBM completed its acquisition of Confluent on 17 March 2026, according to IBM's quarterly filings, and positions it as a real-time data layer alongside watsonx.data and IBM MQ. The Confluent Cloud product page does not mention IBM.

Confluent Cloud runs on Kora, which Confluent calls its cloud-native Kafka engine. Clusters scale automatically, and the vendor claims this halves infrastructure spend and lowers total cost of ownership by up to 60% compared with self-managed Kafka. These are vendor figures without a stated method. The service runs on AWS, Microsoft Azure and Google Cloud across more than 100 regions, with a 99.99% uptime SLA for multi-zone clusters.

The pricing page lists four serverless cluster types. Basic starts at $0 and supports up to 5 TB of storage. Standard and Enterprise add higher partition limits and an SLA of up to 99.99%. Freight trades latency of up to one or two seconds for lower per-GB networking and storage rates, and suits high-volume logging or telemetry. Dedicated clusters with pre-provisioned capacity are sold through sales.

Around the Kafka core, Confluent offers managed connectors, Confluent Cloud for Apache Flink for joins, filters and AI model inference on streams, Tableflow for turning topics into Apache Iceberg or Delta Lake tables, and Stream Governance for schemas and lineage. WarpStream, a Kafka-compatible service that runs inside the customer's own cloud account, is listed as a separate deployment option. New developers receive $400 in credits during their first 30 days, according to the product page.

Potential strengths

  • Broadest managed ecosystem on this page: the product page cites 80+ fully managed connectors, serverless Flink and a governance suite with stream lineage
  • Four published cluster types let small workloads start at $0 on Basic and large, latency-tolerant workloads use the lower per-GB rates of Freight

Trade-offs

  • Total cost combines several meters (eCKU-hours, per-GB networking, storage, connector tasks, Flink CFUs), so a forecast needs the vendor calculator
  • Dedicated cluster pricing is not published, and IBM's ownership since March 2026 means product and contract direction may change
Sources and status

Redpanda

specialistredpanda.com ↗
Consider forEngineering teams that use Kafka clients but want a Kafka API-compatible engine they can run as serverless, in their own cloud account or self-managed, because Redpanda documents all three deployment models with the same API
Pricing notesUsage-based without published unit rates. Serverless is listed from $0 with pay-as-you-go or annual commit billing, metered on uptime, ingress, egress, partitions and storage. Dedicated is metered on uptime, ingress, egress and storage (GB-hours). BYOC is billed on an annual commitment and metered on compute (RPUs, 1 RPU = 2 vCPU and 8 GB memory), ingress, Iceberg ingress, egress and storage. Rates are shown only in the price estimator. Enterprise Edition offers a 30-day trial (checked Oct 2026)
Feature to evaluateOne Kafka API-compatible engine across Serverless, Dedicated, BYOC and self-managed Enterprise Edition, with Redpanda Connect for integration and Iceberg ingestion billed as its own meter

Redpanda describes its product in two lines: the Redpanda Data Platform for streaming, integration and analytics, and an Agentic Data Plane that governs how AI agents access data, call tools and use models. For streaming buyers the relevant part is the Data Platform, which the vendor describes as Kafka API-compatible streaming, Redpanda Connect for integration across hundreds of sources and sinks, and Redpanda SQL for real-time analytics. Redpanda acquired Oxla to add the SQL engine.

The pricing page lists three options. Serverless is listed from $0 with a 30-day free trial and no credit card, and bills pay-as-you-go or on an annual commit. Bring Your Own Cloud runs clusters in the customer's cloud account and is sold on annual commitment. Enterprise Edition is the self-managed product with a 30-day trial. Redpanda's billing documentation also describes Dedicated clusters with uptime rates that vary by region and tier.

Serverless offers a Kafka API endpoint, a 99.9% uptime SLA, AWS PrivateLink and up to 100 MB per second of average ingress per cluster. It is generally available in seven AWS regions, including us-east-1, eu-central-1 and ap-south-1, and in beta on Google Cloud in us-central1. Usage-based pricing is driven by ingress, egress, storage and partitions, with discounted rates through sales.

The BYOC meter list includes a separate charge for ingress to Iceberg topics, which write stream data to Apache Iceberg tables. Named customers on the homepage include Activision, Akamai, Cisco, NYSE, Moody's, Texas Instruments and Vodafone. The vendor also cites a G2 Leader designation in G2's Fall 2026 reports.

Potential strengths

  • Existing Kafka client libraries work against the Serverless Kafka API, so migration does not require rewriting producers or consumers
  • BYOC keeps data in the customer's cloud account while Redpanda operates the cluster, which suits teams with data residency rules

Trade-offs

  • No per-GB or per-hour rates are published on the pricing page or billing documentation, so cost can only be estimated with the vendor's tool
  • Serverless is generally available in seven AWS regions, with Google Cloud in beta in one region, which limits regional choice
Sources and status

Amazon Kinesis Data Streams

enterpriseaws.amazon.com ↗
Consider forTeams building on AWS that want a managed stream feeding Lambda, Amazon Data Firehose and Amazon Managed Service for Apache Flink, because AWS documents these as native consumers of Kinesis Data Streams
Pricing notesUsage-based, US East (N. Virginia) rates from the AWS pricing page examples. On-demand Standard: $0.040 per stream-hour, $0.08 per GB ingested, $0.040 per GB retrieved. On-demand Advantage: no stream-hour charge, $0.032 per GB ingested, $0.016 per GB retrieved, with a 25 MB/s ingest and retrieval account minimum. Provisioned: $0.015 per shard-hour, $0.014 per million 25 KB PUT payload units, extended retention $0.020 per shard-hour, enhanced fan-out $0.015 per consumer-shard-hour and $0.013 per GB (checked Oct 2026)
Feature to evaluateRetention from the 24-hour default up to 365 days, enhanced fan-out with a dedicated 2 MB/s read pipe per consumer per shard, and records up to 10 MiB

Amazon Kinesis Data Streams is the AWS managed service for capturing and storing data streams. Data is available to consumer applications within seconds of being written, according to AWS, and consumers using SubscribeToShard typically receive data within 70 milliseconds.

AWS offers three capacity modes. On-demand Standard, the default, manages capacity automatically: a new stream starts at 4 MB per second and 4,000 records per second for writes and scales by default to 200 MB per second, absorbing up to double its peak write rate of the previous 30 days. On-demand Advantage removes the per-stream hourly charge and lowers per-GB rates for accounts with at least 25 MB per second of ingest and retrieval, and supports warm throughput to pre-scale for expected spikes. Provisioned mode lets teams set a shard count, with each shard providing 1 MB per second and 1,000 records per second for writes and 2 MB per second for reads.

Retention defaults to 24 hours, extends to seven days and reaches 365 days with long-term retention. Enhanced fan-out gives each registered consumer its own 2 MB per second read pipe per shard, so several applications can read the same stream without competing. On-demand streams support up to 20 enhanced fan-out consumers.

The service's value is its position inside AWS. Lambda, Amazon Managed Service for Apache Flink and AWS Glue Streaming process data from streams, and Amazon Data Firehose delivers it to S3, OpenSearch Service, Redshift and HTTP endpoints. AWS also lists newer options for streaming into Apache Iceberg tables on S3 Tables. Kinesis does not speak the Kafka protocol; AWS's FAQ directs existing Kafka users to Amazon MSK.

Potential strengths

  • Native triggers and delivery into Lambda, Firehose, Managed Flink, Glue and S3 reduce the glue code needed on AWS
  • On-demand mode removes shard planning: new streams start at 4 MB/s of writes and scale by default to 200 MB/s

Trade-offs

  • The API is not Kafka-compatible; AWS directs Kafka users to Amazon MSK, so Kafka clients and connectors do not apply
  • Pricing has many meters (stream-hours, shard-hours, PUT units, retention, fan-out), and on-demand retention rates were not shown in the page's examples
Sources and status

Azure Event Hubs

enterpriseazure.microsoft.com ↗
Consider forOrganisations on Microsoft Azure that need high-volume event ingestion from Kafka clients, IoT devices or applications, because Microsoft documents Kafka protocol support without code changes and native links to Stream Analytics, Functions and Data Explorer
Pricing notesUsage-based, East US retail rates from the Azure Retail Prices API. Basic: $0.015 per throughput unit-hour plus $0.028 per million ingress events. Standard: $0.03 per throughput unit-hour plus $0.028 per million ingress events; Capture $0.10 per throughput unit-hour. Premium: $1.027 per processing unit-hour, ingress and Capture included, extended retention $0.10 per GB-month beyond 1 TB per PU. Dedicated: $6.849 per capacity unit-hour, billed in one-hour increments with a four-hour minimum. Geo-replication from $0.09 per GB (checked Oct 2026)
Feature to evaluateNative Apache Kafka, AMQP 1.0 and HTTPS endpoints, with Capture writing the same stream to Blob Storage or Data Lake Storage and a built-in Schema Registry

Azure Event Hubs is Microsoft's fully managed event streaming service. Microsoft describes it as able to ingest millions of events per second with low latency, and as a native Azure service with built-in Apache Kafka compatibility, so existing Kafka workloads can run without code changes or cluster management. The same service accepts AMQP 1.0 and HTTPS, and client libraries cover .NET, Java, Python, JavaScript and Go.

Data is organised into namespaces, event hubs (the equivalent of Kafka topics) and partitions, with consumer groups giving each application its own read position. Retention runs from one day on Basic to seven days on Standard and 90 days on Premium and Dedicated. Capture writes the stream to Azure Blob Storage or Data Lake Storage for long-term storage or batch analytics, and Azure Schema Registry manages Avro and JSON schemas for Kafka applications.

Four tiers set the cost model. Basic and Standard bill per throughput unit, each providing 1 MB per second of ingress and 2 MB per second of egress, plus a charge per million ingress events; auto-inflate can add throughput units as load grows. Premium bills per processing unit with ingress and Capture included and 1 TB of storage per unit. Dedicated provides single-tenant capacity units with 10 TB of storage each and supports events up to 20 MB in preview.

Event Hubs connects to Azure Stream Analytics, including a no-code editor, and to Azure Data Explorer, Azure Functions, Apache Spark and Apache Flink. Security options include Microsoft Entra ID, Private Link and customer-managed keys. Premium and Dedicated add zone redundancy and geo-replication. A local emulator supports development without a cloud connection.

Potential strengths

  • Kafka producers and consumers can point at Event Hubs without code changes, and Kafka is available from the Standard tier upward
  • Four tiers span a $0.015 per hour Basic throughput unit to dedicated single-tenant clusters, with 99.99% SLA and availability zones on Premium and Dedicated

Trade-offs

  • Retention is capped at 1 day on Basic, 7 days on Standard and 90 days on Premium and Dedicated, shorter than Kinesis long-term retention
  • Basic has no Kafka endpoint, Capture or Schema Registry, so most production Kafka workloads start at Standard or Premium
Sources and status

Google Cloud Pub/Sub

enterprisecloud.google.com ↗
Consider forTeams on Google Cloud that want a serverless, partition-free messaging and streaming service feeding BigQuery, Cloud Storage and Dataflow, because Google documents export subscriptions that write directly to both stores
Pricing notesUsage-based, all regions. Throughput (Message Delivery Basic): first 10 GiB per billing account per month free, then $40 per TiB. BigQuery and Cloud Storage subscriptions: $50 per TiB, no free tier. Import topics: $50 per TiB from Kinesis Data Streams, $80 per TiB from Cloud Storage, Azure Event Hubs, Amazon MSK or Confluent Cloud. Message storage: $0.27 per GiB-month. Single message transforms $40 per TiB, AI inference transforms $60 per TiB. A minimum of 1 KB is billed per request; data transfer charged separately (checked Oct 2026)
Feature to evaluatePer-message leasing instead of partitions, export subscriptions straight to BigQuery and Cloud Storage, and import topics that pull from Kinesis, Event Hubs, MSK and Confluent Cloud

Google Cloud Pub/Sub is an asynchronous, scalable messaging service that decouples services producing messages from services processing them. Google states typical latencies on the order of 100 milliseconds. Unlike the partition-based systems on this page, Pub/Sub leases individual messages to subscriber clients and tracks whether each one is processed, so parallelism is not limited by a partition count. Google describes it as combining the horizontal scale of Kafka and Pulsar with middleware features such as dead-letter queues and filtering.

Subscribers can pull messages or receive them by push as HTTP POST requests to webhooks. Export subscriptions write directly to BigQuery or Cloud Storage without a separate pipeline, and are billed at $50 per TiB, with no additional BigQuery ingestion charge. Import topics bring data in from Amazon Kinesis Data Streams, Cloud Storage, Azure Event Hubs, Amazon MSK or Confluent Cloud, which suits teams consolidating streams from other clouds onto Google Cloud.

Single message transforms can reshape or enrich messages in flight, including an AI inference transform that adds a model response to each message; Gemini model charges apply on top. Dataflow, Apache Spark, Cloud Functions, Workflows and Managed Airflow are listed as processing and orchestration options.

Pricing is usage-based on bytes published, delivered and stored, at the same rates in every Google Cloud region. The pricing page's own example shows a 10 MiB per second, one-subscription workload at about $2,000 per month on Pub/Sub. Pub/Sub Lite, which billed on reserved capacity at lower cost, closed to new customers in September 2024 and was turned down on 18 March 2026. Google directs its users to Pub/Sub or Google Cloud Managed Service for Apache Kafka.

Potential strengths

  • No partitions or clusters to size: Google documents per-message parallelism, so consumer concurrency is not capped by a partition count
  • A single flat throughput price in all regions, with a 10 GiB monthly free tier, makes small workloads simple to estimate

Trade-offs

  • Pub/Sub uses its own API rather than the Kafka protocol; Google sells Managed Service for Apache Kafka separately for Kafka workloads
  • The 1 KB minimum per request makes unbatched small messages expensive, and Pub/Sub Lite, the lower-cost option, was turned down on 18 March 2026
Sources and status

Aiven for Apache Kafka

mid-marketaiven.io ↗
Consider forTeams that want upstream open-source Apache Kafka run for them on the cloud of their choice with fixed published plan prices, because Aiven documents managed Kafka on six cloud providers with a Free and a $35 per month Developer plan
Pricing notesPlan-based. Free: $0 per month. Developer: $0.04 per hour, $35 per month. Professional: from $180 per month, listed at $3.84 per hour for the plan shown. Services are billed hourly and invoiced monthly; networking is metered by consumption, and high-volume streaming is quoted by sales. A 30-day free trial is offered for larger plans (checked Oct 2026)
Feature to evaluateDiskless topics based on KIP-1150 write to object storage and run in the same cluster as sub-100 ms topics, alongside managed Kafka Connect and a Karapace schema registry

Aiven is a managed open-source data platform, and Aiven for Apache Kafka is its hosted Kafka service. The vendor handles provisioning, patching, high availability, backups and security, and states that it employs Apache Kafka open-source committers who contribute to the project. The product page lists Kafka 4.3 as the current version.

The service runs on Amazon Web Services, Google Cloud, Microsoft Azure, DigitalOcean, OVH and UpCloud. Bring Your Own Cloud is available for larger setups, running Aiven services in the customer's own cloud account. Production clusters carry a 99.99% uptime SLA, with multi-node clusters across availability zones and automatic node recovery.

Kafka Connect is offered as a managed service with more than 50 connectors, including a managed Debezium connector for change data capture from PostgreSQL and MySQL. A schema registry is built on Karapace, Aiven's open-source project. Other listed features include consumer lag insights, follower fetching so consumers can read from replica brokers, and topic governance with ownership, approval workflows and a topic catalog.

Storage and compute scale independently through tiered storage. Diskless topics, based on the Kafka improvement proposal KIP-1150, use a leaderless design that writes to object storage such as Amazon S3, which the vendor says cuts cross-zone network fees and local disk cost. Diskless and low-latency topics can run in the same cluster. Aiven cites up to 80% lower total cost of ownership, and customer figures such as a 30-40% Kafka spend reduction at Sophos and 72% lower TCO at Claroty. These are vendor-reported results without a stated method.

Potential strengths

  • The only vendor on this page with fixed monthly plan prices published from $0, which makes small and development workloads easy to budget
  • Runs on AWS, Google Cloud, Azure, DigitalOcean, OVH and UpCloud, plus BYOC for larger setups, which suits multi-cloud teams

Trade-offs

  • Professional pricing is shown as a starting figure, and high-volume streaming and BYOC require a sales conversation
  • Diskless topics trade latency for cost: the product page lists diskless P99 latency in the 800 to 2,000 ms range
Sources and status

StreamNative

specialiststreamnative.io ↗
Consider forOrganisations using Apache Pulsar, or wanting Kafka-protocol streams stored directly as Iceberg or Delta tables, because StreamNative documents Pulsar and Kafka protocol support on its Ursa storage engine
Pricing notesUsage-based with published starting points. Serverless: from $73 per month, metered in ETUs. BYOC: from $365 per month, metered in ETUs with usage-based billing. Dedicated: from $505 per month, metered in compute and storage units (CU/SU) on AWS, Google Cloud or Azure. Private Cloud pricing is not published. Billing is monthly by default, with discounts for annual and multi-year commitments (checked Oct 2026)
Feature to evaluateUrsa, a lakehouse-native storage engine, keeps streams alongside Apache Iceberg and Delta Lake tables on object storage, with Pulsar and Kafka protocols on top

StreamNative sells StreamNative Cloud, a managed platform for Pulsar and Kafka-protocol streaming. The vendor was named in The Forrester Wave: Streaming Data Platforms, Q4 2025, according to its homepage.

The core of the current product is Ursa, which StreamNative calls a lakehouse-native engine. Ursa is the storage layer behind what the vendor calls Lakestream: streams are kept on object storage next to Apache Iceberg and Delta Lake tables, so the same data serves real-time consumers and analytical queries without a separate stream-to-table pipeline. Kafka and Pulsar both run on this storage. StreamNative states that Kafka APIs stay in place, so applications move to Ursa without rewrites.

Pulsar remains a standalone offering, used for messaging with multi-tenancy, geo-replication and low-latency queue delivery. Pulsar clusters on StreamNative Cloud support both Pulsar and Kafka-compatible protocols. A cost-optimised cluster profile supports the Kafka protocol only, and dedicated Kafka clusters are marked as coming soon on the pricing page.

Deployment options are Serverless on shared infrastructure, Dedicated clusters on AWS, Google Cloud or Azure in single or multi-zone setups, BYOC clusters in the customer's cloud account with elastic autoscaling, and StreamNative Private Cloud for self-managed use. Named customers include Iterable, Blueshift and Q6 Cyber. The vendor cites a 50% cloud cost reduction at Safari AI, and describes Ursa as reducing total cost of ownership without a published percentage. A free trial is available.

Potential strengths

  • The main managed option on this page for Apache Pulsar, with Pulsar features such as multi-tenancy, geo-replication and queue semantics
  • Published starting prices for Serverless, BYOC and Dedicated give a clearer entry point than vendors that publish meters only

Trade-offs

  • The ETU and CU/SU meters are vendor-specific units, so buyers need the vendor's sizing to compare with per-GB pricing elsewhere
  • The pricing page marks dedicated Kafka clusters as coming soon, so Kafka-only buyers should confirm which profile and protocol their workload will use
Sources and status

How to choose a vendor

Decide whether the Kafka protocol is a requirement

Teams with existing Kafka clients, connectors and skills can move to Confluent, Redpanda, Aiven or the Kafka endpoint of Azure Event Hubs with little code change. StreamNative serves Kafka and Pulsar protocols. Amazon Kinesis Data Streams and Google Cloud Pub/Sub use their own APIs, and AWS and Google point Kafka users to separate managed Kafka services.

Model cost from the meters, not the headline price

Each service bills differently. Confluent charges eCKU-hours plus per-GB ingress, egress and storage. Kinesis charges per stream-hour and per GB in on-demand mode, or per shard-hour in provisioned mode. Event Hubs charges per throughput, processing or capacity unit hour. Pub/Sub charges per TiB of throughput. Run one month of expected traffic, retention and consumer fan-out through each vendor's calculator before comparing.

Check retention, replay and lakehouse output

Retention limits and the cost of keeping data differ widely. Event Hubs keeps data up to 7 days on Standard and 90 days on Premium and Dedicated. Kinesis offers long-term retention up to 365 days. Confluent Tableflow, Redpanda Iceberg topics, Aiven diskless topics and StreamNative Ursa write streams to object storage or open table formats, which changes the storage bill and the analytics path.

Frequently asked questions

What is a streaming data platform?

A streaming data platform stores events, such as clicks, payments, sensor readings or database changes, as ordered streams and delivers them to many consumers within milliseconds or seconds. Producers and consumers are decoupled, and consumers can replay data within the retention period. Apache Kafka is the most widely used protocol; Kinesis, Event Hubs, Pub/Sub and Pulsar are the main alternatives.

How do streaming data platforms charge?

Mostly by usage meters rather than seats. Confluent charges eCKU-hours plus per-GB networking and storage. Kinesis charges stream-hours and per GB, or shard-hours. Event Hubs charges per throughput, processing or capacity unit hour. Pub/Sub charges $40 per TiB after 10 GiB free. Aiven publishes fixed monthly plans, StreamNative publishes starting prices, and Redpanda publishes meters but no rates.

Which platforms are compatible with Apache Kafka?

Confluent and Aiven run Apache Kafka. Redpanda offers a Kafka API-compatible engine. Azure Event Hubs exposes a Kafka endpoint from the Standard tier upward. StreamNative supports the Kafka protocol on its Ursa engine and Pulsar clusters. Amazon Kinesis Data Streams and Google Cloud Pub/Sub use their own APIs; AWS and Google sell separate managed Kafka services.

Is there a free tier?

Several. Confluent Cloud Basic starts at $0 with the first eCKU free, and the product page cites $400 in credits for new developers. Aiven has a $0 Free Kafka plan. Pub/Sub includes the first 10 GiB of throughput each month. Redpanda Serverless offers a 30-day trial without a credit card. StreamNative offers a free trial. Free tiers carry throughput and storage limits.

How long can data be retained?

Limits vary. Kinesis defaults to 24 hours and extends to seven days, or 365 days with long-term retention. Event Hubs allows 1 day on Basic, 7 days on Standard and 90 days on Premium and Dedicated. Confluent Standard, Enterprise and Freight list unlimited storage. Pub/Sub bills retained messages at $0.27 per GiB-month. Aiven, Redpanda and StreamNative use tiered or object storage.

Should a team choose a cloud-native service or a Kafka vendor?

A cloud-native service such as Kinesis, Event Hubs or Pub/Sub suits teams committed to one cloud that want native triggers into that cloud's functions and analytics. A Kafka vendor such as Confluent, Redpanda, Aiven or StreamNative suits teams running across clouds, reusing Kafka clients and connectors, or needing BYOC deployment in their own account.

What is BYOC and which vendors offer it?

Bring Your Own Cloud means the vendor operates the streaming cluster inside the customer's own cloud account, so data stays in that account while the vendor handles operations. Redpanda sells BYOC on annual commitment, StreamNative lists BYOC from $365 per month, Aiven offers BYOC for larger setups, and Confluent offers WarpStream for the same purpose.

How was this comparison made?

Each product was compared on its vendor's public product, documentation and pricing pages, checked in October 2026; Azure rates come from Microsoft's Retail Prices API for East US. No product was tested hands-on and no vendor confirmed its entry. Prices are list rates and exclude data transfer and taxes. Order reflects source readiness and content sequence, not quality.

Suggest a vendor or correction

Send factual corrections to editorial@statwharf.com. Corrections are free. For inclusion or placement enquiries, contact partnerships.

Contact partnerships

First published October 2026. Page update dates reflect editorial changes, not a fresh check of every vendor.