Connected Robots & Physical AI

MQTT for Connected Robots & Physical AI

AMRs, cobots, drones and humanoids publish telemetry and events over MQTT, and your fleet manager sends missions back on their own topics. ConnectMQ connects every robot to your fleet manager, WMS or MES and the data pipeline for your physical-AI models.

No card required

What you can build

Build your robot fleet platform on ConnectMQ

You build the fleet manager and the AI pipeline, ConnectMQ moves the data. Robots publish once — often through an MQTT bridge next to ROS 2 on board — and your fleet manager, WMS or MES, AI data pipeline and safety alerts each subscribe in parallel. Missions go back on dedicated topics.

Your robots
Mobile robots (AMRs)robots/{id}/telemetry
Cobot cellscells/{id}/cobot/state
Dronesdrones/{id}/telemetry
Charging docksdocks/{id}/status
ConnectMQ
  • TLS on 8883
  • per-device ACL
  • QoS 0, 1 and 2
  • Last Will
What you build on top
Fleet manager
WMS / MES
AI data pipeline
Safety & alerts
What you get

Connected Robots & Physical AI on ConnectMQ

  • Telemetry and events from every robot, mission commands back with QoS 1
  • Last Will marks a robot offline the moment it drops off the network
  • Retained state, so a restarted fleet manager knows every robot at once
  • Separate credentials and topic ACLs for every robot and application
example topic design
robots/amr-12/telemetry
robots/amr-12/mission/set
robots/amr-12/status                 (retained)
Publish once

One robot’s telemetry, every system in parallel

A robot publishes its position, battery and state once. Your fleet manager, your AI data pipeline and your safety monitor each subscribe on their own — adding a new consumer never touches the robot. Missions travel back on their own topic, and only the fleet manager is allowed to publish there.

Fan-out
AMR-12robots/amr-12/telemetry{"x":42.1,"y":7.8,"battery":64}
ConnectMQ
Fleet managerjobs, traffic and charging
AI data pipelinetraining and evaluation data you collect
Safety monitorstops, zones and near misses
Missions go back on their own topicrobots/amr-12/mission/set{"goto":"dock-3"}
Real-life example

Send a robot to charge before its battery runs out

A common MQTT setup in a warehouse: each AMR publishes telemetry, the fleet manager subscribes and sends missions back on the robot’s own topic. Robots and fleet manager both connect out to ConnectMQ over TLS.

ConnectMQMQTT broker · TLS 8883Low battery → AMR-12 to dock-3AMR-1224 %18 % ▼→ dock-3docked ✓4471 → AMR-07Fleet managerYour software · subscribedJob 4471→ AMR-12→ AMR-07dock-3ChargingAMR-07AMR-1224 %18 %18 %Warehouse, aisle 4AMR-12 · AMR-07 · dock-3robots/amr-12/telemetry {"battery":18}robots/amr-12/telemetry {"battery":18}robots/amr-12/mission/set {"goto":"dock-3"}robots/amr-12/mission/set {"goto":"dock-3"}robots/amr-12/mission/state {"state":"docked"}Fleet manager · nowAMR-12 docked at dock-3 — job 4471 moved to AMR-07ConnectMQMQTT broker · TLS 8883Low battery → AMR-12 to dock-3AMR-1224 %18 % ▼→ dock-3docked ✓4471 → AMR-07Fleet managerYour software · subscribedJob 4471→ AMR-12→ AMR-07dock-3ChargingAMR-07AMR-1224 %18 %18 %Warehouse, aisle 4AMR-12 · AMR-07 · dock-3robots/amr-12/telemetry {"battery":18}robots/amr-12/telemetry {"battery":18}robots/amr-12/mission/set {"goto":"dock-3"}robots/amr-12/mission/set {"goto":"dock-3"}robots/amr-12/mission/state {"state":"docked"}Fleet manager · nowAMR-12 docked at dock-3 — job 4471 moved to AMR-07
  1. 14:32 AMR-12

    Publishes its telemetry every second over the warehouse Wi-Fi. On its way to job 4471, the battery drops to 18 %.

    robots/amr-12/telemetry → {"x":42.1,"y":7.8,"battery":18,"state":"moving"}
  2. 14:32 Fleet manager

    Subscribed through ConnectMQ: it moves job 4471 to AMR-07 and sends AMR-12 to dock-3, with QoS 1.

    robots/amr-12/mission/set → {"goto":"dock-3","reason":"charge"}
  3. 14:33 AMR-12

    Its MQTT bridge hands the mission to the robot’s navigation; it drives to dock-3 and reports that it is docked.

    robots/amr-12/mission/state → {"goto":"dock-3","state":"docked"}
  4. 14:33 Shift lead

    Gets a notification: AMR-12 is charging, and AMR-07 has already taken over the job.

A robot drops off the Wi-Fi: ConnectMQ publishes its Last Will robots/amr-12/status → offline as a retained message, so the fleet manager stops assigning it jobs right away.

Industries & use cases

Where teams use Connected Robots & Physical AI

Pilot

Pilot one robot cell this week

Start on the Free plan with no card. Basic covers up to 100 concurrent connections — enough for a pilot fleet of robots, their charging docks and your fleet manager. Move to Scale when you add sites and robots.