Your DCS runs the process. ConnectMQ moves the data around it — tank levels, utilities, rotating equipment and emissions — from edge gateways to the historian, MES, maintenance and AI tools that need it, over standard MQTT and TLS.
No card required
Process values sit in the DCS and historian behind strict network zones. Every new consumer — a LIMS, an energy report, an optimisation model — means another OPC connection and another firewall request.
Tank farms, wastewater, cooling towers, compressed air and steam often run on standalone PLCs, RTUs or radar gauges that nobody reads in real time — until someone walks the tank farm with a clipboard.
Each plant has its own tag names, gateways and scripts. Comparing a reactor at one site with its twin at another means mapping spreadsheets, not subscribing to a topic.
ConnectMQ is a managed MQTT broker: edge gateways publish read-only process and asset data once, and every application subscribes. Control and safety stay in your DCS and SIS.
Each plant or group gets its own isolated broker instance. No broker servers to patch in the DMZ, no cluster to babysit — your team focuses on gateways and applications.
Gateways connect out over TLS with their own credentials, and per-topic ACLs limit each one to its unit. A lab app can read tank levels without seeing anything else.
Model enterprise, site, area, unit and equipment in the ISA-95 topic workspace, so historian, MES and analytics subscribe to the same tree with wildcards.
Threshold rules flag a tank above its high level, a pump running hot or a stack reading out of range and notify the right team — alongside your DCS alarms, never instead of them.
Chemical producers usually start outside the control loop — tank inventory, rotating equipment health and environmental data — then feed the same topics to AI agents and optimisation tools.
Remote level readings from fuel, chemical, LPG and bulk tanks for vendor-managed inventory and timely refills
Explore the use caseGive your AI agents live plant data and a guarded way to act, through the unified namespace
Explore the use caseStream vibration, temperature and motor current to your models and open work orders before a machine fails
Explore the use caseParticle counts, differential pressure, temperature and humidity from cleanrooms into your EMS, dashboards and alerts
Explore the use casechem/antwerp/tank-farm/tk-101/level
chem/antwerp/unit-3/p-305a/vibration
chem/antwerp/environment/stack-2/emissions
chem/antwerp/unit-3/r-301/status (retained)Yes. The usual pattern is an edge gateway that reads values from the DCS or PLCs — over OPC UA or Modbus — and publishes them read-only over MQTT. The DCS keeps running the process and the SIS keeps protecting it; MQTT only distributes the data to applications outside the control layer.
Both. OPC UA is strong inside the control network, close to the DCS and PLCs. MQTT is better for moving that data out to many consumers: gateways publish once over an outbound connection and any number of applications subscribe. Many plants convert OPC UA to MQTT at the edge with Kepware, Ignition or Node-RED.
On ConnectMQ every connection can use TLS, every gateway and application has its own username and password, and per-topic ACLs control who may publish or subscribe to what. Gateways only open outbound connections, so nothing in the plant network has to accept inbound traffic. Network zoning and your security review stay with you.
Connect radar or pressure level transmitters to a PLC, RTU or cellular gateway that publishes level and temperature to topics such as chem/antwerp/tank-farm/tk-101/level. Retained messages give a dashboard the last level the moment it opens, and threshold rules alert on high or low levels.
Start on the Free plan — no card required. Connect one unit or tank farm, prove the data flow, then move to Basic or Scale when you go live. No overage charges, cancel anytime.
