Book a consultation

HiveMQ Unified Namespace: Edge, Plant Broker and Enterprise

HiveMQ Pulse and the 2026 Suite: What Is Confirmed

HiveMQ Pulse status in November 2026: the 2025 preview, the 2026 suite, the unconfirmed link between them, and what to ask before relying on it.

Vladimir Romanov


HiveMQ Pulse was announced on 18 February 2025 as a private preview, and as of 20 November 2026 we could not find a general availability announcement, a licence statement or a price. The page at HiveMQ’s Pulse product address now shows the Contextualize layer of the HiveMQ Platform, a suite announced on 9 September 2026, without naming Pulse; HiveMQ has not said how the two relate. The question for a plant is narrow: should the modelling and governance layer of a unified namespace be built on a product whose status the vendor has not published? This page sets out what is confirmed, what is inference, and what to ask. It continues from the HiveMQ unified namespace page in the HiveMQ cluster.

What HiveMQ Pulse was announced as

HiveMQ announced Pulse at the ProveIt! conference in Dallas on 18 February 2025 as a “distributed data intelligence platform” for managing, transforming, governing and analysing device and system data, with a focus on the unified namespace. The announcement said it was available in private preview by application. Its claims included cataloguing, transformation and governance, real-time insight, a calculation engine, AI and machine learning at the edge, and “AI readiness”.

The announcement describes Pulse as built on MQTT publish/subscribe architecture and never calls it a broker. In our view the claims it lists, cataloguing, transformation and governance, make it a modelling and governance layer, not a broker.

What shipped around it. HiveMQ Edge 2025.16 (1 October 2025) added a Pulse Agent that connects to Pulse with activation tokens. It also added “Pulse Assets”, which combine edge data sources into single MQTT payloads published northbound, and pushes assets created in Pulse to chosen Edge instances for mapping. That release needs Java 21 or higher.

HiveMQ Pulse in the September 2026 suite

HiveMQ announced the HiveMQ Platform on 9 September 2026 as “a single system for manufacturers to connect, contextualize, analyze and act on operational data in real time”. HiveMQ’s documentation shows a console with Explore, Connect, Contextualize, Analyze and Act areas, plus a context-aware assistant named Bea.

LayerWhat HiveMQ saysStatus as we read it
ConnectThe broker with TLS, authentication, authorisation and extensionsIncluded in all self-managed plans on the pricing page
ContextualizeDiscovery and cataloguing; semantic modelling and UNS against the ISA-95 hierarchy (sites, areas, lines, assets, signals, versioned); enterprise data governance with role-based access over models; streaming data governance with schema validation and classificationAn add-on with “free usage to start” per the pricing page; Pulse is not named on the page at its product address, and no general availability status is stated
AnalyzeDescribed as an add-onNot researched in detail
ActAgentic AI for operations: agents on real-time data, human oversight, agent-to-agent communicationPublic preview per the documentation and pricing page
BeaAssistant in every console page; in Act it drafts agent definitions from natural languageNot stated separately

The press release for the suite says it is “available today” and offers a free start. That does not settle whether Contextualize, and any Pulse capability inside it, is generally available, because the Act layer in the same suite is stated to be a preview and the Pulse page says nothing either way.

Is HiveMQ Pulse now Data Intelligence?

The rename is not confirmed. Two release notes point toward it. HiveMQ Platform Operator 2.3.0 (21 October 2026) says “The HiveMQ Data Intelligence values replace the HiveMQ Pulse values” in its Helm chart, and Edge 2026.16 (10 November 2026) updates a “Data Intelligence agent” to version 3.6.0. In our fetches, the old Pulse product and documentation addresses returned Platform pages that do not name Pulse, which we read as a hint of a redirect, not proof.

HiveMQ Pulse timeline from February 2025 to November 2026 Five dated events on a line, not to scale. 18 February 2025: Pulse announced as a private preview. 1 October 2025: Edge 2025.16 adds the Pulse Agent and Pulse Assets. 9 September 2026: the HiveMQ Platform suite launched, with Act in public preview. 21 October 2026: Operator 2.3.0 Helm values for Data Intelligence replace Pulse values. 10 November 2026: Edge 2026.16 updates a Data Intelligence agent. Pulse and Data Intelligence names both appear; no release states general availability or a rename 18 Feb 2025 Pulse announced as a private preview 1 Oct 2025 Edge 2025.16: Pulse Agent and Pulse Assets 9 Sep 2026 HiveMQ Platform suite; Act in public preview 21 Oct 2026 Operator 2.3.0: Data Intelligence replaces Pulse Helm values 10 Nov 2026 Edge 2026.16 updates a Data Intelligence agent Not to scale. Dates from HiveMQ releases, announcements and changelogs.
Pulse is announced, wired into Edge and then replaced by Data Intelligence names in Helm configuration values, with no step stating general availability or a rename. The names matter because automation that references one breaks when the other appears.

Our read: the likeliest explanation is one product lineage with a new name, but HiveMQ has not said so, and we do not either. If your Helm charts or Edge configurations reference either name, pin versions and read each release note.

A namespace that does not depend on HiveMQ Pulse

Everything a namespace needs to work is available without a modelling product. A broker holds the topics, HiveMQ Edge or a DataOps tool publishes into them, and Data Hub can check payloads against JSON Schema or Protobuf and transform them with JavaScript. The convention itself, meaning level names, units and ownership, can live in a controlled document and a schema repository. That is more manual than a catalogue with versioned models, and it needs discipline. In our view it is the safer base while the status of Pulse is unknown, because a preview product can then be added later, or dropped, without moving a single topic. The Data Hub page covers what the broker-side checks do and do not enforce.

What to ask before betting a unified namespace on a preview product

Softly blurred dashboard on a monitor showing a line chart and a grid of blue cells
A dashboard is the visible end of a model layer. If the model layer is a preview, the dashboards inherit its risk.

A namespace outlives the tools around it. These are the questions we would put to HiveMQ, and answer ourselves, before a plant makes Pulse, or whatever it is now called, a dependency.

  1. What is the general availability status of the component you will use, and in which document does HiveMQ say so?
  2. What are the licence terms and the price? The pricing page we read does not mention Pulse, and Contextualize is an add-on “with free usage to start” without limits we could find.
  3. What does support cover for a preview? Ask for the response commitments in writing.
  4. Where does the model live, and can you export it? An information model that exists only inside a vendor server is a lock-in, whatever the topics look like.
  5. If the product is removed, does the namespace keep working? Topics and payloads on the broker should stand alone. Test by switching the agent off on a bench.
  6. Which names will appear in configuration, and which will change? The Helm values change above is the example.
  7. What runs at the edge? The Pulse Agent in Edge 2025.16 needs Java 21 or higher, so plan version pinning.
  8. Where is the model server hosted, and what crosses the plant boundary? Deployment details are not on the product page. For OT networks, settle that before the pilot, with our OT network segmentation guidance as a reference.

Where it gets hard

  • Status is not published. Every decision above depends on facts HiveMQ has not put on the pages we read.
  • Preview creep. A pilot becomes production because dashboards depend on it. Decide the exit before the pilot.
  • Two namespaces again. A modelled namespace and the raw broker tree can diverge. Keep one authoritative source for the model, and put the convention in a document that predates the tool.
  • Vendor evidence is thin. The page at the Pulse address carries one customer testimonial from a Ford solution architect and no metrics.

For the Sparkplug side of the same namespace, see HiveMQ Sparkplug. If the real question is what to build first, our modernization roadmap work starts from the decisions, not the product list.

Frequently asked questions

What is HiveMQ Pulse?

HiveMQ announced Pulse on 18 February 2025 as a private preview of a distributed data intelligence platform for managing, transforming, governing and analysing device data, with a focus on the unified namespace. It sits above brokers and HiveMQ Edge and is not a broker itself. The page at its product address, read on 20 November 2026, does not name Pulse; its Contextualize section lists discovery and cataloguing, semantic modelling and UNS, and data governance, which resemble what Pulse was announced to do. HiveMQ has not said that Pulse is part of the suite.

Is HiveMQ Pulse generally available?

We could not confirm it. The announcement called it a private preview, and the product page we read on 20 November 2026 gives no general availability status, date or deployment detail. The pricing page does not mention Pulse. Anyone planning to rely on it should ask HiveMQ for its current status, licence terms and price in writing.

Was HiveMQ Pulse renamed Data Intelligence?

Not confirmed. HiveMQ's Platform Operator 2.3.0 release notes say Helm settings for HiveMQ Data Intelligence replace the HiveMQ Pulse values, and Edge 2026.16 updates a Data Intelligence agent. That points to a rename or a successor, but no HiveMQ page we read states it. Treat the names as one lineage you must verify.

What is in the September 2026 HiveMQ Platform suite?

HiveMQ announced the HiveMQ Platform on 9 September 2026 as layers called Connect, Contextualize, Analyze and Act, with an assistant named Bea. Act, for agentic AI, is a public preview. The documentation also shows an Explore area in the console. The broker alone is now called the HiveMQ Enterprise MQTT Broker, so check which product a quote means.

Can I build a unified namespace without Pulse?

Yes. A namespace needs an MQTT broker, a written topic convention and payload schemas, and something to enforce them. HiveMQ Edge, a broker and Data Hub can do the first three on open or generally available parts, as our unified namespace page describes. Pulse adds modelling, cataloguing and governance on top; it is not required.

References and further reading

  1. HiveMQ Introduces HiveMQ Pulse, a Next-Generation Distributed Data Intelligence Platform · HiveMQThe 18 February 2025 announcement: private preview, early access by application.
  2. HiveMQ Pulse · HiveMQThe current product page. It states no general availability status or date.
  3. HiveMQ Launches New Platform · HiveMQThe 9 September 2026 announcement of the suite.
  4. HiveMQ Edge 2025.16 Released · HiveMQPulse Agent, Pulse Assets and the Java 21 requirement.
  5. HiveMQ Platform Operator 2.3.0 release · HiveMQThe Helm values change from Pulse to Data Intelligence.
  6. HiveMQ Platform documentation · HiveMQ
  7. HiveMQ Pricing · HiveMQChecked on 20 November 2026; it does not mention Pulse.

← Unified Namespace

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.