A private managed broker
Use an isolated broker with TLS and WSS instead of running a server or exposing a home network. The shared public sandbox is only for disposable tests.
HIVEMQ CLOUD SERVERLESS MIGRATION
Move your MQTT project. Keep it managed.
HiveMQ Cloud Serverless Free and PAYG retire on December 31, 2026. RunMQTT offers private managed brokers, per-device credentials, and topic policies, with plans from $15/month.
A new endpoint needs a real migration plan
The retirement applies to Serverless Free and PAYG, not every HiveMQ service. New Serverless clusters are already unavailable.
Update the hostname, credentials, ports, and TLS settings in every affected client. The old cluster URL cannot move to another broker.
Plan retained messages and application recovery separately. Existing sessions, subscriptions, offline queues, and in-flight delivery state do not transfer automatically.
HiveMQ also offers eligible users a free self-managed Migration license. You operate that broker yourself; it is a different option from a hosted service.
Complete cutover before December 31, 2026. HiveMQ says Serverless clusters and their data will be permanently deleted after retirement.
Retirement details checked on October 20, 2026. RunMQTT is independent of HiveMQ.
For teams that want to keep broker operations off their plate
Keep your MQTT client libraries and topic design where compatible. Validate the behaviors your application depends on before moving production traffic.
Reviewable device access
Give devices revocable credentials and reusable publish/subscribe policies. Recreate and test both allowed and denied access during migration.
Choose by behavior as well as capacity
All plans include MQTT 3.1.1, MQTT 5, QoS 0/1, TLS, and WSS. Growth and Scale include QoS 2 and retained messages. Check retained compatibility before moving stateful workloads.
Validate your actual limits
Monthly capacity is not a burst-rate, subscription-count, region, or offline-storage guarantee. Ask us to assess high-rate gateways, hard-coded endpoints, integrations, and contractual requirements.
Estimate the bill before moving the fleet
Prices are in USD, before applicable taxes. Every publish and subscriber delivery counts in 512-byte units, rounded up. Connections include backend consumers.
| Plan | Monthly price | Concurrent connections | Monthly message units |
|---|---|---|---|
| Starter | $15 | 100 | 1,000,000 |
| Growth | $39 | 2,000 | 10,000,000 |
| Scale | $89 | 10,000 | 50,000,000 |
Example: each device publishes one payload of up to 512 bytes per minute to one subscriber, continuously for 30 days. These totals exclude other messages and are estimates, not performance measurements.
- 10 devices: 864,000 message units in 30 days.
- 20 devices: 1,728,000 message units in 30 days.
- 100 devices: 8,640,000 message units in 30 days.
One 7-day trial is available to eligible accounts. A payment method is required; cancel before the displayed trial end to avoid the selected plan’s charge. There is no permanent free private plan.
Prepare, verify, then switch
Start with synthetic data and one representative client. The guide includes a local verification script, a cutover checklist, and client-specific instructions.
- 01
Inventory the workload
Count devices and backend connections, message sizes, fan-out, retained state, subscriptions, and how deployed clients receive new settings.
- 02
Create the broker and access rules
Choose a plan, create policy templates, and issue RunMQTT device credentials. Your old HiveMQ hostname and credentials do not transfer.
- 03
Test representative clients
Check TLS and WSS, allowed and denied topics, reconnects, QoS, retained replay, and the real publish rate. A successful connection alone is insufficient.
- 04
Switch in batches with a rollback window
Coordinate devices and backend consumers, republish required state, and monitor deliveries and usage. Keep the old cluster until the migration is accepted and before its retirement.
For a migration assessment, share approximate connections, message rate, payload size, required features, client software, and target date. Do not send credentials or customer payloads. Assistance scope is agreed before cutover.
Questions before you migrate
Is RunMQTT a free HiveMQ Cloud alternative?
One 7-day trial is available to eligible accounts. A payment method is required; cancel before the displayed trial end to avoid the selected plan’s charge. There is no permanent free private plan.
Can I migrate without downtime or message loss?
That depends on endpoint updates, device availability, application recovery, and delivery semantics. Test staged cutover and rollback; changing the broker address does not move queues or guarantee uninterrupted delivery.
Can I move Home Assistant or ESP32 clients?
Standard MQTT clients can be configured for RunMQTT, but validate your exact software, TLS trust, topic access, subscriptions, retained state, and reconnect behavior. The client guides include acceptance checks and known retained-message limitations.
How do I keep a future move manageable?
Keep endpoint settings updateable, store your topic and access-policy inventory, and make applications able to republish current state and recover from a new session. Use the RunMQTT hostname for TLS; a custom CNAME alone does not provide a valid custom-domain endpoint. Discuss SLA, region, and continuity requirements before subscribing.
Follow your client’s migration path
Use the same client and protocol version as your deployed application.