HiveMQ
HiveMQ Platform: The Broker, the 2026 Suite and the Editions
The HiveMQ Platform explained: the MQTT broker, the September 2026 suite (Connect, Contextualize, Analyze, Act), editions compared and how it fails.
The HiveMQ Platform is, at its core, an MQTT broker written in Java that plant systems, gateways and enterprise applications publish to and subscribe from. Since 9 September 2026 the same name also covers a four-layer suite built around that broker. This page separates the two meanings, shows how the pieces fit, compares the editions, and says where we expect a deployment to hurt. For the vendor as a whole, start at the HiveMQ technology hub.
What the HiveMQ Platform is: the broker and the suite
The broker. HiveMQ’s user guide describes the Enterprise MQTT Broker as supporting MQTT 3.1, 3.1.1 and 5.0, with QoS 0 to QoS 2, retained messages, persistent sessions, last will, shared subscriptions and session and message expiry. Listeners are TCP, TLS, WebSocket and secure WebSocket. It runs as a masterless cluster, so a single node and a multi-node deployment are the same product. HiveMQ also describes it as Sparkplug compatible; the Sparkplug page covers what that means in practice.
The suite. HiveMQ’s 9 September 2026 announcement describes four layers, and its documentation adds a fifth layer, Explore, which it describes as the home page of the platform, plus an AI assistant called Bea:
- Connect moves data: the broker, the Edge gateway, bridges, security and the Enterprise Extensions.
- Contextualize adds discovery and cataloguing, semantic modelling against ISA-95, and data governance.
- Analyze is the analytics layer on the same data.
- Act is agentic AI for operations. HiveMQ’s documentation calls it a public preview.
- Bea is, in the platform documentation’s words, a context-aware AI assistant built into every page of the platform, with an Ask Bea option for configuration help. The Act overview also points to building an agent with Bea.
Two things are not settled in what HiveMQ has published. HiveMQ announced Pulse, a distributed data intelligence product, as a private preview on 18 February 2025. A release of the Platform Operator on 21 October 2026 says Helm values for “HiveMQ Data Intelligence” replace the Pulse values. We have not found a statement that says how Pulse maps onto Contextualize and Analyze, so we do not claim one. The Pulse and 2026 suite page tracks that question.
HiveMQ Platform architecture at a glance
The figure shows where the broker sits. Devices and gateways connect at the bottom, the broker cluster holds the namespace in the middle, and the suite layers read from it.
The practical consequence is that the broker is the part to size and operate carefully. HiveMQ’s documentation shows the suite in one console, but each layer has its own overview page and its own maturity, so evaluate them separately and do not let a preview layer set the schedule for a production broker. Contextualize, Analyze and Act are consumers of what it holds. If you only need a broker, Connect is the product; the other layers are optional. The gateway side of Connect is covered on the HiveMQ Edge page.

HiveMQ Platform editions compared
HiveMQ’s pricing page, as listed on 21 November 2026, shows self-managed plans by connection and throughput caps rather than by message count. Community Edition and Cloud are separate products. This table is a summary; the editions and pricing page has the detail and the arithmetic caveats.
| Edition | Listed price (21 Nov 2026) | Connections | Throughput cap | Support |
|---|---|---|---|---|
| Community Edition (Apache 2.0) | Free | Not capped by licence | None stated | Community |
| Lab (self-managed) | Free, 30-day licence | 25 | 25 messages per second | Community |
| Launch (self-managed) | $299 per month | 10,000 | 500 messages per second | Community |
| Run (self-managed) | $499 per month | 10,000 | 1,000 messages per second | Silver |
| Enterprise (self-managed) | Custom quote | Custom | Custom | Silver to Platinum |
| Cloud Starter | From $0.34 per hour plus $0.80 per million messages | 10,000 | 1 MB per second | Silver |
HiveMQ states that all self-managed plans include TLS, authentication, authorization, the Enterprise Extensions and in-stream data governance. Throughput on the pricing page is normalised to 5 KB messages. We have not confirmed whether Enterprise is still priced by connection. The Cloud page covers the managed option, including HiveMQ’s statement that Cloud Serverless retires on 31 December 2026.
How the HiveMQ Platform is selected
HiveMQ is rarely chosen alone; it is chosen against a short list. The questions that decide it, in the order we ask them:
- How many persistent clients and how much message volume? The throughput caps above are the first filter. A Mosquitto-class broker may be enough for a single line; see HiveMQ vs Mosquitto.
- Does the namespace need to survive a node loss without an operator? That is a cluster requirement, and it pulls the choice toward a clustered broker.
- Who runs it? Managed Cloud, Kubernetes with the Platform Operator, or a ZIP on a plant server are different operating burdens.
- Which integrations are required? Kafka, enterprise security and data policy are Enterprise Extensions, not Community Edition features.
- How many sites? HiveMQ documents bridging as the multi-site tool. The multi-site architecture page goes further.
For the wider choice among event brokers, see the event broker comparison and the UNS broker page.
How a HiveMQ Platform deployment fails
HiveMQ documents recovery steps and overload behaviour; it does not publish a catalogue of field failures. The list below is our view, built from general broker operations and from what the documentation describes.
- Cluster sized for the average, not the reconnect storm. After a network event, every client reconnects at once and resubscribes. A cluster that handles steady state can still fall over here. HiveMQ’s documentation says the broker applies overload protection, which we cover below.
- Retained messages that only grow. A Unified Namespace uses retained messages heavily, and a topic nobody clears stays forever. HiveMQ’s sources we read did not size retained-message storage, so measure it. Sparkplug Aware mode adds further retained messages.
- Overload protection engaging. HiveMQ states each client has a credit budget of 100, and at zero the broker stops reading that client’s TCP socket. A client that appears slow or silent may be throttled on purpose. Tune the clients before you disable the protection, which HiveMQ advises against.
- Java and upgrade discipline. The minimum Java is 21. With monthly releases, a plant that upgrades once a year falls behind the supported line quickly. Plan a rolling upgrade, one node at a time.
- Discovery that works in the lab and not in production. HiveMQ’s cluster guide says the minimal cluster configuration “is only recommended for testing purposes in local networks” and that “UDP transport is not suitable for production environments”.
HiveMQ Platform lifecycle and licensing
The table below lists the releases that matter on 21 November 2026.
HiveMQ ships one minor broker release per month, normally in the first week, with maintenance builds the same day. As of 21 November 2026 the current release is 4.57 (3 November 2026). Version 4.55 (1 September 2026) is the long term support release; HiveMQ’s guidance is a new LTS about every 18 months. Support for 4.28.x continues through February 2027, per HiveMQ’s changelog. A breaking change appeared as recently as 4.57, where $client-events payload fields were renamed to camelCase, so read release notes even for a minor upgrade.
| Release | Date | Role |
|---|---|---|
| 4.57 | 3 November 2026 | Current monthly release |
| 4.56 | 29 September 2026 | Monthly release |
| 4.55 | 1 September 2026 | Current LTS; Java 21 remains the minimum, Java 25 supported, Control Center v1 removed |
| 4.28.x | Maintenance builds monthly | Previous LTS, supported through February 2027 |
The choice between LTS and monthly is a change-control question. A plant that validates software once a year belongs on the LTS line; a team that can regression-test every month gets new features sooner. In our view, pick one line deliberately and write down who reads each release note, because a release can remove an interface, as 4.55 did with Control Center v1.
Licensing for the self-managed broker is by plan as in the table above. Community Edition is Apache 2.0, with the GitHub page pointing to version 2026.6 on 21 November 2026.
What we do here
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.
In practice, when a HiveMQ broker is on the table, we would:
- Size the broker from a client and topic inventory, not from the vendor’s connection caps alone.
- Ask for a failure test plan: node loss, network split and a full reconnect.
- Review the topic and retained-message design before it is built. Our MQTT in manufacturing guide and Unified Namespace guide set out the principles.
- Check where the broker sits in the OT network. See OT networks.
Limits and open questions
- Pulse and the suite. How the 2025 Pulse preview maps onto Contextualize and Analyze is not stated in sources we read.
- Act is a preview; its production readiness is unproven.
- Retained-message sizing and the persistence engine are not documented in the pages we read.
- Enterprise licence unit is a quote, so we cannot say what it is priced on.
- Prices are as listed on 21 November 2026 and change.
Deeper
- Clustering and high availability: replicas, node loss and overload.
- Deployment and Kubernetes: ZIP, Docker and the Platform Operator.
- Editions and pricing: the plans in detail.
- Sibling: HiveMQ Cloud, the managed option.
Frequently asked questions
What is the HiveMQ Platform?
Two things share the name. HiveMQ's documentation uses it for the Java MQTT broker that supports MQTT 3.1, 3.1.1 and 5.0. On 9 September 2026 HiveMQ also launched a suite called the HiveMQ Platform, with four layers named Connect, Contextualize, Analyze and Act. The platform documentation, not the launch release, also names an assistant called Bea. Connect is the broker. The other layers sit on top of it.
Is HiveMQ Act generally available?
No. HiveMQ's documentation and pricing page describe Act, the agentic AI layer for operations, as a public preview as of 21 November 2026. Connect, Contextualize and Analyze are described as available. Treat Act as something to evaluate, not as a production dependency, until HiveMQ announces general availability.
Which HiveMQ release is the long term support version?
HiveMQ 4.55, released on 1 September 2026, is the current long term support release and replaced 4.28. HiveMQ's changelog says 4.28.x support continues for six months after that release, through February 2027. The current monthly release is 4.57, released on 3 November 2026.
Does HiveMQ cluster the way a database does?
HiveMQ describes a masterless cluster in which every node is equal and persistent data is replicated, with a default replica count of 2. There is no primary node to fail over from. The cluster acts as one logical broker to MQTT clients. The details of loss and recovery are on the clustering page.
Which Java version does HiveMQ need?
HiveMQ's 4.55 release notes say the system requirements remain on Java 21 as the minimum, and that Java 25 is supported and recommended. Check this before an upgrade, because the Java runtime on a plant server is often older than the broker requires.
References and further reading
- HiveMQ launches new HiveMQ Platform · HiveMQThe 9 September 2026 announcement of the four layers.
- HiveMQ Platform documentation · HiveMQThe console, the Bea assistant and the layer overviews.
- HiveMQ Enterprise MQTT Broker user guide · HiveMQProtocol support, listeners, deployment and monitoring.
- HiveMQ cluster documentation · HiveMQ
- HiveMQ overload protection · HiveMQ
- HiveMQ pricing · HiveMQPlans and limits as listed on 21 November 2026.
- What's new in HiveMQ 4.55 · HiveMQThe LTS release, the Java 21 minimum and Java 25 support.
- What's new in HiveMQ 4.57 · HiveMQ
- Managing HiveMQ releases and support · HiveMQThe LTS and monthly release policy.
- HiveMQ Act overview · HiveMQ