dlandiak
Most MQTT brokers hit a ceiling when you need to scale horizontally or survive node failures without message loss. We built TBMQ on Kafka because it's battle-tested at scale across the industry — you get fault tolerance, high throughput, and horizontal scalability as a foundation rather than something you bolt on later.
TBMQ has a Community Edition (open-source) and a Professional Edition with advanced observability, enterprise features, and monitoring. The demo runs the PE version, so you can see the full feature set without installing anything.
Two ways to try it:
- No signup: Connect via MQTT directly to "demo.tbmq.io" — ports 1883 (TCP), 8883 (TLS), 443 (WSS), username - "demo", and no password. Test pub/sub, shared subscriptions, retained messages. Public environment, so no sensitive data.
- Quick SSO signup: Head to https://demo.tbmq.io for read-only access to the full professional UI — live session/subscription browsing, message flow dashboards, and more.
Happy to answer questions about the architecture or tradeoffs. Fair criticism welcome.
TBMQ 2.1 levels up your MQTT stack with embedded integrations and Helm support
Open-source MQTT broker shows market-leading performance
Key points can be found there and everyone will choose their own priorities. For us these are: * https://bloomberg.github.io/blazingmq/docs/introduction/comp... * https://bloomberg.github.io/blazingmq/docs/introduction/comp... (Kafka is Java as well as TBMQ, Kafka already does not depend on Zookeeper) * https://bloomberg.github.io/blazingmq/docs/introduction/comp... * https://bloomberg.github.io/blazingmq/docs/introduction/comp... (for this we recommend reviewing our test - https://thingsboard.io/docs/mqtt-broker/reference/3m-through...)
You can find another test here: https://thingsboard.io/docs/mqtt-broker/reference/3m-through...
Please see the architecture doc for more details: https://thingsboard.io/docs/mqtt-broker/architecture/
We have implemented TBMQ to satisfy our enterprise customers' needs. Some of them used hivemq before but decided to ask us to build a new solution (TBMQ) as they were not fully satisfied with hivemq. One of the most important advantages we provided is cluster support in our open-source version compared to hivemq.