Product documentation

Build and operate with RunMQTT

Start with a private broker, lock down device access, then understand the protocol and billing details before production traffic arrives.

Product overview

How RunMQTT organizes private brokers, device identities, topic access, and day-to-day operations.

Create a private broker, grant a test topic, and receive your first message over TLS.

Connect JavaScript, Python or Java applications to RunMQTT, or use a coding agent to adapt the integration to your project.

Assess your MQTT workload, recreate access controls, verify clients, and switch to RunMQTT with a rollback plan.

Model device identities and publish-subscribe permissions with reusable policy templates.

Supported MQTT versions, transport endpoints, QoS levels, retained messages, and browser console scope.

Distribute live messages across backend workers and verify delivery using your private RunMQTT Broker.

Test reconnects, offline delivery, retained state and Last Will behavior before production.

Replace HiveMQ connection settings with verified TLS, scoped RunMQTT credentials, and a real MQTT message round trip.

Locate connection and delivery failures using RunMQTT credentials, policies, logs and usage.

Plan broker reconfiguration, MQTT discovery, availability and restart checks before switching Home Assistant from HiveMQ.

Self-serve plan prices, private broker capacity, message accounting, usage review, and custom fleet pricing.