Less operational work
Leave broker infrastructure, maintenance, and upgrades to the team behind EMQX.
EMQX Broker
Managed MQTT.
Any Cloud.
Connect devices, process messages, and route data to applications across AWS, Azure, OCI, and Google Cloud.
Free monthly quota on Serverless. View pricing
Example message flow
sensor-01 Online machine-02 Online
Publish · MQTT over TLS
EMQX BrokerQoS 1
Topic
factory/line-1/temperature{ "device_id": "sensor-01", "temperature": 24.6 }Subscribe
Live dashboard
Rule + connector
Data platforms
Why EMQX Broker
Build your product. We’ll run the broker.
Enterprise MQTT, data integration, and cloud choice in one managed service.
Built-in data integration
Filter, transform, and send device data to your existing systems with rules and connectors.
Your choice of cloud
Choose a supported cloud and region, or use your own cloud account with BYOC.
Capabilities
Ready for production MQTT
MQTT messaging
MQTT 3.1.1 and 5.0, QoS 0–2, retained messages, and shared subscriptions. Connect over TLS or WebSocket.
Scalable capacity
Size Dedicated Flex for your session and message load, with dedicated resources for your deployment.
Message processing
Use SQL rules and Flow Designer to filter, transform, and route messages to downstream systems.
Cloud deployment
Choose your cloud and region. Connect private resources with VPC peering and PrivateLink on supported plans.
Enterprise security
Protect connections with TLS and topic permissions. Add mTLS and external authentication on supported plans.
Observability
Track connections and message traffic. Use client details, alerts, logs, and traces to investigate issues.
Benefits
More time for your product
Launch faster
Start connecting devices without first building and operating a broker cluster.
Reduce integration work
Replace custom routing code with configurable rules and connectors.
Keep your architecture flexible
Choose your deployment environment and keep the systems you already use.
Use cases
Connect what your business runs on
Data centers
Stream liquid cooling and power telemetry from PLCs via edge gateways for monitoring and analytics.
Industrial telemetry
Stream data from MQTT devices and edge gateways to your cloud applications.
Energy systems
Collect telemetry from meters, inverters, and charging infrastructure across sites.
Connected vehicles
Move vehicle telemetry, status updates, and messages between vehicles and cloud services.
Plans & Pricing
Plans for your workload
Start with Serverless, choose isolated production capacity with Dedicated Flex, or deploy in your own cloud account with BYOC.
Customer stories
In production. Making a difference.
How teams use EMQX managed services in their applications.
Connected safety · BYOC
Reliable messaging for safety systems.
Inovonics moved to EMQX Cloud BYOC to support wireless safety systems in the U.S. and Canada, with Redis authentication and DynamoDB integration.
Read Customer Story
Media services · Managed MQTT
Less work to connect each new service.
TVU uses EMQX Broker for real-time messaging across MediaHub. Standard MQTT topics simplify service integration; EMQX Tables stores operational metrics.
Read Customer Story
Connected mobility · EMQX Cloud
30% more efficient R&D delivery.
Luyuan built its next-generation IoT platform for smart two-wheelers on EMQX Cloud, shortening new business launches by three months.
Read Customer Story
FAQ
Frequently asked questions
EMQX Broker is the fully managed MQTT service on EMQX Cloud. Built on EMQX Enterprise, it connects devices and applications, processes messages, and routes data to your systems.
EMQX Enterprise is the software you deploy and manage. EMQX Broker delivers managed MQTT. EMQX Cloud is the platform that includes Broker, Tables, Fleets, and Agents.
Dedicated Flex supports AWS, Azure, Google Cloud, and Oracle Cloud. BYOC supports AWS, Azure, and Google Cloud. Serverless options differ. See the current region list.
Choose Serverless for a quick start or smaller workloads, Dedicated Flex for isolated production capacity, and BYOC for deployment in your own cloud account. Plan changes may require migration.
Yes. EMQX Broker supports standard MQTT clients. When migrating, check endpoint settings, authentication, topic permissions, and any features specific to your current service.
Yes. Rules and connectors can send MQTT data to Kafka, GCP Pub/Sub, EMQX Tables, Snowflake, databases, and cloud services. Source connectors can also publish data back to MQTT where supported. Connector availability and private networking depend on your plan.
No. Broker can be used on its own. Add Tables for time-series storage, Fleets for device management, or Agents for AI workflows. These are separate EMQX Cloud services.