Life & fun · alternatives · 2026
24 alternatives to Liftbridge – lightweight, fault-tolerant message streams
Kafka-style message streaming in Go. Built on NATS. Single binary, no JVM, no ZooKeeper. - liftbridge-io/liftbridge
Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes. Prices are shown for the 1 we have checked on their own sites, 1 of them free or with a free tier. Liftbridge – lightweight, fault-tolerant message streams launched in 2018; newer entries below may have overtaken it.
- 1
Lightweight, fault-tolerant message streams
2020 · liftbridge.io · its alternatives →
- 2
A realtime server for the modern web
2016 · deepstream.io · its alternatives →
- 3
Scalable open source pub/sub SDK with support for RPC, JWT authentication and Kubernetes — optimized for async/await
2016 · socketcluster.io · its alternatives →
- 4
🦭 Distributed log streaming engine built from first principles - nubskr/walrus
Dec 2025 · github.com · its alternatives →
- 5PD
PicoMQ is a Rust server for Durable Streams, built on Object Store. Cheap, URL-addressable, granular streams (create/append/read/long-poll/SSE), with Pico Protocol or Durable Streams Protocol as the facade. S3Stream is the stream storage primitive, used in AutoMQ, shipped as a Rust library. Coordination is a command log in Postgres.
Aug 2026 · picomq.com · its alternatives →
- 6
Contribute to panyam/KafkaLite development by creating an account on GitHub.
2015 · github.com · its alternatives →
- 7
Hello Everyone! We built SQLFlow as a lightweight stream processing engine. We leverage DuckDB as the stream processing engine, which gives SQLFlow the ability to process 10's of thousands of messages a second using ~250MiB of memory! DuckDB also supports a rich ecosystem of sinks and connectors! https://sql-flow.com/docs/category/tutorials/ https://github.com/turbolytics/sql-flow We were tired of running JVM's for simple stream processing, and also of bespoke one off stream processors I would love your feedback, criticisms and/or…
Dec 2025 · sql-flow.com · its alternatives →
- 8
Goka is a compact yet powerful distributed stream processing library for Apache Kafka written in Go. - lovoo/goka
2017 · github.com · its alternatives →
- 9
Hey HN – I built Dock after years of team chat frustrations as a founder. Free forever for teams up to 5. Unlimited search, unlimited history. No "upgrade to see messages older than 90 days" nonsense. Built for teams who work both async and sync/real-time when it matters. runs on SOC 2 infra, compliant, secure and in-transit and at-rest encryption, runs on Cloudflare. Early stage – would love feedback from anyone who's felt the same pain.
Jan 2026 · getdock.io · its alternatives →
- 10
Kafka 0.8.0 broker implementation on top of Cloudflare Workers - maxwellpeterson/kafka-worker
2022 · github.com · its alternatives →
- 11
When building Hookie, I worked with NATS Jetstream a lot. While you can do everything using the CLI, I prefer the feeling of a nice GUI better. So I built one.
Aug 2026 · streambench.app · its alternatives →
- 12
Hi HN, I’m excited to share Kameo, a lightweight Rust library that helps you build fault-tolerant, distributed, and asynchronous actors. If you're working on distributed systems, microservices, or real-time applications, Kameo offers a simple yet powerful API for handling concurrency, panic recovery, and remote messaging between nodes. Key Features: - Async Rust: Each actor runs as a separate Tokio task, making concurrency management simple. - Remote Messaging: Seamlessly send messages to actors across different nodes. - Supervision and Fault Tolerance: Create self-healing systems with actor…
2024 · github.com · its alternatives →
- 13
Kafka-based Job Queue for Python. Contribute to joowani/kq development by creating an account on GitHub.
2016 · github.com · its alternatives →
- 14
Hey, I'm a co-founder at ElectricSQL. Durable Streams is the delivery protocol underneath our Postgres sync engine—we've been refining it in production for 18 months. The core idea: streams get their own URL and use opaque, monotonic offsets. Clients persist the last offset they processed and resume with "give me everything after X." No server-side session state, CDN-cacheable, plain HTTP. We kept seeing teams reinvent this for AI token streaming and real-time apps, so we're standardizing it as a standalone protocol. The repo has a reference Node.js server and TypeScript client. Would love…
Dec 2025 · github.com · its alternatives →
- 15
We started CallFS after yet another late-night “why did the uploads vanish?” incident. Our small team had stitched together rsync, a fragile NFS mount, and an S3 bucket—none of it observable, all of it waiting to bite us. So we wrote a single-process file service in Go that: • Speaks the S3 API (so existing tooling works). • Stores hot data on local disks for speed; cold data can sit in any S3-compatible bucket. • Exposes Prometheus metrics and JSON logs by default, because “what happened?” shouldn’t be guesswork. • Ships as a ~25 MB static binary—no external deps, MIT license. Today it’s…
2025 · github.com · its alternatives →
- 16
Hi HN, I built Ayder — a single-binary, HTTP-native durable event log written in C. The wedge is simple: curl is the client (no JVM, no ZooKeeper, no thick client libs). There’s a 2-minute demo that starts with an unclean SIGKILL, then restarts and verifies offsets + data are still there. Numbers (3-node Raft, real network, sync-majority writes, 64B payload): ~50K msg/s sustained (wrk2 @ 50K req/s), client P99 ~3.46ms. Crash recovery after SIGKILL is ~40–50s with ~8M offsets. Repo link has the video, benchmarks, and quick start. I’m looking for a few early design partners (any…
Jan 2026 · github.com · its alternatives →
- 17BA
2012 · flotype.com · its alternatives →
- 18
Kafka Socks▲81An easy-to-use, lightweight KafkaJS to Socket.io library
2021 · github.com · its alternatives →
- 19
- 20
- 21
🦎 A lightweight, multi-protocol gateway for event-driven applications and AI agents. Expose and govern Kafka, MQTT, APIs, and MCP through one high-performance engine with shared routing, security, schema, and observability. - aklivity/zilla
2023 · github.com · its alternatives →
- 22
I built a message broker that speaks the Kafka wire protocol, so any Kafka client (librdkafka, kafka-python, kcat, etc.) works without code changes. The entire binary is 52KB. No JVM, no ZooKeeper, no third-party libraries — just C++20 with kqueue/epoll. Starts in <10ms, uses 0% CPU when idle. I built this because running Kafka locally for development is painful — gigabytes of RAM, slow startup, ZooKeeper/KRaft configuration. I just wanted something that accepts produce requests and gets out of the way. Technical details: - Single-threaded event loop (kqueue on macOS, epoll on…
Feb 2026 · github.com · its alternatives →
- 23
Hey HN! I'm excited to announce the release of Kiwi v0.1.1. I started working on Kiwi a few months ago with the primary motivation of providing an extensible WebSocket adapter that allows client applications to securely subscribe to real-time data sources such as Kafka. Often times, there is a desire to extend the real-time data that flows through sources like Kafka to end users in a fast and secure manner. Rather than standing up custom solutions, Kiwi lets operators focus on writing business logic, by loading custom WASM plugins that handle tasks like authorization and event filtering per…
2024 · github.com · its alternatives →
- 24
Simple configuration and mocking of Kafka clients. Contribute to obsidiandynamics/jackdaw development by creating an account on GitHub.
2019 · github.com · its alternatives →
Also compare
- Liftbridge – Lightweight, fault-tolerant message streams alternatives
- Deepstream.io – open-source real-time server with pub/sub and data sync alternatives
- SocketCluster.io – flexible open-source real-time server with pub/sub alternatives
- Walrus – a Kafka alternative written in Rust alternatives
- PicoMQ – Durable Streams over HTTP, on object storage alternatives
- KafkaLite – A simple message broker inspired by Kafka alternatives
Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →