Book a consultation

HiveMQ

HiveMQ Community Edition and HiveMQ's Open-Source Footprint

HiveMQ Community Edition explained: the Apache 2.0 broker, Edge, the Java client, MQTT CLI, what CE lacks against Enterprise, and how it fails.

Vladimir Romanov


HiveMQ Community Edition (CE) is the open-source core of HiveMQ’s MQTT broker: Java code under the Apache License 2.0, on GitHub, implementing MQTT 3.1, 3.1.1 and 5.0. It is a real broker, and it is on the Eclipse Sparkplug compatible list. What it is not is the product HiveMQ sells for sites that cannot lose their broker, because clustering, the Enterprise Extensions and the support sit on the other side of a licence line. This page maps that line, explains what an open-core broker means for a plant, and describes how a Community Edition deployment typically fails. It belongs to the HiveMQ technology cluster, and the company behind it is profiled on the HiveMQ company page.

What HiveMQ publishes as open source

HiveMQ states that it launched an open-source community on 16 April 2019, with Community Edition and the HiveMQ MQTT Client, both in Java, and that its commercial editions are built on Community Edition. The GitHub organisation shows Apache 2.0 on the ten repositories we viewed on 20 November 2026. The table lists what matters to a plant.

ComponentLicenceWhat it isStatus as of 20 November 2026
Community Edition brokerApache 2.0Java MQTT broker, MQTT 3.1, 3.1.1 and 5.0Release 2026.5 is dated 27 May 2026 on HiveMQ’s changelog. The README download link names 2026.6, for which we found no dated release page
HiveMQ EdgeApache 2.0 for open features, licence key for commercial onesGateway that turns industrial protocols into MQTT and bridges to another brokerRelease 2026.16 on 10 November 2026. Open source release July 2023
MQTT Client for JavaApache 2.0Client library, blocking, asynchronous and reactive APIs1.4.2 in the README examples, no release date shown
MQTT CLIApache 2.0Command line client and broker test toolRelease version not shown on the GitHub page
Community extensionsApache 2.0Prometheus, InfluxDB, CloudWatch, Heartbeat, File RBAC, Deny Root Wildcard, MQTT Message Log, Sparkplug Aware, Sparkplug InfluxDBListed in HiveMQ’s catalogue of 29 extensions
Testcontainers moduleNot applicableTest helper for starting a broker in Java testsRepository archived 25 October 2023, moved into testcontainers-java from version 1.17.0

Two cautions on the table. HiveMQ’s catalogue lists the Splunk extension as commercial but places it in the community section, so the catalogue contradicts itself there. And we did not confirm which community extensions run on Community Edition rather than only on the Enterprise broker. The cluster discovery extensions, for instance, only make sense with clustering. Check each extension’s documentation before you design around it.

Breadboard circuit with tangled jumper wires beside a blue digital multimeter
Open-source parts are bench parts: excellent for building and testing, and the plant still owns the integration and the upkeep.

The HiveMQ Edge page covers the gateway in detail. The MQTT client and tools page covers the Java client and MQTT CLI.

HiveMQ Community Edition vs Enterprise: what CE lacks

HiveMQ’s README says CE “implements all MQTT features” and calls it the foundation of its enterprise platform. It does not list differences. The picture below comes from HiveMQ’s documentation, its pricing page and HiveMQ staff replies in its community forum on clustering, which are forum evidence and not an official matrix. Where we found no statement, the table says so.

CapabilityCommunity EditionEnterprise broker
LicenceApache 2.0Commercial licence, plans from free Lab to custom Enterprise
MQTT 3.1, 3.1.1, 5.0YesYes
ClusteringNot supported. HiveMQ staff said so in the forum in September 2021 and added in October 2021 that there were no plansDocumented masterless cluster, default replica count 2
Enterprise Extensions (Kafka, Security, databases, Bridge)Not confirmed for CE: we found no statement that they run on itIncluded in all self-managed plans, per the pricing page of 20 November 2026
Control CenterNot confirmed for CEWeb interface, version 2 since 4.55
Extension SDKOpen Community Extension SDKCommunity and Enterprise Extension SDKs
SupportCommunityCommunity on Lab and Launch, Silver on Run, Silver to Platinum on Enterprise
Sparkplug compatible listingListed by EclipseProfessional Edition listed by Eclipse

Clustering is confirmed absent, with a caveat. We checked the forum thread ourselves on 20 November 2026. The staff statements are from 2021, the README is silent, and a feature can change. Ask HiveMQ in writing before a design depends on this, in either direction. For what clustering does on the Enterprise side, see clustering and high availability, and for the plans and prices see editions and pricing.

The open-core model and what it means for a plant

Open core means the base is open and the features a production site tends to need are paid. In our view the useful question is not “open or closed” but “which feature do I need that sits behind the paid line”.

HiveMQ's open-core line Two columns separated by a dashed line. On the left, Apache 2.0 parts: the Community Edition broker, the Java MQTT client, MQTT CLI, community extensions and the open Edge gateway. On the right, parts that need a licence or plan: the clustered Enterprise broker, Enterprise Extensions, Control Center, Data Hub and the commercial Edge features. An arrow shows that Community Edition is the core the Enterprise broker is built on. Open, Apache 2.0 Licence or paid plan Community Edition broker (single node) MQTT Client for Java and MQTT CLI Community extensions (metrics, Sparkplug) Edge gateway, open features and bridge the open-core line Enterprise broker with clustering Enterprise Extensions (Kafka, Security) Control Center and Data Hub Edge southbound writes, Data Hub on Edge Community Edition is the core the Enterprise broker is built on, per HiveMQ
The open-core line: HiveMQ publishes the broker core, client tools and gateway as Apache 2.0, and sells clustering, Enterprise Extensions, management and governance features.

What it means in practice. You can build and prove a design on Community Edition at no licence cost, and moving to the Enterprise broker later is a licensing and operations change, not a rewrite, because clients speak standard MQTT. HiveMQ’s pricing page of 20 November 2026 also lists a free Lab plan with a 30-day licence and 25 connections. The cost of the open path is that you carry the work a vendor would otherwise carry: patching, monitoring, backup and the decision when to upgrade. That is a legitimate trade for a lab, a test rig and some single-line deployments. It should be a decision someone signs, not a default.

How a Community Edition deployment fails

These are our view of failure modes, drawn from general MQTT and plant practice rather than from HiveMQ documentation.

  • The pilot becomes production. A broker installed for a proof of concept on a spare server keeps running, and by the time three lines publish to it, nobody owns it. Restarting it for a patch now interrupts production data.
  • No clustering, no failover. A single node is a single failure domain. If the host dies, clients disconnect, and persistent sessions, retained messages and queued messages on that node are as safe as its disk. A Unified Namespace with retained birth and state topics needs that data back after a restart, and Sparkplug consumers need a clean rebirth. Test this deliberately.
  • Upgrade drift. Community Edition releases are irregular, several a year, against the Enterprise broker’s monthly minors with a long-term-support line. Java is a moving part too: HiveMQ’s 4.55 requires Java 21 as the minimum for the Enterprise broker, and the CE 2026.5 release notes list an upgrade of the build toolchain to Java 21. An unmaintained box falls behind on both.
  • Support gap. When a client connects and drops every thirty seconds, there is no vendor ticket. Someone on your team reads the logs and the specification.
  • Extension assumptions. A design that quietly relies on an Enterprise Extension, such as the Kafka or Security extension, fails the day it meets Community Edition.
  • Open ports and default credentials. Brokers exposed with anonymous access are a documented pattern in MQTT security studies. Place the broker in the right zone; see OT network segmentation.

What we do here

We are independent of HiveMQ and have no commercial relationship with the company. When we design a Unified Namespace or an edge architecture, we use Community Edition thinking in these ways:

  • Prove the topic tree first. A throwaway broker on a laptop or a container is enough to test namespace design, retained messages and Sparkplug state handling before the platform is chosen.
  • Draw the failure domain before choosing the edition. If a broker outage stops a whole site, we treat a cluster, or a design that tolerates broker loss, as a requirement.
  • Name an owner for any open-source broker. Patching, Java version, monitoring and backup go on a named person’s list.
  • Keep clients standard. Plain MQTT clients make it cheap to move between Community Edition, the Enterprise broker or another broker.
  • Write the upgrade path down. If Community Edition is the start, the page says what triggers the move and what it costs.

We design MQTT and Unified Namespace architectures and integrate brokers with PLCs, SCADA, historians and enterprise systems as part of IT/OT projects. We are independent of HiveMQ: we have no commercial relationship with the company and do not resell its products. If you are weighing editions, our IT/OT integration service covers that kind of review, and our MQTT in manufacturing guide covers the protocol background.

Limits and open questions

  • CE version and date. Release 2026.5 is dated 27 May 2026. The README names 2026.6, and we found no dated page for it.
  • Clustering in CE. Confirmed by 2021 staff forum statements only. No official feature matrix was found.
  • Which community extensions run on CE. Not confirmed for each one.
  • Data Hub on CE. HiveMQ documents Data Hub with the Enterprise broker. We did not confirm whether any part works on Community Edition.
  • Security advisories. GitHub shows no published security advisories and no SECURITY.md for Community Edition as of 20 November 2026. That tells you what HiveMQ has published through GitHub, not that nothing exists.
  • Sparkplug listing. The Eclipse list shows the entries without a version or date.

Deeper

  • HiveMQ vs Mosquitto: Community Edition and the Platform against the most common open-source broker, on the same dimensions.
  • MQTT client and tools: the Java client, MQTT CLI, Swarm and how to test a namespace before go-live.

For the open-source gateway beside the broker, read HiveMQ Edge. For Sparkplug on the broker, see HiveMQ and Sparkplug.

Frequently asked questions

Is HiveMQ Community Edition free for commercial use?

HiveMQ Community Edition is published under the Apache License 2.0 on GitHub, which permits commercial use. That covers the broker itself. It does not include HiveMQ's support, its Enterprise Extensions or clustering. If you run it in production, the support and the patching are yours. Read the licence text itself and have your legal team confirm.

Does HiveMQ Community Edition support clustering?

No. HiveMQ staff wrote in the company's community forum in September 2021 that CE does not support clustering, and in October 2021 that there were no plans to add it. This is forum evidence, not an official feature matrix, and HiveMQ's README does not list differences. Clustering is documented for the Enterprise broker.

What is the difference between HiveMQ Community Edition and HiveMQ Edge?

Community Edition is a central MQTT broker. HiveMQ Edge is an open-source gateway that translates industrial protocols such as OPC UA and Modbus into MQTT and bridges to another broker. Both have Apache 2.0 code. Edge also has commercial features, such as southbound writes and Data Hub on Edge, that need a licence key.

Is HiveMQ Community Edition on the Sparkplug compatible list?

Yes. The Eclipse Sparkplug compatible software page, fetched on 20 November 2026, lists HiveMQ MQTT Broker Community Edition, Professional Edition and the Sparkplug Aware Extension. The page showed no version or date for those rows, so check the version you plan to run against the Eclipse Sparkplug TCK yourself.

Should a plant run HiveMQ Community Edition in production?

It can fit a single cell or line where a broker restart is tolerable and clients reconnect and republish. It does not fit a site whose data flow must survive a broker failure, because CE has no clustering. In our view the deciding questions are the failure domain, who patches it, and who answers the phone at 2 a.m.

References and further reading

  1. hivemq-community-edition on GitHub · HiveMQLicence, README and the version named in the download link.
  2. HiveMQ CE 2026.5 released · HiveMQThe latest dated Community Edition release we found.
  3. HiveMQ launches new open source MQTT community · HiveMQ (PRWeb)The 16 April 2019 release that started the open-source line.
  4. Cluster support in Community Edition (CE) · HiveMQ Community ForumHiveMQ staff answers on clustering in CE, 2021.
  5. HiveMQ Edge documentation · HiveMQOpen-source and licensed Edge features.
  6. HiveMQ extensions catalogue · HiveMQWhich extensions are community and which are Enterprise.
  7. Eclipse Sparkplug compatible software · Eclipse Foundation

← HiveMQ

Have a project that needs technical ownership?

Send us the situation. If it is not something we should take on, we will say so.

The Plant-Side Brief

The weekly brief for the people who own a plant’s control systems.

One email every Wednesday for engineering and operations leaders responsible for controls, SCADA, MES and OT networks. Skim the top in two minutes; read the Deep Dive when you have fifteen.

  • One modernization problem, worked through to cost, risk and a schedule you can defend. The Deep Dive.
  • End-of-support dates before they reach your plant Windows, servers, controllers and HMI software. Lifecycle Watch.
  • A checklist your engineers can run that week not a framework to admire. Field Kit.
  • Every number sourced, no vendor agenda we are paid by plants, never by vendors.