HiveMQ

HiveMQ Community Edition is a Java-based, open-source Message Queuing Telemetry Transport (MQTT) broker that supports MQTT 3.x and MQTT 5 for lightweight…

  • Databases
  • Other
  • Tools & Utilities
HiveMQ Community Edition is a Java-based, open-source Message Queuing Telemetry Transport (MQTT) broker that supports MQTT 3.x and MQTT 5 for lightweight messaging between devices and applications.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • 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.

70/100 Good

Maintained
100last commit 5 days ago
Popular
621,217 GitHub stars
Easy to install
251 install platform, install notes
Light to run
502 GB minimum RAM
Security check
80no serious findings, CI, tests, OpenSSF Scorecard 5.8/10

Availability: platform listings confirmed today, links checked 12 days ago

GitHub stars
1,217
Open issues
29
Last commit
2026-11-16
Latest release
2026.5
License
Apache-2.0
Activity
steady

Checked 5 days ago - source: GitHub (hivemq/hivemq-community-edition)

Resources & Compatibility

Minimum requirements: 2 GB RAM.

Checked 39 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Point your app at the broker host and port In the MQTT client settings, point to your HiveMQ broker (the server that handles MQTT messages) by setting serverHost and serverPort, for example 8883 when using TLS (the secure connection type). If the host, port, or firewall is wrong, the app cannot connect and no messages will flow. source
  • Add a username and password if required If your HiveMQ broker requires login, set the username and password in the connection settings, like the username/password section in the example. If you leave these out when they are required, the broker will reject the connection and the app will appear unable to sign in. source
  • Give each device a unique client ID Give each device a unique client ID, the label HiveMQ uses to recognize that connection, such as my-mqtt-device-001. If two devices use the same ID, HiveMQ may disconnect one of them or confuse their sessions, causing dropped messages. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I start HiveMQ CE from the downloaded package?

Unzip the downloaded package, then run run.sh on Linux or macOS and run.bat on Windows from the bin folder. Java 11 or later is required to run it.

Which port should I use for a TLS MQTT connection to HiveMQ?

Point the MQTT client to the broker host and the TLS port, for example 8883. If the host, port, or firewall is wrong, the client cannot connect.

What should I configure if my HiveMQ broker requires login?

Set the username and password in the MQTT client connection settings. If required credentials are omitted, the broker rejects the connection and the app appears unable to sign in.

Why must each MQTT device have a unique client ID?

HiveMQ uses the client ID to recognize a connection. If two devices use the same ID, HiveMQ may disconnect one or confuse their sessions, causing dropped messages.

Answers sourced from github.com, github.com, github.com, github.com

Community

Collected 25 days ago - public community threads