The word gateway gets attached to many products, but the core idea is one thing: the controlled point where one network hands data to another. In OT, that point does a lot of work.
SCADA Gateway in one line: In SCADA and OT networks a gateway is a device or node that connects two different networks and passes data between them - typically bridging field-level devices to a higher-level SCADA, historian, or cloud system. Beyond forwarding traffic, an industrial gateway usually translates between protocols, aggregates data from many local devices, buffers it against connectivity loss, and enforces security at the boundary between operational and business networks.
At its simplest a gateway is a junction between two networks. In IT that is often a router. In OT the term implies more, because the two networks usually differ not just in addressing but in protocol, trust level, and reliability. An industrial gateway typically speaks the field protocols on its downstream side - Modbus, DNP3, EtherNet/IP - and a different, often IP-based protocol on its upstream side toward SCADA or the cloud.
A capable gateway aggregates: it collects data from many local devices and presents them upstream as a single consolidated source, so the SCADA connects to one gateway instead of dozens of individual devices. It also buffers, holding data locally when the upstream link is down and forwarding it on reconnection. And it is the natural place to enforce security policy, since it is the one controlled path between zones.
The name is qualified by role. A protocol gateway focuses on translating between industrial protocols. A cellular or field gateway provides the wireless link from a remote site back to the network. An edge gateway runs local processing - filtering, deadband, even analytics - before sending data on. A cloud or IoT gateway is oriented toward pushing field data up to a cloud platform, usually over an outbound, encrypted connection.
These roles overlap constantly, and one physical box often plays several at once: a single unit at a well pad might terminate the cellular link, translate Modbus to a cloud protocol, buffer during outages, and encrypt the uplink. The right question is not what a gateway is called but which of these functions it actually performs in a given design.
In a distributed production operation the gateway is where a site's data leaves the field. Each pad or facility typically has a gateway (or a gateway function inside its RTU) that gathers local instrument data, buffers it against the frequent connectivity gaps of remote sites, and forwards it upstream over cellular, radio, or satellite. Getting this node right largely determines a site's data reliability.
The gateway is also the security control point between the OT network and anything outside it. A well-designed field gateway makes only outbound connections, so no inbound port is exposed to the internet, and it authenticates and encrypts its uplink. This lets a site publish its data without becoming a way in - the same reasoning that puts firewalls and data diodes at higher-consequence boundaries.
Because the gateway aggregates and translates, it also insulates the upstream system from field-level detail. The SCADA or cloud platform sees a clean, consistent data stream regardless of the mix of legacy and modern devices behind the gateway, which is what makes mixed-vendor brownfield sites manageable.
A router forwards IP packets between networks. A gateway is a broader term: in OT it usually also translates protocols, aggregates device data, buffers during outages, and enforces security at the boundary. Every gateway routes in some sense, but not every router is doing a gateway's job.
Usually yes - some node at each site must read local devices and forward their data. Merobix connects field PLCs and RTUs to the cloud through a local gateway function that buffers data during connectivity loss and uses outbound-only, encrypted connections so no inbound port is exposed.
Because it is the one controlled path between the field network and everything outside it, it is the natural place to enforce policy. A well-built field gateway makes only outbound connections and encrypts its uplink, so a site can send data out without exposing a way in.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.