HiveMQ Platform Operator

HiveMQ Platform Operator is a Kubernetes operator that automates the installation, configuration, scaling, and lifecycle management of HiveMQ Platform MQTT…

  • Databases
  • Infrastructure
  • Tools & Utilities
HiveMQ Platform Operator is a Kubernetes operator that automates the installation, configuration, scaling, and lifecycle management of HiveMQ Platform MQTT broker clusters. It is designed for platform engineers and DevOps teams who need to deploy and manage MQTT brokers on Kubernetes without manual intervention.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

35/100 Low

Maintained
62last commit 176 days ago
Popular
00 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
0
Open issues
0
Last commit
2026-05-29
License
Apache-2.0
Activity
stale

Checked 14 days ago - source: GitHub (sjentzsch/hivemq-helm-charts)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Point MQTT clients at the right broker address Set the broker hostname and port in your MQTT client settings; the example uses 8883 with TLS. If these are wrong, client apps cannot connect. source
  • Use authentication and persistent sessions If your broker requires login, put the username and password in the client's CONNECT settings. If you want a device to resume its old session, set clean start to false; otherwise it may start with no previous state. source
  • Publish exact topics, subscribe with wildcards Use a plain topic like home/temperature when publishing, and patterns like home/+/temperature or home/# only when subscribing. Wrong patterns are why devices miss messages. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What does the HiveMQ Platform Operator deploy into Kubernetes?

It installs HiveMQ based on the supplied configuration.

Why would a self-hosted deployment migrate from the HiveMQ Legacy Operator to the Platform Operator?

The Platform Operator is a major upgrade from the Legacy Operator. Migration is driven by Kubernetes changes and current cloud-native best practices.

Answers sourced from docs.hivemq.com, docs.hivemq.com

Community

Collected 48 days ago - public community threads