Telematics units, reefer controllers, trackers and warehouse robots publish over MQTT on cellular and Wi-Fi; your TMS, WMS, dispatch and customer apps subscribe. ConnectMQ runs the broker that keeps them connected while the signal comes and goes.
No card required
Vehicles drive through tunnels, rural areas and border crossings. Systems that poll a telematics API every few minutes miss events and show positions that are already out of date.
Trackers, reefer units, tyre sensors and door sensors come from different vendors, each with its own portal. Dispatch checks four screens to answer “where is it, and is it still cold?”
Shippers and consignees want live tracking, temperature evidence and instant delay notices — not a call to the dispatcher or a PDF after delivery.
MQTT was made for unreliable links: small packets, persistent sessions and Last Will. ConnectMQ gives you all of that as a managed broker, so your team builds the TMS integration, not the infrastructure.
A private, isolated broker instance run for you. Vehicles, depots and apps connect to one endpoint over TCP, TLS or secure WebSocket.
Every vehicle and gateway has its own username and password, and per-topic ACLs keep each on its own topics — a subcontractor’s trucks can publish without reading the rest of the fleet.
Persistent sessions deliver queued commands after a tunnel, Last Will marks a vehicle offline, and retained messages give a new dispatch screen every vehicle’s last position at once.
Threshold rules flag a reefer drifting from its set point, a door opened in transit or a vehicle that went silent, and notify dispatch straight away.
Logistics teams usually start with live fleet tracking and cold chain, then use the same topics for connected vehicle data and real-time notifications to drivers and customers.
Live location, vehicle and driver data for dispatch, your TMS and customer ETAs
Explore the use caseTemperature, door and location data from reefers, cold rooms and pharma shipments, with alerts on every excursion
Explore the use caseVehicle telematics, remote commands and OTA campaign messaging over one MQTT connection
Explore the use caseLive order status, delivery tracking, alerts and in-app updates pushed to web and mobile apps over secure WebSockets
Explore the use casefleet/truck-084/gps
fleet/truck-084/reefer/temperature
fleet/truck-084/commands
fleet/truck-084/status (retained)MQTT keeps one lightweight connection open and pushes data the moment it changes, with small headers that save cellular data. Persistent sessions and QoS 1 cope with dropouts, and Last Will reports a vehicle that disconnects unexpectedly — things you would otherwise build yourself on top of HTTP polling.
Many telematics units and gateways support MQTT natively: point them at your ConnectMQ endpoint with a username, password and TLS, and publish to topics such as fleet/truck-084/gps. For devices that only report to a vendor cloud, a small bridge service can read the vendor API and republish over MQTT.
Yes — MQTT was designed for large numbers of connected devices on constrained networks. Start your pilot on the Free plan, move to Basic or Scale as the fleet grows, and use shared subscriptions to spread incoming messages across several instances of your backend.
ConnectMQ supports TLS on every connection, separate credentials for every vehicle, gateway and app, and per-topic ACLs, on a broker instance isolated from other customers. Commands to vehicles travel on their own topics, which only your dispatch backend is allowed to publish to.
Start on the Free plan — no card required. Connect a few trucks or one depot, watch them live, then move to Basic or Scale when you go live. No overage charges, cancel anytime.
