Streaming

Event streaming and messaging.

6 listings, including 6 from other publishers. Entries cover the deployment options documented on their individual pages.

Watch this category with RSS · Build a requirements shortlist

Deployment comparison

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
Aiven for Apache Kafka BYOCAWS, Azure, Google CloudVendor-operated BYOC
Servers / containers
Commercial Only

Commercial managed service. BYOC requires an Aiven commitment and Advanced or Premium support. Aiven and the cloud provider bill separately.

Enable BYOC with Aiven, apply the provider-specific Terraform template, then provision Classic Kafka through the Aiven Console or CLI.Aiven manages provisioning and maintenance. The customer provides the cloud account, network configuration, IAM, quotas, and backup storage access.
Scope and evidence

Classic Kafka uses fixed service plans. Diskless topics require enablement and an eligible custom cloud and plan. Aiven documents limited OCI access for its wider BYOC program. Confirm product and region eligibility. Metrics and logs reach Aiven, and controlled support access is documented. Agree how to migrate topics and remove delegated access before exit.

  • Aiven custom cloud on AWS — The customer applies a Terraform template in its AWS account and grants Aiven permissions through an IAM role.

    Vendor / upstream documentation · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Aiven custom cloud on Azure — The customer sets up an Azure custom cloud in its subscription before provisioning Kafka.

    Vendor / upstream documentation · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Aiven custom cloud on Google Cloud — The customer sets up a Google Cloud custom cloud in its project before provisioning Kafka.

    Vendor / upstream documentation · Reviewed 2026-11-21. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-21

Apache KafkaGoogle CloudCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for upstream Apache Kafka.

Run the official Java distribution or Apache Kafka container image; configure the documented broker/controller topology for production.Customer manages broker capacity, replication, retention, authentication, authorization, monitoring and upgrades.
Scope and evidence

The single-node quickstart is an evaluation starting point. Commercial Kafka distributions, hosted services and independently licensed connectors are outside this upstream listing.

  • Apache Kafka deployment on GKE using Strimzi — Google documents creating customer GKE infrastructure and deploying Apache Kafka through the Strimzi operator. This is upstream Kafka operated in the customer project, not Confluent Cloud. The published tutorial includes version-specific ZooKeeper/KRaft assumptions; verify current Kafka and Strimzi compatibility and production security.

    Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Apache PulsarAWSCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for upstream Apache Pulsar.

Use the official Helm chart on a customer-operated Kubernetes cluster; standalone Docker is documented for development and evaluation.Customer manages brokers, bookies, metadata, durable volumes, retention, access controls and upgrades.
Scope and evidence

The cited 4.2 deployment guide belongs to a maintained release line. Match chart and service versions; standalone mode is not equivalent to a resilient production cluster. Connectors and remote sinks have separate boundaries.

  • Apache Pulsar 4.2 deployment on AWS — The upstream 4.2 guide provisions EC2 instances and networking with Terraform, then installs Pulsar with Ansible in the customer AWS account. Review the selected release, instance types, persistence and network access before using the example.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Cloudera on CloudAWS, Azure, Google CloudShared operations · vendor control plane
Servers / containers
Commercial Only

Commercial Cloudera subscription with cloud infrastructure charges paid separately.

Register the customer cloud environment and credentials, then provision Cloudera workload services through the control planeCloudera operates the service control plane; the customer owns cloud resources, credentials, data governance, network integration, workload sizing and shared operational responsibilities.
Scope and evidence

This entry covers Cloudera's public-cloud BYOC service, not a fully customer-operated software distribution. Workloads and data run in the customer's AWS, Azure or Google Cloud environment while Cloudera operates the control plane. Service availability and implementation details differ by provider, especially on Google Cloud, so confirm each required service before procurement. Cloudera November bulletins cover critical Brotli CVE-2026-111497 and compromised eMudhra certificates. Use the TSB matrices for the exact Runtime or Private Cloud Base component and fixed build rather than applying a generic platform version.

  • Cloudera workloads in customer AWS, Azure and Google Cloud environments — Cloudera documents registering customer AWS, Azure and Google Cloud environments and credentials so its control plane can provision workload resources. Provider service availability differs and must be checked for the selected workload.

    Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-17

Confluent Platform Self-ManagedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

A commercial Confluent subscription is required for Confluent Platform components deployed with CFK; component licenses otherwise vary.

Install the Confluent for Kubernetes operator with Helm, then deploy Confluent Platform components through Kubernetes custom resources.Customer manages Kubernetes clusters, node pools, persistent storage, load balancers, DNS and routing, identity and RBAC, secrets, backups, scaling and upgrades; CFK reconciles the declared Confluent application resources.
Scope and evidence

This entry covers self-managed Confluent Platform deployed with Confluent for Kubernetes, not Confluent Cloud. Current CFK guidance explicitly addresses Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine. Provider examples do not certify every Kubernetes, Confluent Platform or topology combination; use the current supported-environments matrix and validate cross-cluster networking, storage, security, version compatibility and subscription terms. Confluent's November 2026 security releases address multiple broker, Kafka Connect, ZooKeeper, TLS trust, JWT, file-read, and denial-of-service issues. Upgrade to the latest patched release for the deployed branch: 7.6.15, 7.7.13, 7.8.12, 7.9.11, 8.0.9, 8.1.7, 8.2.5, 8.3.3, or 8.4.1. Until patched, deployments using a separate Kafka Connect administrative listener should remove admin.listeners; the ZooKeeper fix applies to the affected 7.x lines identified by Confluent. CONFSA-2026-37 covers CVE-2026-114938 in Confluent Platform 7.6.x–8.4.x and Control Center 2.0.x–2.7.x when package/archive installs use affected customer JDKs, plus specified Docker-image ranges. Fixed-runtime releases were still being prepared at review time. Apply -XX:-UseBASE64Intrinsics to every affected Java process, restart and verify the flag until the applicable fixed image or runtime is available.

  • Confluent for Kubernetes guidance for EKS, AKS and GKE — The current CFK multi-region guide explicitly identifies Google Kubernetes Engine, Amazon Elastic Kubernetes Service and Azure Kubernetes Service for provider-specific configuration and validation. The CFK overview defines the product as managing self-managed Confluent Platform in the customer's own Kubernetes environment. This evidence does not include the separately operated Confluent Cloud service.

    Vendor / upstream documentation · Reviewed 2026-11-16. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-16

Redpanda BYOCAWS, Azure, Google CloudVendor-operated BYOC
Servers / containers
Commercial Only

Commercial

Redpanda Cloud BYOC provisioningRedpanda manages provisioning, monitoring and upgrades with the permissions you grant.
Scope and evidence

BYOC supports AWS and Google Cloud VPCs and Azure VNets. BYOVPC/BYOVNet lets the customer provision networking first. Review agent permissions and emergency support access. Redpanda Cloud's November update adds Load Factor dashboard metrics for BYOC deployments on version 26.2 or later. Treat the October BYOVNet, self-service scaling, and Azure tier announcements as separate earlier changes when planning upgrades.

  • Redpanda BYOC supported infrastructure — Redpanda explicitly documents BYOC clusters in the customer AWS or Google Cloud VPC or Azure VNet, with a Redpanda-operated control plane. The architecture and provisioning requirements differ by provider; this is the BYOC offering, not Dedicated clusters in the vendor account.

    Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-12

Choose 2–4 listings to compare

Browse listing cards

How these listings fit

Aiven for Apache Kafka BYOC
Managed Apache Kafka brokers in the customer's cloud account, operated by Aiven.
Apache Kafka
Distributed event log with topics, producers, consumers and stream processing integrations; applications and connectors determine downstream processing.
Apache Pulsar
Distributed messaging and streaming with persistent topics and separately scalable serving and storage components.
Cloudera on Cloud
Cloudera provides streaming ingestion and processing services where supported by the selected cloud deployment.
Confluent Platform Self-Managed
Runs Apache Kafka brokers together with schema, connector and stream-processing services for customer-operated event streaming.
Redpanda BYOC
Managed Kafka-compatible streaming in your cloud account.

Review dates and sources appear on each listing. Functionality, edition, deployment and licensing must be checked together. Filter this category with cloud and deployment controls →

All categories · Suggest a listing or correction