Book a consultation

HiveMQ

HiveMQ Alternatives: EMQX, Mosquitto, AWS IoT Core and More Compared

HiveMQ alternatives compared on licence, clustering, MQTT 5 and Sparkplug status: EMQX, Mosquitto, VerneMQ, NanoMQ, Chariot, AWS, Azure and Solace.

Vladimir Romanov


HiveMQ alternatives fall into four groups: open-source brokers you run yourself (Eclipse Mosquitto, VerneMQ, NanoMQ), commercial brokers with a different licence model (EMQX, Cirrus Link Chariot, Coreflux), managed cloud services (AWS IoT Core, Azure Event Grid MQTT broker) and enterprise event brokers that speak MQTT among other protocols (Solace). None replaces HiveMQ in every role. The choice turns on three questions: would a broker outage stop a whole site, does Sparkplug state handling matter, and who will operate the broker for ten years. This page compares the options on the same dimensions as of 20 November 2026. It sits under the HiveMQ technology hub, and the vendor’s own market position is on the HiveMQ competitors page.

HiveMQ alternatives compared on the same dimensions

Every row answers the same six questions. HiveMQ is first as the reference. Facts come from each vendor’s documentation, the Eclipse Foundation and the sources listed at the foot of the page.

ProductLicenceDeploymentClusteringMQTT 5Sparkplug (Eclipse list)Where it fits
HiveMQ (reference)Community Edition under Apache 2.0; commercial plans for the Enterprise brokerSelf-managed, HiveMQ Cloud, Edge gatewayMasterless cluster in the Enterprise broker; none in Community Edition per HiveMQ staff in its forumYes, with 3.1 and 3.1.1Listed: Community, Professional, Sparkplug Aware ExtensionPlant and enterprise namespace with Sparkplug
EMQXBusiness Source License 1.1 from version 5.9Self-managed, EMQX Cloud, NanoMQ at the edgeMasterless cluster; multi-node production needs a commercial licenceYes, with 3.1 and 3.1.1Not listedVery large connection counts, rule-based routing
Eclipse Mosquitto and Cedalo Pro MosquittoEPL/EDL; Pro Mosquitto is commercialSelf-managed, small footprintNone in open source; Cedalo sells high availability in Pro MosquittoYes, with 3.1 and 3.1.1Not listedOne cell or line, gateways, labs
VerneMQApache 2.0 per its GitHub README; commercial support and custom releases offeredSelf-managedCluster support per its README; whether masterless is not confirmedYes, with 3.1, 3.1.1 and 5.0Not listedTeams that run Erlang and want Apache-licensed source
NanoMQMITEdge and gatewayNot confirmed; its README mentions a QUIC bridgeYes, with 3.1, 3.1.1 and 5.0 (Auth and server redirection unsupported)ListedPlant-edge broker that bridges upstream
Cirrus Link ChariotCommercialSelf-managed and as a cloud serviceNot confirmed3.1.1 per its documentation; 5 not confirmedListed: Server, Distributor, Engine, TransmissionIgnition-centred plants
CorefluxCommercial; free Community plan for non-production use, Growth from $205 per month billed annually, per its siteBroker with in-broker scriptingHA and clustering on the Enterprise plan, per its siteNot stated on its home pageNot listed; a Sparkplug B connector per its siteUNS builders who want logic in the broker
AWS IoT CoreProprietary, pay per useAWS-managed onlyManaged3.1.1 and 5 with documented differences, QoS 0 and 1 onlyNot listed; no AWS statement foundDevice fleets and cloud analytics on AWS
Azure Event Grid MQTT brokerProprietary, managedAzure-managed; a separate broker runs in Azure IoT Operations at the edgeManagedYes, QoS 0 and 1 onlyNot listed; one Microsoft post claims native supportAzure-centred estates
SolaceCommercialSelf-managed and Solace CloudEvent mesh across brokersYes, with 3.1.1Not listed; a 2023 community test reported a passMany sites and non-MQTT enterprise consumers

How to read the Sparkplug column. The Eclipse list had 20 products on 20 November 2026 and shows no version or date per product. Listed means the vendor completed the Eclipse compatibility process. Not listed means no evidence on that list, not that the broker fails. A Sparkplug design that depends on retained STATE messages and ordered birth messages should be tested against the real host application, whatever the list says. The HiveMQ Sparkplug page covers what the listing contains.

Adjacent stacks and services that ended

Two stacks are often named beside brokers without being brokers, and two services are lessons rather than options.

NameWhat it isWhy it is not a like-for-like option
United Manufacturing HubOpen-source UNS stack with Kubernetes, MQTT, Kafka and a time-series database; a lighter single-container core existsA bundle that includes broker functions; you adopt its data model as well
LitmusCommercial industrial edge data platform; its UNS documentation describes a Litmus MQTT brokerA data platform first; where the broker runs is not stated in the pages we read
Google Cloud IoT CoreManaged MQTT endpoint, retired 16 August 2023No longer available
Confluent MQTT ProxyKafka-side MQTT proxy, deprecated from Confluent Platform 7.9Confluent recommends connectors with a real broker instead

What the table does not show

The paid line moves, so ask which feature sits behind it. HiveMQ, Cedalo and EMQX all follow an open-core pattern: an open broker, with clustering and integrations on the commercial side. HiveMQ Community Edition has no clustering; open-source Mosquitto has none; EMQX allows single-node production use free and requires a commercial licence for more than one node, according to the EMQX licence FAQ. A high-availability pair counts as a cluster in that reading. Our reading of the pattern is that the useful question is never open against closed, but what you need that the free tier lacks.

Managed services differ from the specification. AWS IoT Core and Azure Event Grid both support QoS 0 and 1 only, and AWS documents further differences in its MQTT developer guide. That matters less for telemetry than for a Sparkplug namespace. The HiveMQ vs AWS IoT Core page works through it.

Enterprise brokers answer a different question. Solace and Kafka-based paths link sites and non-MQTT systems. The Solace vs HiveMQ page covers that pair, and the event broker comparison places every family on one map.

Single-node brokers have their place. The HiveMQ vs Mosquitto page covers the free end, and HiveMQ vs EMQX covers the nearest commercial rival.

Wall rack holding saws, planes, chisels and screwdrivers in neat rows
A broker is a tool chosen for a job: the rack is full, and the question is which one fits the work in front of you.

Two lessons from services that went away

Google Cloud IoT Core. Google announced the retirement in August 2022, as TechCrunch reported at the announcement, and Google’s services summary of July 2023 gave 16 August 2023 as the discontinuation date. Google pointed customers to its network of partners, without naming them in that report. The lesson is dependency on a protocol endpoint that a vendor can retire, not a verdict on cloud brokers.

Confluent MQTT Proxy. Confluent’s documentation lists the proxy as deprecated from Confluent Platform 7.9 and recommends the MQTT source and sink connectors with a real broker. Our reading: a proxy that makes Kafka look like a broker saves a component until the day it is withdrawn. The Kafka vs MQTT page explains why the two are normally paired.

HiveMQ has its own version of the lesson. HiveMQ’s documentation states that HiveMQ Cloud Serverless retires on 31 December 2026. That is a vendor-managed tier, not the broker, and a free migration licence for the self-managed Enterprise broker is offered to affected users. We found no second source for the date. See cloud vs self-hosted.

How to choose among HiveMQ alternatives

The tree below follows the questions in the order that removes options fastest. It is our method, not a vendor’s, and it ends at a short list, not a winner.

Decision tree for choosing among HiveMQ alternatives A decision tree with four questions. First, would a broker outage stop a whole site's data flow. If no, a single node is enough: Mosquitto, NanoMQ, HiveMQ Community Edition or EMQX on one node. If yes, ask whether the broker must run on your own network or support QoS 2. If not, a managed cloud broker such as AWS IoT Core or Azure Event Grid fits, after checking QoS and retained-message limits. If yes, ask whether Sparkplug state handling matters. If yes, prefer Eclipse-listed brokers: HiveMQ, Chariot and NanoMQ, and test any other with the Sparkplug test kit. If no, choose a clustered self-managed broker: HiveMQ, EMQX with a licence, VerneMQ, Pro Mosquitto or Coreflux. A separate final box notes that where many sites and non-MQTT enterprise consumers exist, a mesh or Kafka layer goes above the plant brokers. Which broker family: four questions, in order Would a broker outage stop a whole site's data flow? No Yes A single node is enough Mosquitto, NanoMQ, HiveMQ Community Edition, EMQX on one node Must it run on your own network, or support QoS 2? No Managed cloud broker AWS IoT Core, Azure Event Grid MQTT. Check QoS and retained-message limits Yes Does Sparkplug state handling matter? No Clustered, self-managed HiveMQ, EMQX (licensed), VerneMQ, Pro Mosquitto, Coreflux Yes Prefer Eclipse-listed HiveMQ, Chariot, NanoMQ. Test any other with the Sparkplug test kit Then, across sites Many plants, or enterprise consumers beyond MQTT? Add a mesh or Kafka layer above the plant brokers (Solace, Kafka). The plant brokers stay.
Outage impact and runtime location remove most options before features are compared. Sparkplug evidence then narrows the clustered list; cross-site needs are a separate layer, not a reason to replace the plant broker.

Each answer is a short list, not a decision. Write the requirement down, then test the short list against a real publisher and a real consumer.

  1. Failure domain. If a restart that drops clients for a minute is acceptable and they republish on reconnect, a single node is cheaper to run and easier to understand.
  2. Where it runs. Plant traffic that must keep flowing when the WAN fails belongs on a broker inside the plant. Managed services fit when the data is already headed to that cloud.
  3. Evidence for Sparkplug. Use the Eclipse list as a starting point and a pilot with your own host application as the test.
  4. Operations. Who patches, monitors and upgrades the broker over ten years, and what does the licence allow them to run?

How a broker migration fails

Because MQTT clients are standard, moving between brokers is cheaper than leaving a platform. The failures come from state the clients do not carry. These are our field-pattern view, not sourced incidents.

  • Retained messages are not there. A new broker starts with no last-known values. A tank level published only on change may not republish for hours, so consumers see nothing. Plan a forced republish at cutover.
  • Persistent sessions start clean. Messages queued for offline subscribers on the old broker do not move with them.
  • Sparkplug state is lost. Host applications and edge nodes need to rebirth against the new broker, and Last Will behaviour has to match what the host expects. Test with the real host.
  • Access rules do not export. Roles, users and topic permissions are product-specific, and a wildcard that was narrow on one broker can be wide on another.
  • Specification differences surface late. QoS 2, shared subscriptions, topic aliases and message ordering are not uniform across brokers and managed services.
  • Onward integrations are rewritten. Extensions, rule engines and data policies that feed Kafka or databases do not port between products.
  • Parallel running creates loops. Two brokers bridged in both directions on overlapping topics duplicate traffic. Use a topic prefix per direction, as the edge-to-cloud bridging page describes.

Illustrative: a packaging line moves its UNS from a single Mosquitto process to a clustered broker over a weekend. Every publisher reconnects within seconds, but the filler’s state topic is retained and publishes on change, and the filler has been running steadily since Friday. Monday’s dashboards show the line as unknown until someone restarts the publisher. A cutover step that triggers a republish removes the problem.

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.

  • Requirement first: writing the failure domain, Sparkplug, security and operations requirements before any product is named.
  • Short-list testing: a pilot with a real publisher and host application, covering retained messages, Last Will and reconnect behaviour.
  • Migration runbooks: parallel running, forced republish, bridge loop prevention and a rollback step.
  • Placement: where the broker sits relative to the OT network zones, as set out in OT network segmentation and ISA/IEC 62443.
  • Support: IT/OT integration and an independent owner’s engineer view where a vendor selection is under way.

Limits and open questions

  • The Eclipse list is self-certification. It shows no version or date, and we did not run the test kit against any broker.
  • No benchmarks. We did not compare throughput or latency; vendor figures are the vendors’ own.
  • Gaps in the facts. Chariot’s clustering and MQTT 5 status, Coreflux’s licence terms, and VerneMQ’s current release activity were not confirmed from primary sources.
  • Pricing. HiveMQ’s plans are on its pricing page as listed on 20 November 2026. We did not compare other vendors’ prices.
  • Ownership. We found no acquisition of HiveMQ, EMQ, Cedalo or Cirrus Link as of 20 November 2026, which does not prove none occurred.
  • Security records. Every long-lived broker has advisories. A count of them is not a ranking, so we do not compare counts.

Check each vendor’s current documentation and ask for written answers on any item above before you rely on it.

Deeper

Across to a sibling: HiveMQ in manufacturing. Back to the HiveMQ hub, or read about the company behind it.

Frequently asked questions

What are the main alternatives to HiveMQ?

For a plant or enterprise MQTT broker the realistic alternatives are EMQX, Eclipse Mosquitto (with Cedalo's Pro Mosquitto), VerneMQ, NanoMQ at the edge, Cirrus Link Chariot, Coreflux, and the managed services AWS IoT Core and Azure Event Grid. Solace is an enterprise event broker that also speaks MQTT. The right one depends on clustering need, Sparkplug evidence and who operates it.

Which alternatives to HiveMQ are on the Eclipse Sparkplug compatible list?

On the list fetched on 20 November 2026, the broker products are Cirrus Link Chariot, NanoMQ, two SIOTH brokers and HiveMQ itself. EMQX, Mosquitto, VerneMQ, AWS IoT Core, Azure Event Grid and Solace are not listed. Not listed does not mean a broker cannot carry Sparkplug traffic, so test the behaviour you need.

Is a managed cloud broker a good replacement for HiveMQ in a plant?

Sometimes. AWS IoT Core and Azure Event Grid support QoS 0 and 1 only, which suits most telemetry, and they remove broker patching. They sit across the WAN from the plant, differ from the MQTT specification in documented ways, and tie you to one cloud. Many plants keep a broker on site and send selected topics to the cloud service.

Is Mosquitto enough for a unified namespace?

For one cell or line, yes. The open-source Mosquitto broker is a single process with no clustering, so a restart or failure stops the data flow until clients reconnect. A site-wide namespace that many systems depend on usually needs a clustered broker or a plan for fast recovery. Cedalo sells a high-availability Pro Mosquitto for that case.

How hard is it to switch MQTT brokers?

Standard MQTT clients connect to any compliant broker, so switching is cheaper than leaving a platform. The work is in what clients do not carry: retained messages, persistent sessions, access rules, Sparkplug state, bridges and the extensions or rule engines that move data onward. Plan a parallel run and test the retained-message and rebirth behaviour.

References and further reading

  1. Sparkplug Compatible Software · Eclipse FoundationThe list used for every Sparkplug status in this page.
  2. EMQX License FAQ · EMQ TechnologiesSingle-node and multi-node terms under the Business Source License 1.1.
  3. AWS IoT Core MQTT developer guide · Amazon Web ServicesThe documented differences from the MQTT specification.
  4. Azure Event Grid MQTT support · Microsoft
  5. Eclipse Mosquitto 2.1.0 released · Eclipse Mosquitto
  6. Confluent MQTT Proxy · ConfluentThe deprecation notice and the recommended connector approach.
  7. Google Cloud will shutter its IoT Core service next year · TechCrunch
  8. Google Cloud Platform Services Summary (July 2023) · Google CloudGives 16 August 2023 as the Cloud IoT Core discontinuation date.
  9. HiveMQ pricing · HiveMQPlans as listed on 20 November 2026.

← 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.