Disk-Aware Offline Buffer
Readings wait in a local store sized from the free disk space, with a floor and a ceiling, and stop growing before the disk runs low.
Every gateway keeps collecting through an outage and uploads the backlog in order when the line returns. Local Rules run your critical automation on the gateway itself, with no internet at all.

Rural plants, estates and basements lose their connection more often than anyone admits. A gap in the data hides what happened, and an automation that lives only in the cloud stops the moment the line drops. IoTServa keeps both on the site: the data waits safely on disk, and the rules that protect the equipment keep running.
Readings wait in a local store sized from the free disk space, with a floor and a ceiling, and stop growing before the disk runs low.
When the uplink returns the backlog is sent oldest first with backoff, so the cloud is never flooded and nothing arrives out of order.
Many readings travel in one message during a long outage, so hours of data catch up in minutes.
If the buffer ever has to drop the oldest readings, the gap is recorded with its start, end and size and shown on the gateway page, never silently hidden.
Each gateway shows readings waiting, oldest waiting age, disk used and its connection state, and the AI assistant can tell you what is still waiting.
A Rule that watches a value and switches an output is compiled in the cloud, signed, and run on the gateway, so it works with the internet down.
Local Rules switch on an edge with hysteresis and a hold time, only inside the time windows you set, so outputs never chatter.
Every local write passes the gateway's own signed limits. Turning a rule off or pressing the kill switch never moves an output by itself.
Each local rule action is recorded with its real time and uploaded with the buffer, so the history is complete after an outage.
The gateway talks to Controller8 relay boards over the local network, checking the board identity before every write, so relays switch with no internet.


Screens from the live IoTServa software with a demo company and demo data.
The gateway keeps reading every device and stores the readings on its own disk. When the connection returns it uploads them oldest first, so charts and reports have no hole.
It depends on the disk and how many values are read. The buffer is sized from the free space with a floor and a ceiling, and the gateway page shows how much is waiting and how long it can last.
Yes. Local Rules are compiled and signed in the cloud and run on the gateway. A rule that switches a heater or pump on a temperature keeps working offline and reports what it did when the line returns.
Every local write is checked against signed limits on the gateway, uses hysteresis and a hold time, and turning a rule off never switches the output by itself.
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.