Drivers Beside the Wires
Serial and Ethernet drivers run on the gateway, so RS-485 trunks and local networks never need to be exposed.
The edge gateway sits on the equipment network, speaks each protocol natively, and forwards clean data upstream. Collection continues when the uplink does not.

Protocols such as Modbus RTU, BACnet MS/TP, KNX and DALI live on local networks, often on RS-485 cabling that does not reach the internet on its own. An edge gateway runs the drivers where the wires are, so only signed, normalized readings travel across the internet.
Serial and Ethernet drivers run on the gateway, so RS-485 trunks and local networks never need to be exposed.
If the uplink drops, readings are buffered on the gateway disk up to a size limit and sent in order when the connection returns.
The gateway connects outward to IoTServa, so no inbound ports are opened to the equipment network.
Ports, devices, Nodes and polling are set in IoTServa and sent to the gateway as a signed bundle, so there are no local settings to drift.
One command installs the gateway and pairs it automatically. Signed updates then roll out in stages and roll back on their own if a new version fails its checks.
Run on a DIN-rail gateway or an industrial PC that you already own or buy separately.
The gateway runs on 64-bit Linux, for example Ubuntu on an industrial PC or a Raspberry Pi class board, with a Windows service for sites that standardize on Windows. The Standalone System Screen Scraper reads systems that have no data interface.
Reads serial lines through a port or USB converter, and reads DALI lighting through a DALI gateway or controller.
Requests are grouped and timed per bus, so slow serial trunks stay responsive.
Critical Rules run on the gateway itself, so alarms and interlocking actions keep working when the internet is down.
Manage Ethernet, Wi-Fi and cellular links from the cloud, with automatic failover to 4G or 5G when the main line drops.
Run camera analytics and anomaly models on an edge AI box at the site, sending only events upstream.
See every serial port the gateway found, add one with a click, watch live traffic and get a plain-language diagnosis when a bus is silent.
Run step-by-step checks with a plain fix for each failure, and read one register once to prove the wiring before you add Nodes.
Approved support staff can open a recorded terminal on a gateway from the browser, over the same outbound connection, with idle and session time limits.
Each gateway gets a one-line install command with an eight-character code, and the console shows install progress live.




Screens from the live IoTServa software with a demo company and demo data.
Yes, for sources that are already reachable over IP, such as an MQTT broker, a BACnet/IP network or a LoRaWAN network server. Serial and local-only networks need a gateway on the site, and systems with no data interface use the Windows Standalone System Screen Scraper.
It runs as a headless background service that starts on boot and keeps collecting without anyone logged in. A local commissioning page on the gateway is used to pair it and check its status; everything else is configured from the cloud.
A 64-bit Linux computer on amd64 or arm64, such as an industrial PC or a 64-bit Raspberry Pi class board, with the right ports: RS-485 for serial devices and Ethernet for IP devices.
Replace it from the console. The new gateway takes over the same devices and Nodes, so history and alert rules are kept. Sensors and screen scrapers can be replaced the same way.
See VYROX Hardware or Read the Protocol Guides
Tell us which protocols are on site. We will scope a pilot that reads your real devices.