Managed infrastructure
Add a device registry, state synchronization, and job tracking without maintaining their infrastructure.
EMQX Fleets Public Beta
Device management
for your MQTT fleet
Register devices, synchronize state, send commands, and run asynchronous jobs—all on EMQX Cloud.
Example fleet
- Devices
- 24
- Online
- 22
- Offline
- 2
| Device | Connection |
|---|---|
| thermostat-01 | Online |
| thermostat-02 | Online |
| sensor-03 | Offline |
thermostat-01Temperature setpoint
72°F
Desired
Requested setting
68°F
Reported
Device setting
Pending. The reported setpoint is still 68°F.
Why EMQX Fleets
Device services, fully managed.
Add device management to your MQTT application without running its backend infrastructure.
One view of each device
View device identity, connection status, and reported state together.
Part of EMQX Cloud
Use Broker for messaging, Tables for device history, and Fleets for device management in EMQX Cloud.
Capabilities
Register. Synchronize. Operate.
Device registry and models
Register devices and define reusable models for their properties, events, and commands.
Register your first deviceGroups and fleet search
Group devices and find them by connection status, type, or reported properties.
Search your fleetDevice shadows
Store desired and reported state, and see which settings each device still needs to apply.
Explore device shadowsRemote commands
Send a command to a connected device and track its response, failure, or timeout.
Send commandsFleet jobs
Dispatch asynchronous jobs to devices or groups and track progress for each device.
Manage fleet jobsConsole and APIs
Manage devices in the console or integrate Fleets into your application through APIs.
Explore the Fleets APIBenefits
Less maintenance. More visibility.
Focus on your product
Spend less time maintaining device services and more time building your application.
Investigate with context
Review device state and operation results to decide what to do next.
Find what needs attention
Spot pending or failed operations and identify the devices that need follow-up.
Use cases
Operate devices across sites
Inspect reported state, coordinate configuration changes, and track remote operations.
Support products after deployment.
Organize devices by model or group, inspect reported settings, and track remote configuration changes.
Coordinate configuration by site.
Group thermostats and controllers by location, review pending settings, and run configuration jobs.
Manage equipment remotely.
Inspect reported state and send supported commands through MQTT devices or gateways.
Coordinate devices across energy sites.
Group meters, inverters, and gateways by location to coordinate reporting and configuration changes.
Plans & Pricing
Plans for your fleet
Fleets instance and egress charges are waived during Public Beta. Broker, Tables, and applicable network charges are separate.
FAQ
Frequently asked questions
EMQX Fleets is the fully managed IoT device management service on EMQX Cloud. It provides a device registry, state synchronization, remote commands, and batch jobs.
Broker handles MQTT messaging. Fleets adds device models, persistent state, and operation tracking for your application.
Yes, using a standard MQTT client library. Device software must implement the Fleets topics, message formats, and workflows for the capabilities you use. See the MQTT integration guide.
Jobs can dispatch update instructions and track device-reported progress. Your device software and update infrastructure handle firmware download, validation, installation, and recovery. See the Jobs guide.
During Public Beta, Starter is available on Google Cloud in Iowa and Oregon. Capacity tiers range from 10,000 to 100,000 devices. The selected tier cannot currently be changed after creation. Check the current plans.
Fleets instance and egress charges are waived during Public Beta. Eligible accounts have one 14-day trial at the 10,000-device tier; non-trial deployments require a payment method. Broker, Tables, and applicable network charges are separate. See pricing details.
Migration requires mapping device identities, authentication, topics, state models, and operations to Fleets. MQTT support helps with transport integration; management APIs and behavior still need adaptation. Talk to us about your current setup.