TBMQ 2.1 introduces native HTTP, MQTT, and Kafka integrations—plus an official Helm chart to make deploying your MQTT infrastructure easier than before.

Our architecture introduces a new Integration Executor microservice, ensuring that outbound integrations have zero impact on the core MQTT broker’s performance.

Yes, TBMQ currently uses Redis, but as a fully open-source broker that prioritizes open-source technologies, we’re following the community shift to Valkey and plan to support it in the next release.