--- title: "MQTT Broker for Oil & Gas | Wells, Pipelines, Tanks | ConnectMQ" description: "Managed MQTT for oil and gas: report-by-exception data from wellheads, pipelines and tank farms over cellular or satellite, Sparkplug B-style topics and TLS." url: "https://connectmq.com/industries/oil-gas/" language: "en" --- ![](https://connectmq.com/images/industries/hero/oil-gas.webp) # Every well and tank, reporting by exception 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. [Try it free](https://app.connectmq.com/signup) [Use cases](#use-cases) No card required The challenge ## Remote assets, expensive data 1. 01 ### Polling over thin links 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. 2. 02 ### Truck rolls to read a gauge 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. 3. 03 ### Data locked in the SCADA host 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. Why ConnectMQ ## Why oil and gas teams choose ConnectMQ MQTT was first designed to monitor oil pipelines over satellite. ConnectMQ gives you its report-by-exception model as a managed, private broker. - ### 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. - ### Outbound TLS from the field 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. - ### State awareness over bad links 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. - ### Alarms without a SCADA seat 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. Key use cases ## Key use cases in Oil & Gas From the wellpad to the terminal, these are the MQTT use cases upstream, midstream and downstream operators start with. [ ### Remote Asset Monitoring SCADA data from unmanned wellheads, pipelines, pump stations and substations over cellular or satellite Explore the use case](https://connectmq.com/use-cases/remote-asset-monitoring/)[ ### Predictive Maintenance Stream vibration, temperature and motor current to your models and open work orders before a machine fails Explore the use case](https://connectmq.com/use-cases/predictive-maintenance/)[ ### Tank Level Monitoring Remote level readings from fuel, chemical, LPG and bulk tanks for vendor-managed inventory and timely refills Explore the use case](https://connectmq.com/use-cases/tank-level-monitoring/)[ ### Industrial Agentic AI Operations Give your AI agents live plant data and a guarded way to act, through the unified namespace Explore the use case](https://connectmq.com/use-cases/industrial-agentic-ai/) Architecture ## From the field to your control room - Wellhead RTUs & pump controllers - Compressor & pump stations - Pipeline pressure & CP sensors - Tank level gauges **ConnectMQ**MQTT 3.1.1 · 5 · TLS - SCADA & HMI - Historian - Production & hauling apps - Maintenance & AI agents Example topic namespace ``` upstream/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-07 ``` Related solutions ## Solutions for Oil & Gas [ ### Industrial IoT & Smart Manufacturing Machines, PLC gateways, OEE and quality data Learn more](https://connectmq.com/industrial-iot/)[ ### Smart Energy Meters, EV chargers, solar and batteries Learn more](https://connectmq.com/energy-utilities/) ## Oil & Gas: frequently asked questions Why is MQTT used in oil and gas? MQTT 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. What is Sparkplug B, and does ConnectMQ support it? 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. How do I connect remote RTUs and wellsites to an MQTT broker? 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. Is MQTT reliable over satellite and cellular links? 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. ## Pilot your remote sites on ConnectMQ 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. [Get started](https://app.connectmq.com/signup) [See pricing](https://connectmq.com/pricing/) ## Other industries - [Manufacturing](https://connectmq.com/industries/manufacturing/) - [Automotive](https://connectmq.com/industries/automotive/) - [Utilities](https://connectmq.com/industries/utilities/) - [Renewable Energy](https://connectmq.com/industries/renewable-energy/) - [Chemicals](https://connectmq.com/industries/chemicals/) - [Pharma & Life Sciences](https://connectmq.com/industries/pharma-life-sciences/) - [Food & Beverage](https://connectmq.com/industries/food-beverage/) - [Healthcare](https://connectmq.com/industries/healthcare/) - [Transportation & Logistics](https://connectmq.com/industries/transportation-logistics/) - [Retail & E-commerce](https://connectmq.com/industries/retail-ecommerce/) - [Telecom](https://connectmq.com/industries/telecom/) - [Financial Services](https://connectmq.com/industries/financial-services/) - [Agriculture](https://connectmq.com/industries/agriculture/) ## Articles [All articles](https://connectmq.com/blog/) Managed MQTT Cloud ### [How to Choose an IoT MQTT Broker: 12 Criteria and the Questions to Ask Your Vendor](https://connectmq.com/blog/how-to-choose-an-iot-mqtt-broker/) A practical 12-point checklist for choosing an IoT MQTT broker, a table of questions to ask every vendor, and a five-minute hands-on test you can run against broker.connectmq.com. September 21, 20269 min read Managed MQTT Cloud ### [What Is a Managed MQTT Broker? Benefits, Costs and How to Choose](https://connectmq.com/blog/managed-mqtt-broker/) A managed MQTT broker lets you run IoT messaging without operating servers, certificates or patches yourself. Compare managed and self-hosted, pick a deployment model and connect your first client in five minutes. September 1, 202610 min read Industrial IoT ### [Sparkplug B and the Unified Namespace: Structuring Industrial IoT Data on MQTT](https://connectmq.com/blog/mqtt-sparkplug-b-unified-namespace/) Sparkplug B gives industrial MQTT a strict session and payload model, while a Unified Namespace gives your plant data a single, readable home. Here is how they fit together, with topic design tips and live examples. August 26, 20269 min read