Register, organize, command. EMQX Fleets gives you the entire device management stack as one managed service on EMQX Cloud. Skip the AWS IoT Core stitching, ship in days.
Millions
Devices per Fleet
<100 ms
Twin Update Latency
99.95%
Service SLA
MQTT 5.0
Native Wire Protocol
One
Unified EMQX Cloud Console
Teams either stitch together brokers, databases, and bespoke APIs, or get locked into a hyperscaler's IoT stack. Both paths leak time, money, and operational risk.
Brokers, shadows, registries, and time-series stores all live in different services with different bills and SLAs.
Platforms like AWS IoT Core and Azure IoT Hub trap your devices in proprietary topics and pricing models.
Rolling your own registry, shadow, and command pipeline burns 6–12 months before a single device ships.
Without unified registry and query layers, operators can't answer "which devices are offline in building A?"
Fleets sits on top of EMQX Broker and EMQX Tables to give you registry, shadow, query, jobs, and diagnostics, delivered as a single managed service on EMQX Cloud.
Multiple vendors, multiple bills, lots of glue code.
Devices
Self-host Broker
Custom Registry
Twin DB
Jobs Runner
Time-Series Silo
Five managed primitives, one console, one API.
Define device blueprints with Thing Types, register Things, and roll them up into Thing Groups, from one console or REST API.
A digital twin per device captures reported state, accepts desired state, and converges bi-directionally over MQTT, with built-in versioning.
Search and segment your entire fleet by type, group, tag, status, or property value. Instant results across millions of devices.
Push configuration or trigger commands across thousands of devices, with delivery tracking, timeouts, retries, and per-execution status.
A walk-through of the console. Built for operators, designed for engineers.
A Single Pane of Glass for Every Fleet.Thing types, registered things, online counts, deployment health, and region, refreshed in real time.
Thing Types
12
Things
248,103
Online
241,872
| Property | Value |
|---|---|
| Status | Running |
| Cloud Platform | AWS / Azure / Google Cloud |
| Region | us-east-1 |
Model Devices Once. Register Thousands.Define a Thing Type with versioned JSON; every Thing inherits its properties, events, and commands and reports state automatically.
| Thing | Type | Status |
|---|---|---|
| Main Floor Climate Hub | home-climate-hub@1.0.0 | Online |
| Loading Dock Sensor 04 | door-sensor@2.1.0 | Online |
| Robot Arm · Bay 12 | robot-arm-r6@1.4.0 | Online |
Reported, Desired, Delta. Converging in Real Time.The shadow gives operators a view of what every device reports and what the cloud wants, side by side, with version vectors and auto-acknowledgement.
Reported
{
"mode": "standard",
"version": 42
}
Desired
{
"mode": "eco",
"version": 43
}
SQL-Like Queries Across Millions of Devices.Filter by tag, group, status, type, or property value, and stream results into dashboards, alerts, or downstream pipelines.
1status:offline AND group:"Building-A"
2 AND tag:battery-watch
| Name | MQTT Client ID | Status | Tags |
|---|---|---|---|
| lock-frontdoor | mqtt-lock-frontdoor | Offline | building-a · battery-watch |
| thermostat-lab | mqtt-thermostat-lab | Offline | building-a · floor-3 |
Fleet-Wide Jobs and One-Shot Commands.Schedule jobs over thousands of devices or fire request-response commands, with retries, timeouts, and complete per-execution audit.
Succeeded
3,084
In Progress
812
Failed
19
Every primitive you'd build yourself, designed, scaled, and supported by EMQ.
Reusable, versioned capability templates let device behavior evolve safely over time.
Register, tag, group, and decommission devices via REST API or console; connection state tracked by EMQX.
Organize by location, project, or tenant; hierarchical namespaces give a tree view with rolled-up counts.
Push configuration or trigger commands over MQTT with delivery tracking, timeouts, and retries.
Devices publish severity-tagged events; operators acknowledge and resolve from one console.
Query historical readings with avg/min/max/last aggregations and time bucketing, no separate pipeline.
Fleets ships with the API primitives engineers expect and the operating model business owners need.
Per-VIN twins, OTA-ready desired state, and group-level rollouts for millions of vehicles, OBUs, and dashcams.
Model PLCs, sensors, and machines as Thing Types; group by factory and line for predictive maintenance.
Always-on shadows for thermostats, hubs, and sensors; sync setpoints from apps and roll out firmware fleet-wide.
Expose Fleets as the control plane for AI agents, let LLM-driven workflows query state, send commands, and react to events safely.
Describe a device type with a versioned JSON Thing Type with properties, events, commands, and security.
// home-climate-hub@1.0.0
{
"thingType": "home-climate-hub",
"version": "1.0.0",
"properties": {
"temp": "float",
"mode": "enum"
},
"events": ["over_temperature"],
"commands": ["set_mode"]
}
Provision Things via REST API or console; devices connect with MQTT 5.0 and auto-bind to their type.
# Provision a thing
$ curl -X POST https://api.emqx.cloud/v1/things \
-H "Authorization: Bearer …" \
-d { "name":"main-hub-001",
"thingType":"home-climate-hub@1.0.0",
"tags":{ "building":"A" } }
Query the fleet, sync shadows, dispatch jobs, and stream history, all from the EMQX Cloud console.
# Query offline things in Building-A
GET /v1/things?q=status:offline AND group:Building-A
# Update desired state
PATCH /v1/things/main-hub-001/shadow/desired
{ "mode": "eco" }
Fleets is one of four managed services on EMQX Cloud. Together they form a complete IoT backend.
EMQX Brokers
Managed MQTT 5.0 messaging at any scale.
EMQX Tables
Time-series database integrated with the broker.
EMQX Fleets
Device management for connected fleets.
EMQX Agents
AI control plane for agentic IoT.
Open standards, no lock-in, global edge presence, and enterprise-grade security.
Pure MQTT 5.0 and REST APIs. No proprietary device SDKs required.
Migrate workloads in or out. Your topics, your data.
Multi-cloud, multi-region deployments on AWS, GCP, and Azure.
SOC 2 Type II, mTLS, RBAC, and Defender anomaly detection.
Everything you need to know about EMQX Fleets.
New fleets onboard weekly with hands-on support from the engineering team. Tell us about your use case and we'll be in touch within five business days.