Every remote site that talks to the outside world does so through one box that sits at the boundary between the local network and the wide-area link. That box is the edge router. It decides what leaves the site, over which connection, and under what security rules. This guide explains what an edge router is and the jobs it quietly handles at a remote SCADA site.
Edge Router in one line: An edge router is the device at the boundary of a local network that connects it to a wide-area network - the internet, a cellular carrier, or a private WAN. At a remote SCADA site it routes traffic between the field devices and the head end, and usually also handles the cellular modem, firewall, VPN, NAT, and failover.
A switch connects devices on the same local network and forwards frames among them; a router connects different networks and decides how traffic moves between them. The edge router is the router that faces the WAN - it separates the site's local OT network from the outside link and forwards traffic across that boundary using IP addresses and routing rules. In a small remote site, one device is often both: a router with a built-in switch for the local ports and a WAN interface for the uplink.
Because it sits at the edge, this router is where several critical functions concentrate. It runs Network Address Translation so many field devices can share one carrier-assigned IP. It enforces the firewall that controls what may enter and leave. It terminates the VPN tunnel that secures traffic to the head end. And in cellular designs, the modem and its APN, dual-SIM, and failover logic frequently live in the same box. The edge router is, in practice, the site's whole network boundary in one enclosure.
At an unmanned well pad, the edge router is usually a hardened industrial cellular router. On its LAN side it connects to the PLC, RTU, and flow computer, often through a small built-in switch. On its WAN side it holds the SIM and modem that reach the carrier. Between the two it applies NAT and firewall rules, brings up an outbound VPN to the SCADA head end, and manages failover to a backup SIM or link if the primary drops.
Increasingly these routers also do light edge computing - buffering data during outages, running store-and-forward, or hosting a protocol gateway - which blurs the line between a router and an edge gateway. The distinction is one of emphasis: an edge router's core job is connectivity and security at the boundary, while an edge gateway leans toward data processing. Many field boxes now do both.
The edge router does not originate process data - it is the conduit through which every reading leaves the site and every command arrives. If it is misconfigured, unreachable, or down, the whole site goes dark regardless of how healthy the instruments are. That makes the edge router one of the most important pieces of hardware at a remote location, and a frequent first suspect when a site stops reporting.
A cloud SCADA such as Merobix reaches the field controllers through the edge router's connection, polling them over Modbus, DNP3, MQTT, or OPC UA once the router's VPN and NAT deliver the traffic. Because the router handles the connectivity, security, and failover, the head end can stay in the cloud and simply receive whatever the router forwards. A well-configured edge router is what makes cloud-hosted SCADA practical for remote assets.
A switch connects devices on the same local network. An edge router connects that local network to a wider network like a cellular carrier or the internet, routing traffic across the boundary and typically handling NAT, firewall, VPN, and failover. Many small-site devices combine a router and a switch in one box.
They overlap. An edge router focuses on connectivity and security at the network boundary - routing, NAT, firewall, VPN, failover. An edge gateway leans toward data processing, protocol translation, and buffering. Many modern field devices do both, so the terms are often used loosely.
Because all traffic leaves and enters the site through it. A failed modem, wrong APN, misconfigured firewall or VPN, or a crashed router will take the whole site offline even if the instruments are fine, which is why it is one of the first things to check when a site stops reporting.
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.