Open-source distributed event streaming platforms that provide scalable data processing capabilities without relying on Confluent.
AutoMQ is a cloud-native streaming platform and Kafka-compatible message broker. It implements the Kafka protocol to provide integration with existing clients and ecosystems while functioning as a message queue that persists data directly to cloud object storage. The system decouples compute from storage, allowing processing power and storage capacity to scale independently. It utilizes a shared-log architecture and object-storage-based persistence to remove dependencies on local disks, which reduces operational costs and eliminates manual disk management. The platform includes mechanisms fo
AutoMQ is a cloud-native, self-hostable streaming platform that implements the Kafka protocol and uses object storage for persistence, offering Kafka API compatibility, high availability, and a shared-log architecture — squarely the kind of self-hosted Kafka alternative this search needs.
Jocko is a cloud-native event streaming platform and distributed commit log implemented in Go. It functions as a distributed message broker that ensures data durability and high availability by replicating record sequences across a cluster. The system is designed as a Zookeeperless event streamer, utilizing built-in consensus coordination to manage cluster state and leader election without requiring external coordinator services. It implements the Kafka wire protocol, allowing it to communicate with existing ecosystem clients and tools. The platform provides capabilities for distributed log
Jocko is a Kafka-wire-protocol-compatible event streaming platform that runs as a single binary without Zookeeper and replicates logs for high availability, fitting your self-hostable Kafka alternative requirement, though it currently lacks a built-in schema registry, connector ecosystem, and stream processing (KSQL).
Apache Pulsar is a cloud-native distributed pub-sub messaging system designed for high-performance data ingestion. It functions as a geo-replicated data streamer and a multi-tenant event streaming platform, providing a serverless stream processing engine and a tiered storage messaging broker. The system distinguishes itself by separating serving layers from storage layers to allow independent scaling of compute and data retention. It features native geo-replication to synchronize messages across different geographical regions and employs a multi-layered tenant isolation model using authentica
Apache Pulsar is a self‑hostable, cloud‑native event streaming platform that provides Kafka‑compatible APIs, a built‑in schema registry, a connector ecosystem, and serverless stream processing, making it a comprehensive alternative to Confluent’s Kafka while meeting your key requirements for high availability and geo‑replication.
Kafka is a distributed event streaming platform designed for capturing, storing, and processing real-time data streams across interconnected nodes. It functions as a distributed commit log, providing a fault-tolerant storage mechanism that records state changes sequentially to ensure data consistency and durability across distributed environments. The platform distinguishes itself through a partitioned commit log architecture that enables horizontal scaling and parallel processing of data streams. It integrates a stream processing engine for continuous transformations and aggregations, while
Apache Kafka is the core open-source event streaming platform you’re looking for, but this repository provides only the foundational distributed commit log and stream processing engine — it does not include the schema registry, connector ecosystem, or KSQL that you would get in a full Confluent distribution; you would need to add those as separate projects.
Redpanda is a distributed event streaming engine designed to serve as a high-performance, drop-in replacement for existing event-driven architectures. It provides a foundation for building and scaling applications that require reliable data movement, analytical querying, and strict operational compliance across both cloud and self-managed environments. The platform distinguishes itself through a shared-nothing architecture that utilizes thread-per-core execution and a non-blocking asynchronous input/output engine to maximize throughput. It maintains data consistency through a consensus-based
Redpanda is a distributed event streaming engine built as a drop-in Kafka replacement with Kafka API compatibility, self-hosting, stream processing, and replication support, making it exactly the self-hostable managed-Kafka alternative you are looking for.
Fluvio is a distributed event streaming platform and cloud-native streaming engine designed for collecting, persisting, and replicating real-time data streams across a distributed cluster. It functions as a real-time data pipeline for building stateful workflows that ingest, enrich, and export data between external sources and sinks. The platform is distinguished by its use of WebAssembly to execute compiled modules for in-line data transformations and filtering. This allows for the execution of custom business logic to reshape information in motion without requiring a restart of the cluster.
Fluvio is a self-hostable distributed event streaming platform with connectors and replication, making it a member of the category you're looking for; however, it does not offer Kafka API compatibility, schema registry, or KSQL-style stream processing, so it fills only part of what Confluent provides.