Router vs Gateway in Industrial IoT: What to Use and When
Router, IoT gateway, protocol gateway, or edge computer? What each device actually does, how their roles overlap, and a plain decision guide for industrial connectivity.
Four words used as if they mean the same thing
Router, gateway, protocol gateway, edge computer. In industrial connectivity these four terms get swapped around as if they were interchangeable, and the marketing on the boxes does not help. They overlap, but they are not the same, and choosing the wrong one means either paying for capability you never use or hitting a wall the day you need to read a sensor.
The clearest way to tell them apart is by the job each one is built to do. Start from the job, not the label on the datasheet.
What a router does
A router moves IP traffic between networks. In the field that usually means an industrial cellular router: it takes a local Ethernet or Wi-Fi network on the machine and connects it to the internet over LTE or 5G, with a VPN back to your servers and a firewall in front.
A router is about connectivity, not content. It does not understand Modbus, it does not read a temperature sensor, and it does not know what a work order is. It moves packets reliably from one side to the other. If all you need is to put a machine that already speaks IP onto the network, a router is the right and cheapest answer.
What an IoT gateway adds
An IoT gateway sits one layer deeper. It connects devices that do not speak IP (sensors, controllers, meters) to a platform or cloud, and it usually carries its own connectivity on board, which is why a cellular IoT gateway and a cellular router can look identical from the outside.
The difference is what happens to the data. A gateway reads the field protocol, normalizes the readings, applies a little logic (filtering, thresholds, buffering when the link drops), and publishes structured data upward, typically over MQTT. It bridges the machine world and the IP world. A router connects networks; a gateway connects devices to systems.
Protocol gateways and edge computers
Two more roles sit around the gateway:
A protocol gateway (or protocol converter) is specialized translation. Modbus RTU to MQTT, BACnet to REST, CAN to a serial line. It may not provide any wide-area connectivity at all; its whole job is to make one protocol speak another, often inside a panel.
An edge computer is a small computer in a rugged enclosure. It can do everything above and then run real applications: containers, local analytics, machine learning, a local database. You reach for one when the logic at the edge is too heavy for a gateway and waiting on the cloud is not an option.
Where the roles overlap
The reason the words blur is that a single capable box often fills several of these roles at once. An open Linux gateway with a cellular modem is a router, a protocol gateway, and a lightweight edge computer in one unit, decided by the software it runs rather than by the hardware category on the box.
The table below is the honest version: most devices are strong in one or two columns and partial in the rest.
| Capability | Cellular router | IoT gateway | Protocol gateway | Edge computer |
|---|---|---|---|---|
| Network connectivity (cellular, WAN) | ||||
| Routing, VPN, firewall | ||||
| Protocol translation (Modbus, CAN, BACnet) | ||||
| Reads sensors and field I/O | ||||
| Local processing and buffering | ||||
| Runs custom applications |
A plain decision guide
Match the device to the job:
- The machine already speaks IP and just needs to be online. Use an industrial cellular router.
- You need to get sensor, PLC, or meter data to a platform. Use an IoT gateway.
- Two systems on site speak different protocols and need to talk. Use a protocol gateway.
- You need real computation at the edge (analytics, local control, offline operation). Use an edge computer, or a gateway powerful enough to run your application.
When the requirements span several of these, an open Linux gateway is usually the economical choice, because you add roles in software instead of adding boxes. See our routers and gateways, the connectivity side on M2M connectivity, and the data side on condition and process monitoring.
Frequently asked questions
What is an IoT gateway? A device that connects field equipment to a platform or cloud, translating the machine's protocol into structured data and usually carrying its own cellular or wired connectivity.
What is the difference between a router and a gateway? A router connects networks and moves IP packets. A gateway connects devices to systems and understands the data, translating protocols and publishing structured readings. Many cellular gateways include a router inside them.
Do I need both a router and a gateway? Often no. A capable IoT gateway with a cellular modem provides the routing function too. You only need both when you want to keep network management and data handling on separate devices.
What is a cellular gateway? An IoT gateway with a built in LTE or 5G modem, so it connects field devices to the cloud over the mobile network without a separate router.
Build your industrial telemetry solution.
Discuss embedded gateway delivery, telemetry pipelines, and customer-owned IP with our team.


