Solutions
RelayQ for systems where failure must be contained, not propagated.
Where RelayQ Fits
RelayQ is a deterministic edge runtime for industrial data systems that brings industrial equipment (Modbus, DNP3, OPC UA, BACnet/IP) and IoT sensors (MQTT, Sparkplug B) into one data path.
It is built for teams running critical data infrastructure at the edge: plant floors, substations, vehicles, hospitals, water networks, and rail systems. These teams all face the same reality: their systems must continue operating even when individual devices fail, stall, or misbehave.
The Core Problem
Across critical infrastructure, one pattern repeats:
- Failures propagate: a single misbehaving device can affect unrelated systems.
- Dependencies introduce risk: every external library is a door you can’t lock.
- Edge conditions are unpredictable: power loss, connectivity gaps, and device faults are routine.
- Traditional MQTT brokers don’t isolate failure: they forward messages regardless of correctness or system state.
How RelayQ Changes This
RelayQ enforces controlled behavior in the data path:
- Each device is isolated, one failure cannot impact others
- Each connection is strictly bounded, no slow client can stall the system
- An acknowledged QoS 1 message is written to disk before the acknowledgement, so a power loss after the acknowledgement does not lose it
- Third-party code is limited to the optional TLS stack
These guarantees are enforced by architecture, not configuration.
Industry Solutions
Industrial Automation
Failure containment for factory floors and SCADA systems. Sparkplug B traffic with the wrong topic shape, namespace/version, or message type is rejected at ingress. Misbehaving devices cannot corrupt downstream data.
Energy & Smart Grid
A parallel telemetry path beside grid SCADA that keeps operating across substation outages and compromised field devices. No single device can disrupt grid-wide telemetry.
Railway & Transportation
A non-vital telemetry copy of trackside and onboard status that stays consistent across communication drops and equipment failures, outside the path to interlocking logic.
Automotive & EV Edge
Predictable system behavior across connectivity loss and ECU restarts. No slow or disconnected vehicle can stall the pipeline.
Medical Devices & Healthcare IoT
Non-alarm device telemetry that keeps flowing when equipment malfunctions. No malfunctioning monitor can stall other devices’ data streams.
Water & Wastewater
Distributed infrastructure telemetry that remains stable across remote site disconnections and sensor faults, with native Modbus RTU/TCP and DNP3.
Common Outcomes
Systems that remain operational despite device failures
Faster isolation when components misbehave
Shorter compliance cycles from auditable, minimal SBOMs
Predictable behavior under real-world conditions, not just ideal ones