If you build smart hardware for your own customers — appliances, wearables, controllers, sensors — your product depends on a broker you should not have to babysit. Focus on the device and the app; let the broker be infrastructure.
No card required
You build the firmware and the apps, ConnectMQ moves the data. Every unit you ship publishes its state; your mobile app, support console, analytics and update service each subscribe to the topics they need.
products/{device-id}/state
products/{device-id}/events
products/{device-id}/config (retained)Customers see live state and control the device from their phone; commands and state travel over the same broker.
Each unit gets its own credentials and topic permissions at the factory or on first setup.
Publish an update notice to a device group, watch each unit report its new version and roll out in waves.
Your support console subscribes to a single unit’s events and logs to help a customer in minutes.
Feature usage and errors from the field stream into your analytics, without a separate telemetry stack.
Start with a prototype batch on the Free or Basic plan and grow to a large fleet with the same code.
Rule for unit-0193: products/0193/#
| Client | Action | Topic | Result |
|---|---|---|---|
| unit-0193 | publish | products/0193/state | allowed |
| unit-0193 | subscribe | products/0193/config | allowed |
| unit-0193 | subscribe | products/0194/# | denied |
| unit-0193 | publish | products/0194/commands | denied |
| support-app | subscribe | products/+/events | allowed |
Give each device its own username and password and limit it to products/{its id}/#. A cloned or compromised unit cannot read or control anyone else’s device, and you can revoke one credential without touching the rest of the fleet.
The everyday loop of a connected product: the device in the customer’s home publishes its state, your mobile app subscribes, and commands go back on the device’s own topics. Device and app both connect out to ConnectMQ.
19:20 Air purifier
Publishes its state when the air gets worse: PM2.5 at 38 µg/m³, fan on level 1.
products/0193/state → {"pm25":38,"fan":1}19:20 Your mobile app
Subscribed to the device’s topics with the customer’s credentials. The customer taps Boost.
products/0193/set → {"fan":3}19:20 Air purifier
Speeds the fan up and confirms its new state, which the app shows straight away.
products/0193/state → {"pm25":31,"fan":3}19:21 Customer
Watches the air quality improve — and the device never sees anyone else’s topics.
Per-device credentials: unit 0193 may only use products/0193/#, so copied firmware cannot read or control anyone else’s purifier.
Machines, PLC gateways, OEE and quality data
Hubs, sensors and Home Assistant setups
Vehicle tracking, telematics and cold chain
Meters, EV chargers, solar and batteries
Robot fleets talking to fleet managers and AI pipelines
Power, cooling and rack environment
Streetlights, parking, air and waste sensors
Soil probes, weather stations and irrigation
From first ESP32 to classroom labs
Start on the Free plan with no card. Basic covers up to 100 concurrent connections — enough for a prototype batch and your test apps. Move to Scale as shipments grow — same endpoint style, no firmware rewrite.
