An IoT gateway is an edge device that connects sensors, controllers, and machines to the cloud, translating various industrial protocols into a single, coherent data stream. In distributed deployments — from production halls to hotels — it is precisely this node that determines reliability, security, and the real cost of data transmission. In this guide we explain how an IoT gateway works, which protocols it supports, what its architecture looks like, and when to move data processing closer to the source.
In short: an IoT gateway is an intermediary between field devices and the cloud that aggregates data, translates protocols (Modbus, MQTT, LoRaWAN), and performs preliminary edge computing, reducing network traffic by as much as 60-90% and cutting latency to single-digit milliseconds.
What is an IoT gateway and how does it work?
An IoT gateway is an intermediary layer between field devices (OT) and cloud systems (IT) that collects data from many interfaces, normalises it, and forwards it over a secure channel. In practice it is a single-board computer or industrial controller running Linux or real-time firmware.
A typical flow looks like this: the gateway polls sensors (e.g. every 1-5 s), buffers the readings, filters out anomalies, and publishes aggregated telemetry to the cloud via MQTT or HTTPS. As a result, hundreds of devices appear in the backend as a single, orderly data source, rather than a chaos of incompatible buses.
It is worth distinguishing two operating modes. A transparent gateway merely forwards frames, whereas an application gateway interprets data, runs rules, and makes decisions locally. In industrial and hotel deployments the latter model dominates, because it reduces dependence on the link.
Which protocols does an IoT gateway support?
The key function of an IoT gateway is protocol translation — converting heterogeneous field buses into a common cloud protocol. A good gateway simultaneously speaks the language of old PLC controllers and modern message brokers.
- Modbus RTU/TCP — a standard in industrial automation; the gateway maps registers to MQTT topics (see our guide to Modbus retrofit to Azure).
- MQTT — a lightweight publish/subscribe protocol for cloud communication; we describe the QoS levels in our article on the MQTT protocol.
- LoRaWAN and NB-IoT — long-range LPWAN networks for battery sensors, with a range of 2-15 km in open terrain.
- Zigbee, BLE, CAN, and RS-485 — short-range and vehicle buses, supported by FSS industrial protocols.
The more interfaces a node supports, the easier it is to connect an existing fleet of machines without replacing infrastructure — this is the most common retrofit scenario in Polish industry. The gateway also isolates sensitive OT networks from the internet, acting as a controlled point of contact.
What does an IoT gateway architecture look like?
An IoT gateway architecture consists of four layers: data acquisition, edge processing, buffering, and cloud communication. Each layer can be scaled independently depending on the number of devices and latency requirements.
The acquisition layer handles the bus drivers; the edge layer runs rules, compression, and TinyML models; the buffer (store-and-forward) protects data when the link is lost; and the communication layer encrypts transmissions and manages the session. In many deployments the device also acts as an OTA firmware update point for the subordinate sensors.
When should you use edge processing on the gateway?
Edge processing pays off whenever latency, transmission cost, or data privacy are critical. A rule of thumb: the higher the sampling frequency, the more logic it is worth moving to the network edge.
Examples include vibration detection in machines (FFT analysis locally instead of sending raw 10 kHz samples), real-time control with latency below 10 ms, and filtering of video streams. A gateway can reduce volume from gigabytes to megabytes per day, which directly lowers cloud and cellular transmission bills. In practice this means lower bills and a faster system response to critical events without waiting for a reply from the cloud.
How do you secure an IoT gateway?
The IoT gateway is the most vulnerable point of the architecture, because it connects the trusted OT network with the public internet. The foundation is the zero-trust principle: every device and every connection must be authenticated and encrypted.
Recommended practices include TLS 1.3 encryption, authentication with X.509 certificates instead of passwords, secure boot with signed firmware, and network segmentation (VLAN) separating field devices from IT. It is also worth enabling signed OTA updates to prevent the loading of tampered software and hijacking of the node.
How to build an IoT gateway: hardware and firmware
The choice of hardware depends on the operating environment and the computing power needed at the edge. A microcontroller is sufficient for light tasks, while an application processor with Linux is better for analytics and containerisation.
- MCU class (ESP32, STM32) — low power consumption, firmware on FreeRTOS, ideal for simple translation and a dozen or so sensors.
- MPU/SBC class (i.MX, Raspberry Pi CM4) — Linux, Docker containers, support for hundreds of devices and AI models at the edge.
- Industrial gateways — DIN-rail enclosure, operating range -40 to +85 degrees C, redundant power supply, and 4G/5G modems.
The FSS team designs both dedicated IoT devices and firmware as well as cloud backend, which allows us to match the node class exactly to the project's requirements and budget.
Frequently asked questions (FAQ)
How does an IoT gateway differ from a router?
A router forwards packets within a single family of IP protocols, whereas an IoT gateway translates various field protocols (Modbus, LoRaWAN, Zigbee) into a common format, aggregates data, and performs edge processing. A gateway operates at higher application layers, not just the network layer, and often integrates business logic.
How much does deploying an IoT gateway cost?
The cost depends on scale and operating environment. Off-the-shelf industrial gateways cost 150-800 EUR per unit, while a dedicated device designed for a client costs 5-40k EUR for NRE plus the per-unit cost. Savings on data transmission often pay back this investment in 12-24 months.
Does an IoT gateway work without a permanent connection to the cloud?
Yes. A well-designed gateway buffers data locally (store-and-forward) and executes edge logic offline, then synchronises the backlogged telemetry once the link is restored. This is crucial in locations with unstable GSM or limited bandwidth.
Summary and key takeaways
The IoT gateway is the foundation of a scalable and secure Internet of Things architecture: it translates protocols, aggregates data, and pushes intelligence to the network edge, lowering costs and latency. A well-designed gateway combines the right class of hardware, hardened firmware, and encrypted cloud integration.
FSS has for years delivered complete IoT solutions — hardware, firmware, and cloud backend — for industry and hospitality. If you are planning a new deployment or a retrofit of an existing installation, check out our IoT integration services and let's talk about an architecture tailored to your device fleet.
{“@context”: “https://schema.org”, “@type”: “Article”, “headline”: “The IoT Gateway: Architecture and Edge Protocols”, “description”: “An IoT gateway connects sensors and machines to the cloud, translates protocols (Modbus, MQTT, LoRaWAN), and processes data at the network edge.”, “author”: {“@type”: “Organization”, “name”: “FSS”}, “publisher”: {“@type”: “Organization”, “name”: “FSS”}, “image”: “https://fss.cc/wp-content/uploads/2026/07/bramka-iot-gateway.png”, “inLanguage”: “en-US”}
{“@context”: “https://schema.org”, “@type”: “FAQPage”, “mainEntity”: [{“@type”: “Question”, “name”: “How does an IoT gateway differ from a router?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “A router forwards packets within a single family of IP protocols, whereas an IoT gateway translates various field protocols (Modbus, LoRaWAN, Zigbee) into a common format, aggregates data, and performs edge processing. A gateway operates at higher application layers, not just the network layer, and often integrates business logic.”}}, {“@type”: “Question”, “name”: “How much does deploying an IoT gateway cost?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “The cost depends on scale and operating environment. Off-the-shelf industrial gateways cost 150-800 EUR per unit, while a dedicated device designed for a client costs 5-40k EUR for NRE plus the per-unit cost. Savings on data transmission often pay back this investment in 12-24 months.”}}, {“@type”: “Question”, “name”: “Does an IoT gateway work without a permanent connection to the cloud?”, “acceptedAnswer”: {“@type”: “Answer”, “text”: “Yes. A well-designed gateway buffers data locally (store-and-forward) and executes edge logic offline, then synchronises the backlogged telemetry once the link is restored. This is crucial in locations with unstable GSM or limited bandwidth.”}}]}