Drivers Beside the Wires
Serial and Ethernet drivers run on the gateway, so RS-485 trunks and local networks never need to be exposed.
Platform
Edge Gateway
The edge gateway sits on the equipment network, speaks each protocol natively, and forwards clean data upstream. Collection continues when the uplink does not.
Why It Matters
Protocols such as Modbus RTU, BACnet MS/TP and KNX live on local networks, often on RS-485 cabling that cannot leave the building. An edge gateway runs the drivers where the wires are, so only normalized tags travel across the internet.
- Reads BACnet, Modbus, KNX and MQTT locally
- Receives LoRaWAN and BLE data from gateways on the site
- Holds data during outages and forwards it in order
- Connects outward only, with TLS
What It Does
Store and Forward
If the uplink drops, readings are held on the gateway and sent in order when the connection returns.
Outbound Connections Only
The gateway connects outward to IoTServa, so no inbound ports are opened to the equipment network.
Remote Configuration
Devices, profiles and polling are managed from IoTServa, not by visiting each site with a laptop.
Industrial Hardware or Your Own PC
Run on a DIN-rail gateway or an industrial PC that you already own or buy separately.
Polite Polling
Requests are grouped and timed per bus, so slow serial trunks stay responsive.
Edge Gateway Questions
Can IoTServa run without an edge gateway?
Yes, for sources that are already reachable over IP, such as an MQTT broker or a LoRaWAN network server. Serial and local-only networks need a gateway on the site.
What hardware does the gateway need?
A small industrial computer or DIN-rail gateway with the right ports, such as RS-485 for serial devices and Ethernet for IP devices.
More From the Platform
Start With One Site. Prove It on Real Devices.
Tell us which protocols are on site. We will scope a pilot that reads your real devices.