Book a consultation

HiveMQ

HiveMQ Cloud: Tiers, Hosting, Serverless Retirement and Plant Fit

HiveMQ Cloud explained: Starter and Enterprise tiers, EU and US hosting, the Serverless end on 31 December 2026, certifications and plant failure modes.

Vladimir Romanov


HiveMQ Cloud is HiveMQ’s managed MQTT service: HiveMQ runs the broker, you point clients at it. For a plant, the question is rarely whether the service works. It is what happens to the line when the connection between the plant and the service does not. This page covers the tiers HiveMQ lists today, where it hosts, the retirement of the Serverless plans on 31 December 2026, the certifications, and how a cloud broker fails a plant. It is current as of 21 November 2026 and built from HiveMQ’s pricing page, documentation and announcements. Prices change, so date any figure you quote.

It sits under the HiveMQ hub and has one deeper page, listed at the end. The self-managed alternatives are on the HiveMQ Platform page. HiveMQ Cloud is one product line of a company we profile separately.

HiveMQ Cloud tiers as listed today

HiveMQ’s pricing page lists two Cloud tiers: Starter and Enterprise. HiveMQ’s Serverless vs Starter blog post (dated 27 February 2026 on the page) names a lineup of Serverless, Starter, Professional and Enterprise. We did not find Standard or Professional on the pricing page on 21 November 2026, so we do not describe them as current. The Cloud documentation still lists the Serverless Free and Pay As You Go plans, which are being retired (next section).

StarterEnterprise
Price as listed 21 Nov 2026From $0.34 per hour plus $0.80 per million messages; 15-day trialCapacity-based quote
Connections and throughput10,000 connections, 1 MB per secondCustom
Uptime SLA99.95%Up to 99.99%
SupportSilverSilver, Gold or Platinum
HostingEU and US“Choose your cloud”
Multi-AZ and Private LinkNot offeredOffered
Platform layersConnect onlyConnect, Contextualize, Analyze, Act (public preview)

Source: HiveMQ pricing page, 21 November 2026. A fetched summary of a pricing page can flatten fine print, so re-read the live page before you put these numbers in a budget. The Starter figures are minimums: “from $0.34 per hour” is a starting price, and the message charge is separate. The Enterprise unit of pricing is not published.

Hosting. The pricing page says only “EU and US” for Starter. We could not confirm which hyperscalers host it or which regions exist, so the page does not say, and neither should a design document until HiveMQ confirms in writing. Where a plant’s data must stay is covered in Cloud vs self-hosted.

Scattered white clouds over a flat green horizon
A broker in the cloud is far from the machine: every publish crosses a wide area network, and the plant depends on that link.

The Serverless retirement on 31 December 2026

HiveMQ’s documentation states that HiveMQ Cloud Serverless is being retired on 31 December 2026. After that date clients cannot connect, and clusters and their data are deleted. The documentation also says users who are affected can claim a free migration licence for the self-managed HiveMQ Enterprise broker. The note covers the Serverless Free and Pay As You Go plans.

We found this date in a single source, the Cloud documentation, which is a primary source. A web search turned up no second page. In our view that is enough to act on and not enough to leave unconfirmed: if you run a Serverless cluster, ask HiveMQ to confirm the date and the migration terms in writing, and plan as if the date is firm. The steps are on the Cloud vs self-hosted page.

Why it matters beyond HiveMQ. A hosted tier can be withdrawn on the vendor’s schedule, not yours. Google Cloud IoT Core, announced for shutdown in August 2022 and retired on 16 August 2023, is the cautionary precedent in this market. A plant system that treats a cloud broker as permanent infrastructure needs an exit path before it needs a feature.

HiveMQ Cloud certifications

HiveMQ publishes three assurance items that matter to a security review. Read each for scope, because a company-level certificate is not the same as a certified product.

ItemWhat HiveMQ saysScope note
ISO/IEC 27001HiveMQ states it holds the certification. Its July 2024 SOC 2 announcement says “ISO/IEC 27001:2013” and its March 2024 post gives no version. We could not confirm a move to the 2022 editionHiveMQ’s blog names development, operations, support systems, products and professional services, with “on-premise, Cloud, extensions, broker”. Edge is not named
SOC 2 Type IIAnnounced 18 July 2024, all five Trust Services Criteria, auditor Insight AssuranceThe announcement does not say which products are in scope. Type I was completed in January 2024
CSA STARHiveMQ Cloud is listed on the Cloud Security Alliance registryThe registry lists HiveMQ Cloud with a Level 1 entry (CAIQ self-assessment v4.0.3, dated 11 December 2025) and a Level 2 entry (STAR Certification v4.0, dated 24 November 2025). Read the Level 2 scope before relying on it

We found no HiveMQ IEC 62443 statement for the broker. 62443 is the industrial security standard, and our IEC 62443 guide explains where a broker sits in it. Third-party profiles sometimes list further compliance frameworks for HiveMQ Cloud. We do not repeat them because HiveMQ does not confirm them.

How a HiveMQ Cloud broker is selected

It fits when the data producers are already off-site or on the internet. Fleets of remote devices, vehicles, sites with no IT staff, and pilots where nobody wants to run a server are the cases the managed model suits. For a manufacturing plant, selection usually turns on four questions.

  1. Where must the data stay? A regulation or a customer contract may fix the region. “EU and US” is a coarse answer.
  2. What does the line do without the broker? If a stopped link must not stop the process, the cloud cannot be the only broker.
  3. Who operates it? A managed service removes broker patching. It does not remove client configuration, topic design or access control.
  4. What are the limits? Starter lists 10,000 connections and 1 MB per second. Know your peak connection count and message rate first.

For contrast, the hyperscalers. Amazon Web Services IoT Core and Azure Event Grid are also managed MQTT services, and both document differences from the specification. Their documentation lists QoS 0 and 1 only, with QoS 2 not supported, and AWS documents that message ordering is not guaranteed. A design that relies on QoS 2 or on strict ordering needs to test each service. These are documented facts about those services, not a ranking. Which is right depends on what else is already in the cloud account.

How HiveMQ Cloud fails for plants

These are our reading of how any cloud-hosted broker behaves in a plant, drawn from general MQTT and IT/OT practice, not HiveMQ incident reports.

Where a cloud MQTT broker fails a plant A plant zone holds a PLC and a gateway with local buffering. A WAN link leads to a managed cloud broker. Four numbered failure points: the plant uplink, WAN latency, quota limits at the broker, and a broker-side change such as a plan retirement. Plant PLC and sensors Gateway with local buffer WAN and internet Managed cloud broker Connections and rate quota Plan and service lifecycle 1 2 3 4 1 Uplink down: publishes stop unless the gateway buffers them. 2 Latency: every publish and acknowledgement waits on the round trip. 3 Quota: connections or rate above the plan are refused or slowed. 4 Lifecycle: a plan can be retired on the vendor's date.
A cloud broker adds a wide area network and a vendor's plan limits between the machine and its data. The fix is a local buffer at the plant, not a faster link.
  • WAN or ISP outage. The plant keeps running its PLCs, but anything that depends on the broker stops: dashboards, downstream consumers and any control logic that listens to MQTT. A client library queues some messages while disconnected, but an in-memory queue is bounded and lost on restart. HiveMQ Edge offers offline buffering, in memory or file-native, as a commercial feature, and in the Ignition path the store-and-forward sits in the MQTT Transmission history store, not the broker.
  • Latency. MQTT at QoS 1 waits for an acknowledgement, so each publish costs a round trip. For monitoring that is fine. For anything that closes a loop in tens of milliseconds it is not, and our MQTT guide explains why such loops belong on the plant side.
  • Quotas. A plan with 10,000 connections and 1 MB per second has a ceiling. Birth bursts after an outage, when every device reconnects and republishes at once, are where ceilings are hit, so size for the recovery peak, not the average.
  • Security perimeter. Outbound-only connections from the plant to the cloud are easier to defend than inbound ones, but each client still needs credentials and TLS. See OT network segmentation for where the broker goes.
  • Lifecycle. The Serverless retirement is the example. A plan, region or feature can change on the vendor’s date.

HiveMQ Cloud lifecycle and licensing

Cloud is billed as a service: usage-based on Starter, a quoted capacity on Enterprise. There is no licence key to manage, and no version to patch. HiveMQ’s broker releases (4.57 on 3 November 2026, with 4.55 the current long-term-support line) are the self-managed track. We did not find a published statement of which broker version Cloud runs or when it upgrades, so ask. The self-managed plans, Lab, Launch, Run and Enterprise, are compared on editions and pricing.

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.

  • Placement: deciding which brokers sit at the plant, which in a data centre and which in a cloud, before any vendor is chosen.
  • Failure design: specifying local buffering, reconnect behaviour and recovery-peak sizing for the link to a cloud broker.
  • Network review: placing the broker and its outbound paths in the OT network, through OT network assessment.
  • Exit planning: a documented path off any hosted service, written before it is needed.
  • Vendor questions: a written list to put to HiveMQ or any managed provider about scope, regions and limits.

Limits and open questions

  • Regions and hyperscalers. The pricing page says “EU and US”. We could not confirm which clouds or regions host Starter.
  • Tiers. We did not find Standard or Professional on the pricing page. Whether either survives under another name is unconfirmed.
  • Serverless date. One primary source, the Cloud documentation.
  • Certification scope. The SOC 2 announcement names no products, a HiveMQ page we could not verify may describe Cloud as Type I, and the ISO standard version is stated differently in different HiveMQ posts. Ask for the certificate and report.
  • Enterprise pricing unit. Not published.
  • Cloud broker version and upgrade policy. Not found.

Read the live pricing page and ask HiveMQ for written answers before you rely on any of these.

Deeper

  • Cloud vs self-hosted: what Serverless users must do before 31 December 2026, and how to decide between Cloud and a broker you run

Across to a sibling: the HiveMQ Platform, the self-managed side. Back to the HiveMQ hub, or read about the company behind it.

Frequently asked questions

What tiers does HiveMQ Cloud have?

HiveMQ's pricing page, as listed on 21 November 2026, shows two Cloud tiers: Starter, from $0.34 per hour plus $0.80 per million messages, and Enterprise, priced by quote. We did not find Standard or Professional tiers on that page, although a HiveMQ blog post dated 27 February 2026 names a Professional tier. Check the live page before you budget.

When does HiveMQ Cloud Serverless end?

HiveMQ's documentation states that Serverless retires on 31 December 2026. After that date clients cannot connect, and clusters and data are deleted. We found this date in one source, the Cloud documentation, so confirm it in writing with HiveMQ if you run a Serverless cluster.

Is there a free route off Serverless?

HiveMQ's documentation states that affected Serverless users can claim a free migration licence for the self-managed Enterprise broker. Moving to Cloud Starter is the other documented path. We did not read the licence terms, so ask HiveMQ what the migration licence covers and for how long.

Is HiveMQ Cloud certified?

HiveMQ states it holds ISO/IEC 27001 and SOC 2 Type II, announced on 18 July 2024, and its Cloud service is listed on the Cloud Security Alliance STAR registry with a Level 1 self-assessment and a Level 2 certification entry. The certification scope is the company and its products, and the announcement does not say which products SOC 2 covers. Ask for the reports and read the scope.

Can a plant run on a cloud MQTT broker alone?

It can, but in our view it should not be the only broker. A WAN or ISP outage cuts every client from the broker, and latency adds delay to every publish. Most plant designs keep a broker or gateway at the site and bridge selected topics to the cloud.

References and further reading

  1. HiveMQ Pricing · HiveMQCloud tiers, prices and hosting regions as listed on 21 November 2026.
  2. HiveMQ Cloud documentation · HiveMQServerless retirement notice and the migration licence.
  3. HiveMQ earns SOC 2 Type II compliance · HiveMQThe 18 July 2024 announcement.
  4. Understanding HiveMQ ISO/IEC certification · HiveMQScope statement for ISO/IEC 27001.
  5. HiveMQ Cloud on the CSA STAR registry · Cloud Security Alliance
  6. AWS IoT Core MQTT developer guide · Amazon Web ServicesDocumented differences from the MQTT specification, for contrast.
  7. Azure Event Grid MQTT support · MicrosoftQoS, TLS and message size limits, for contrast.

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