Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

Waterstream review

#24 of 46 in MQTT Broker Software

A focused MQTT-to-Kafka broker for teams that already run Kafka-compatible streaming.

6.8/10Editor score
Waterstream6.8 Contact Waterstream

Reviewed by iTechGuides Editors · Editorial team · Updated Nov 2026

Waterstream is a commercial MQTT broker that connects MQTT clients with Kafka topics in both directions. It is aimed at IoT teams already using Kafka-compatible streaming platforms, including mid-market and enterprise deployments. Teams can deploy it as a Docker image at the edge, on-premises, or in the cloud, either standalone or in Kubernetes. Its Kafka dependency is central to its value: this is a way to give MQTT clients access to a Kafka-backed data flow, rather than a general-purpose broker for environments without Kafka.

The product’s main distinction is how it uses Kafka as both persistence layer and integration point. It stores MQTT messages and client state in Kafka, and can deliver Kafka records to clients over MQTT or WebSockets. Rewinding to earlier message history uses Kafka, while Schema Registry validation can check messages against schemas. Bridge mode connects Waterstream to an existing MQTT broker. Apache Kafka, Confluent Cloud, IBM Event Streams, and Redpanda are named integrations; Prometheus metrics and Grafana support observability. Stateless multi-instance scaling behind a load balancer is suited to deployments that need to scale broker instances.

Deployment options include self-hosted and cloud, with Docker and Kubernetes support; the product also supports MQTT 3.1 and MQTT 5. Authentication methods include username/password, client certificates, and JWT. Waterstream is commercially licensed, and prospective buyers are directed to contact sales. A free development license is available, but it is not a perpetual free plan. This approach makes sense for organizations willing to operate Kafka and seeking MQTT access to that ecosystem. Teams looking for an MQTT broker without a Kafka dependency, or a publicly priced product with support beyond documentation, should consider alternatives.

Waterstream pros and cons

  • Where it wins
    • Persists MQTT messages and client state in Kafka for replay.
    • Supports bidirectional MQTT and Kafka integration, including WebSockets.
    • Scales statelessly across instances and exposes Prometheus metrics for Grafana.
  • Where it doesn't
    • Requires Kafka, limiting its fit for standalone MQTT deployments.
    • Commercial licensing and contact-sales pricing add a buying step.
    • Setup and support detail centers on documentation and deployment expertise.

Waterstream fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update