HiveMQ
HiveMQ Strategy: From MQTT Broker to Industrial AI Platform
HiveMQ strategy read in two columns: what the company states about its Industrial AI pivot, open core, cloud and partners, and what we read in it.
HiveMQ strategy has moved in three dated steps: an MQTT broker company, then, from 16 October 2025, an “Industrial AI Platform”, then, on 9 September 2026, “the industrial data platform for agentic AI”. This page keeps the company’s words and our reading apart. In the table below the left column is what HiveMQ states, attributed and dated, and the right column is our read, marked as ours. It is aimed at a plant or an architecture team deciding whether to buy a broker from a vendor that now sells much more than a broker. For the company itself, see the HiveMQ company profile; for the products, the HiveMQ technology hub. Joltek is independent of HiveMQ and has no commercial relationship with it.
HiveMQ strategy: what it states and what we read
Every entry on the left comes from a HiveMQ release, blog post, documentation page or its pricing page, dated. HiveMQ is private and publishes no revenue, so we cannot test any of its growth statements against accounts. The right column is judgement, not fact.
| Topic | HiveMQ states | Our read |
|---|---|---|
| Positioning | On 16 October 2025 HiveMQ announced a “Strategic Shift to Become Leading Industrial AI Platform”, with its platform “embedding intelligence and action directly into real-time data streams”. On 9 September 2026 it launched the HiveMQ Platform as “the industrial data platform for agentic AI” | The broker’s job has not changed. What is new is a layer of governed data and AI workflows above it, sold to the same buyers. Read each release for which parts are shipping and which are announced |
| The four layers | The September 2026 release describes Connect, Contextualize, Analyze and Act, and says the platform is available today with a free start. HiveMQ’s documentation and pricing page label Act a public preview | Connect is the broker and the part with a decade of field history. Act in preview is a direction, not a reason to choose a broker today |
| Open core | The Community Edition is Apache 2.0 on GitHub, and the commercial editions are built on it. HiveMQ Edge is Apache 2.0 with commercial features behind a licence key | The line between free and paid is where plants live. Find which feature you need, such as clustering or the enterprise extensions, and ask whether it sits behind the line |
| Cloud | HiveMQ’s pricing page lists Starter and Enterprise for Cloud as of 20 November 2026. Its documentation states that Serverless retires on 31 December 2026 | A managed endpoint can be retired by its vendor. Ask what notice and what migration path the contract gives you |
| Sparkplug and UNS | HiveMQ lists a Sparkplug Aware Extension, and its Community and Professional editions appear on the Eclipse Sparkplug compatible list as fetched on 20 November 2026. Its representative is named as a delegate in the Steering Committee minutes of 4 June 2026 | Standards work and a compatibility listing are the strongest evidence in this table, because a third party holds the list. Unified Namespace content is also how HiveMQ reaches plant teams |
| US focus | The 4 May 2022 Series A release states that more than 50 percent of revenue came from US-based companies. The 8 August 2023 release opens a Boston office and states that the US accounts for 60 percent of revenues | Sales and executive weight sit in the US. For a plant elsewhere, ask where support is staffed and in which hours |
| Partners | A 16 March 2026 blog announces the HiveMQ Partner Network with three tiers: Authorized, Premier and Elite | A programme gives integrators a route to HiveMQ. A tier is not evidence that a given partner has delivered a plant like yours |
| Ignition | On 23 July 2025 HiveMQ announced it joined the Inductive Automation Ignition Technology Ecosystem Program as a technology partner. The release makes no Sparkplug or module claim | Membership signals that Ignition plants are a target. Test the Ignition and broker combination on your own site rather than reading it from the announcement |

How the HiveMQ strategy moved over time
The diagram sets HiveMQ’s own self-description at each date against what it launched. We chose the dated sources for each step, and the descriptions are the company’s wording or a close paraphrase.
The Industrial AI pivot: what HiveMQ states
HiveMQ states the rationale in the 16 October 2025 release: embed intelligence and action directly into real-time data streams, to help customers move from AI pilots to real production outcomes, with HiveMQ Pulse structuring and validating the data. The release appointed Barry Libert as Chairman and CEO. It also cites an IoT Analytics market estimate, which we do not repeat because estimates of this kind disagree.
On 9 September 2026 HiveMQ launched the HiveMQ Platform as “the industrial data platform for agentic AI”. The release defines the layers in a sentence each. Connect creates a secure real-time backbone across OT and IT systems, from edge to cloud. Contextualize defines data models and governance once and applies them consistently. Analyze calculates trusted KPIs close to the source and surfaces deviations while operations are running. Act puts trusted intelligence into governed, human-supervised workflows. HiveMQ’s chief technology officer is quoted as saying manufacturers will not jump from dashboards to autonomous operations overnight, and that the platform offers a governed path with people in control at every step.
Pulse needs a careful sentence. HiveMQ announced it on 18 February 2025 as a private preview, described as a distributed data intelligence platform focused on the Unified Namespace. HiveMQ’s current Pulse product page places it under Contextualize but gives no status or date, so we cannot confirm from sources whether Pulse was renamed into the suite or continues as a separate product. Our Pulse and the 2026 suite page tracks it.
Our read on the Industrial AI pivot for a plant buying a broker
In our view the pivot is a change of what is sold, not of what a broker does. An MQTT broker moves messages between publishers and subscribers. Nothing in the September 2026 release changes that. The value HiveMQ now describes sits in naming, modelling and governing the data that crosses the broker, and in running agents on it. Those are real needs. They are also products with their own maturity, and the one furthest from production, Act, is labelled a public preview.
A vendor that wants the data platform may price the broker as a door. We read the free start and the self-serve plans on the pricing page as a way to get a broker in place and then sell the layers above. That is a normal software model and not a criticism. It means a plant should price the broker on its own and then price each layer it will actually use. The editions and pricing page lists the plans as published on 20 November 2026.
Lock-in moves up the stack. MQTT clients are standard, so changing the broker is relatively cheap. Data models, governance rules and agent definitions held in a vendor platform are not standard, and moving them costs more than moving the broker. If you adopt Contextualize or Act, keep the models and rules exportable and documented in your own repository.
Write down the commitments you need. The direction changed twice in twelve months, so ask for the broker’s long-term support policy in writing rather than relying on a pitch.
HiveMQ strategy on open core and cloud
HiveMQ states that its open-source footprint is the base of its products. The 2019 launch release said the commercial editions are built on the open-source Community Edition, and the GitHub organisation shows the Community Edition, the Java MQTT client and HiveMQ Edge under Apache 2.0. Edge is a gateway that converts industrial protocols to MQTT. Its documentation says the packaged product mixes open-source and commercial features, and that commercial features, including Data Hub on Edge, need a licence key.
We read this as open core, the common shape for brokers. EMQX, Cedalo and HiveMQ all give away a single broker and charge for more, but the paid line differs: HiveMQ staff say Community Edition has no clustering, EMQX 5.9 and later needs a commercial licence for production clusters, and Cedalo sells high availability on top of Mosquitto. The competitors page compares them. The practical test is concrete. Make a list of the features your design needs, then mark which are in the free edition. A plant running one broker per line with clients that republish after a reconnect may stay on the free edition. A plant that needs a clustered site broker will not.
The Serverless retirement is the cleanest example of cloud strategy in the sources. HiveMQ’s Cloud documentation states that Serverless retires on 31 December 2026, that clients cannot connect after that date, that clusters and data are deleted, and that affected users can claim a free migration licence for the self-managed Enterprise Broker. We found that date in HiveMQ’s documentation only, not in a second source, so verify it with HiveMQ if it affects you. The pricing page as of 20 November 2026 lists Cloud as Starter, from $0.34 per hour plus $0.80 per million messages, and Enterprise. Our read is that HiveMQ is narrowing Cloud to two offers, with the cheapest tier now a paid one. The cloud versus self-hosted page covers the choice.
HiveMQ strategy on the US, partners and Ignition
HiveMQ’s statements put weight on the United States. The table lists each growth statement with its release date, because the releases give the date and not always the year the figure describes. We found no revenue figure, no headcount and no customer count after 2022 on HiveMQ’s site, which fits a private company.
| Release date | HiveMQ states | How we use it |
|---|---|---|
| 4 May 2022 | More than 50 percent of revenue from US-based companies; over 130 customers | Dated to the release, as a 2022 statement |
| 8 August 2023 | Total revenues doubling year over year; the US now accounts for 60 percent of revenues; a new Boston office | Quoted as the release’s sentence, not assigned to a fiscal year |
| 16 October 2025 | Datelined Boston and Munich | A leadership and market statement, no figures |
| 9 September 2026 | Datelined Boston and Berlin; MQTT used for more than 12 years; named customers Audi, BMW, Mercedes-Benz, Siemens, Liberty Global and Eli Lilly | Customer names are HiveMQ’s claims, with no count |
The partner network is the channel layer. The 16 March 2026 post names three tiers, Authorized, Premier and Elite, and describes them as core foundation, demonstrated commitment and strategic alignment. In our view a three-tier programme is how a vendor with a modest direct sales team scales through integrators. The question for a buyer is whether the integrator you would hire has delivered a HiveMQ system of your size, and that is a reference call, not a tier.
On Ignition, the 23 July 2025 release says HiveMQ joined the Inductive Automation ecosystem to bring real-time industrial intelligence to Ignition users. Many plants run Ignition as their SCADA, so this is a sensible audience. The release does not claim a module or Sparkplug certification. See the Sparkplug page for what the Eclipse list shows and our funding and ownership page for how the company is financed.
Questions to ask HiveMQ before you commit
These are our questions, not HiveMQ’s claims, and they apply to any broker vendor with a platform strategy.
- Which parts of the platform are generally available today, and which are preview? Get the status in writing for each layer you plan to use.
- If we use only the broker, what is the price, and does any feature we need move behind a platform licence?
- Which features of Data Hub, Contextualize and Act are exportable, and in what format, if we leave?
- What is the support commitment for the long-term-support broker release we choose, and for how many years?
- Where is support staffed, in which time zones, and which partner supports our region?
- For Cloud: what notice and migration path apply if a plan is retired, as Serverless is being retired?
- For Sparkplug and Ignition: can you show a reference plant of our size running the combination we plan?
Where Joltek stands on HiveMQ strategy
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. Our modernization roadmap service helps plants decide which layers of a data platform to buy and which to build, and the MQTT in manufacturing guide explains the protocol underneath. If you want a second opinion on a HiveMQ proposal, contact us.
Frequently asked questions
What is the HiveMQ strategy?
HiveMQ states that it is moving from an MQTT broker company to an industrial data platform for AI. A 16 October 2025 release called it an Industrial AI Platform, and a 9 September 2026 release launched the HiveMQ Platform as the industrial data platform for agentic AI, in four layers: Connect, Contextualize, Analyze and Act. The MQTT broker remains the base layer.
Is HiveMQ still an MQTT broker company?
Yes, on the evidence of its own releases. The September 2026 launch describes the platform as built on MQTT, which it calls mission-critical for more than 12 years. The broker is the Connect layer. What has changed is the pitch: the company now sells governed data and AI workflows above the broker, so the broker is the entry point rather than the whole product.
Is HiveMQ open source?
Partly. HiveMQ Community Edition and the HiveMQ Edge gateway are published under the Apache 2.0 licence on GitHub. The commercial editions are built on that core and add features such as clustering and the enterprise extensions, and Edge has commercial features behind a licence key. This is an open-core model, so the useful question is which feature you need sits behind the paid line.
What is happening to HiveMQ Cloud Serverless?
HiveMQ's Cloud documentation states that HiveMQ Cloud Serverless retires on 31 December 2026. After that date clients cannot connect and clusters and data are deleted. The documentation offers affected users a free migration licence for the self-managed Enterprise Broker. HiveMQ's pricing page lists only Starter and Enterprise for Cloud as of 20 November 2026.
Should an AI strategy change how I choose an MQTT broker?
It should add questions, not replace the old ones. Test the broker on what you need today: MQTT version and QoS support, retained messages, clustering, Sparkplug behaviour and licence terms. Then ask which AI features are generally available rather than in preview, what they cost, and whether the broker works without them. Standard MQTT clients keep the exit path open.
References and further reading
- HiveMQ Announces Strategic Shift to Become Leading Industrial AI Platform (16 October 2025) · HiveMQThe Industrial AI Platform release, with the chief executive appointment.
- HiveMQ Launches New Platform (9 September 2026) · HiveMQThe four-layer platform and the agentic AI tagline.
- HiveMQ Series A funding announcement (4 May 2022) · HiveMQCustomer count and US revenue share as stated in 2022.
- The next chapter of HiveMQ (4 May 2022) · HiveMQHow the company described itself and its plans after the Series A.
- HiveMQ Accelerates Growth with New US Office and Expanded Leadership Team (8 August 2023) · HiveMQThe Boston office and the growth statements quoted here.
- Announcing the new HiveMQ Partner Network (16 March 2026) · HiveMQThe Authorized, Premier and Elite tiers.
- HiveMQ Joins Inductive Automation Ecosystem (23 July 2025) · HiveMQIgnition Technology Ecosystem membership.
- HiveMQ Cloud documentation · HiveMQThe Serverless retirement notice and the migration licence.
- HiveMQ pricing · HiveMQPlans as listed on 20 November 2026, including the Act preview label.
- HiveMQ Community Edition on GitHub · HiveMQApache 2.0 licence and release notes.
- Eclipse Sparkplug compatible software · Eclipse FoundationWhich brokers are listed as Sparkplug compatible.