PLCs, CNCs, robots and test stations publish once through edge gateways; your MES, SCADA, historian, OEE dashboards and maintenance tools subscribe. ConnectMQ runs the MQTT broker, so your OT team doesn’t have to.
No card required
Every new dashboard, MES module or analytics project means another OPC UA session, another Modbus poll or another script against the same PLC. Nobody knows any more what depends on what.
Each line, machine builder and plant has its own SCADA project, tag names and historian. Comparing OEE across sites turns into a spreadsheet exercise at the end of the month.
Spindle vibration, motor temperature and cycle-time drift are already in the controller, but they reach maintenance as a breakdown and a CMMS ticket after the line has stopped.
MQTT is the de facto transport for a unified namespace. ConnectMQ gives you a private broker for it — without a server to install and patch in the plant DMZ.
Your own isolated broker instance, MQTT 3.1.1 and 5 over TCP, TLS and WebSocket. Edge gateways such as Ignition, Kepware or Node-RED connect with standard settings.
Gateways open outbound TLS connections, so you add no inbound firewall rules into the OT network. Each gateway and application gets its own credentials and topic permissions.
Model enterprise, site, area, line and cell in the ISA-95 topic workspace, and let MES, ERP, historian and analytics subscribe to exactly the branch they need.
The dashboard and topic monitor show values as they arrive, threshold rules alert on temperature, vibration or stoppages, and the 3D Digital Twin puts live values on each machine.
Most plants start with machine condition and OEE, then add energy and AI agents on the same namespace — no new integrations at the machine.
Stream vibration, temperature and motor current to your models and open work orders before a machine fails
Explore the use caseLive OEE, availability and performance of critical assets across every site
Explore the use caseGive your AI agents live plant data and a guarded way to act, through the unified namespace
Explore the use caseSub-metered energy per site, line and asset, with peak-demand alerts in real time
Explore the use caseacme/dallas/assembly/line-2/station-05/telemetry
acme/dallas/assembly/line-2/station-05/alarms
acme/dallas/assembly/line-2/station-05/state (retained)
acme/dallas/assembly/line-2/oee (retained)
acme/dallas/assembly/line-2/mes/work-order (retained)A unified namespace is one hierarchical topic tree — usually enterprise/site/area/line/cell, following ISA-95 — where every system publishes its current state and events. MQTT is the usual transport: machines publish once, and MES, SCADA, ERP and analytics subscribe to what they need. ConnectMQ is the broker that holds the tree, and its ISA-95 workspace helps you design and browse it.
Usually both. OPC UA is strong close to the equipment, reading a PLC or machine with a rich information model. MQTT is better at distributing that data to many consumers across the plant and the cloud. A typical setup is an edge gateway that reads OPC UA or Modbus and publishes to an MQTT broker such as ConnectMQ.
Most PLCs don’t publish MQTT natively, so an edge gateway does it: Ignition, Kepware, Node-RED or a vendor IIoT gateway reads tags over OPC UA, Modbus TCP, S7 or EtherNet/IP and publishes them to ConnectMQ over TLS with its own credentials. Newer controllers with a built-in MQTT client can connect directly.
Connections are opened from the plant outbound over TLS, so no inbound ports into the OT network. Every gateway and application authenticates with its own username and password, and per-topic ACLs limit what each one can publish or subscribe to. Keep control loops and safety functions on the PLC, and use MQTT for monitoring, reporting and supervisory data.
Start on the Free plan — no card required. Connect one line, build your first live OEE dashboard, then move to Basic or Scale when you go live. No overage charges, cancel anytime.
