RTUs and edge gateways at wellpads, compressor stations and terminals publish only what changed, over cellular, radio or satellite. Your SCADA, historian and production apps subscribe — on a managed MQTT broker you don’t have to run.
No card required
Poll-response SCADA asks every RTU for every register on a fixed schedule, over cellular, radio or VSAT links billed by the megabyte. Scan times stretch, and most of what comes back hasn’t changed.
Lease operators drive hundreds of miles a week to read tank levels, check a pumpjack or confirm a compressor restarted — because the data never left the site.
Production engineering, maintenance and hauling all need the same well and tank data, but it sits in one SCADA host, and every new consumer is another integration and another poll.
MQTT was first designed to monitor oil pipelines over satellite. ConnectMQ gives you its report-by-exception model as a managed, private broker.
Your own isolated MQTT 3.1.1 and 5 broker over TCP, TLS and WebSocket — no broker VM to patch. Ignition Edge, Node-RED and MQTT-capable RTUs connect with standard settings.
Sites connect outbound over TLS with their own username and password, so no inbound ports are opened at the wellsite. Per-topic ACLs keep each site, partner and contractor on their own topics.
Last Will flags a site the moment its link drops, retained messages keep the last known value of every tag, and persistent sessions with QoS 1 catch up after an outage. Sparkplug B birth and death messages work over it as standard MQTT.
Threshold rules on tank level, casing pressure or compressor temperature send alerts and notifications, and the dashboard and topic monitor show field values from anywhere.
From the wellpad to the terminal, these are the MQTT use cases upstream, midstream and downstream operators start with.
SCADA data from unmanned wellheads, pipelines, pump stations and substations over cellular or satellite
Explore the use caseStream vibration, temperature and motor current to your models and open work orders before a machine fails
Explore the use caseRemote 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 caseupstream/pad-14/well-07/wellhead
upstream/pad-14/well-07/pump/commands
upstream/pad-14/status (retained)
downstream/terminal-5/tank-12/level (retained)
spBv1.0/west-field/DDATA/pad-14/well-07MQTT was originally created to monitor oil pipelines over satellite links. Devices publish only when a value changes (report by exception), messages are small, and the broker fans data out to every subscriber. That is far more efficient than polling remote RTUs over cellular, radio or VSAT.
Sparkplug B is a specification on top of MQTT that defines a topic namespace (spBv1.0/…), a payload encoding and birth/death messages for edge nodes; it is common with Ignition and other SCADA hosts. It runs over standard MQTT 3.1.1, so ConnectMQ carries Sparkplug B messages like any others — your edge nodes and host application handle the encoding and state logic.
Use an RTU or flow controller with a built-in MQTT client, or add a small edge gateway (Ignition Edge, Node-RED, a vendor IIoT box) that reads the existing RTU or PLC over Modbus or DNP3 and publishes to ConnectMQ over cellular or satellite. Give every site its own credentials and topics, publish on change, and add a periodic heartbeat.
It was built for them: one long-lived connection, a header of a few bytes, QoS 1 for messages that must arrive, persistent sessions that resume after a dropout and Last Will to flag a lost site. Tune the keep-alive to your link so outages are detected quickly without wasting airtime.
Start on the Free plan — no card required. Connect a few wellpads or tanks, watch them report by exception, then move to Basic or Scale when you go live. No overage charges, cancel anytime.
