Product Roadmap

RelayQ is a deterministic industrial edge runtime evolving into a full edge system for controlled, failure-safe data processing.

The core remains unchanged: a single runtime with zero mandatory dependencies that enforces bounded behavior under real-world conditions. New capabilities extend that model without introducing external components or new failure domains.

Direction

All future development follows a single principle: expand capability without introducing new failure domains.

• Preserve bounded behavior
• Avoid external dependencies
• Keep failure isolated
Today

Pilot Available · v3.0.0-rc.2

The core runtime is available for pilot deployment today as a release candidate, with General Availability targeted for Q4 2026.

Non-intrusive by design, RelayQ never modifies the control system. It observes, structures, and delivers. If RelayQ stops, your plant continues.

Core Runtime

The foundation is a production-grade deterministic runtime with the following characteristics:

MQTT 3.1.1 and 5.0 Broker
Full QoS 0/1/2, retained messages, Will, session persistence, WAL; MQTT 5.0 on the same listener, 269 of 277 normative statements verified
Sparkplug B
Topic-shape and session validation (bdSeq staleness, birth/death sequencing) enforced at ingress
Zero Mandatory Dependencies
std-only core, TLS optional via rustls; ~4.6 MB Full binary, ~1.0 MB Lite binary, ~4.6 MB container
Verified Under Adversarial Conditions
4,902 automated tests traced to the protocol specifications, 6M fuzz inputs, Kani model checking and Loom concurrency analysis on the core state machines
One Security Pipeline
Principal → Authoriser → hash-chained audit file; TLS 1.2/1.3, mTLS, default-deny ACL, brute-force lockout, IP filter, hardened deployment profile
High Availability
Two-node primary/standby with WAL replication, role-aware $SYS topics and Prometheus metrics
Full Observability
Prometheus, $SYS, health checks, admin API, JSON logs, systemd watchdog
Linux and Windows
Signed builds for x86_64, aarch64 and armv7 Linux; Windows x86_64 packages

Edge Capabilities

All data processing is executed locally within the same runtime:

Local Rules Engine
Evaluate and route data at the edge without cloud round-trips
Device Shadow
Last-known state tracking for each connected device
Data Historian
Local buffering and time-series storage at the edge
Hardware-bound Licensing
License tied to device identity, no call-home required
Command Center (in development)
Fleet enrolment with per-device credentials over TLS, check-in, OTA and rollouts from a separate controller

Command Center in action

Fleet enrolment, health monitoring, and staged rollouts from an on-premise control plane, in development, with evaluation opening at release-candidate stage. Edge devices operate independently without it.

Command Center dashboard, fleet health trend and active jobs
Dashboard
Command Center fleet view, device status, version, and health score
Fleet
Command Center staged rollout with canary and wave phases and rollback
Staged rollouts

Explore Command Center →

Q4 2026

General Availability

Production-grade release with full documentation, support SLAs, and commercial licensing.

  • ○ Command Center from release candidate to supported release
  • ○ Stable API and configuration format
  • ○ Long-term support (LTS) commitment
  • ○ Production deployment guides and runbooks
  • ○ Commercial support and SLA options
Pilot Ready

Protocol Translation

RelayQ moves protocol handling into the runtime itself, eliminating external gateway layers.

Modbus/TCP Translation ✓
Poll legacy PLCs and publish register values as MQTT topics
Modbus RTU Translation ✓
Serial RS-485 device integration over MQTT
DNP3 Translation ✓
Utility and energy protocol translation for substation and grid devices
OPC UA Translation ✓
Native OPC UA client for industrial automation systems, translating node data to MQTT topics
BACnet/IP Translation ✓
Native BACnet/IP client, BBMD, COV subscriptions, ReadPropertyMultiple, write-back, for building and facility systems
Exploring

Extended Capabilities

Clustering (exploratory)
Investigating multi-node operation without introducing unbounded state or cross-node failure propagation

Clustering will not compromise the single-node guarantees by default. Any clustering model must preserve deterministic behavior, bounded resource usage, and predictable failure modes.

Single Runtime, Two Editions

RelayQ is a single binary with full capabilities in every deployment. There are no capability tiers or reduced versions. The edition is determined at runtime by the presence of a valid license file.

Evaluation · Full capabilities, 24-hour runtime per start, no license file needed.
Production · Unlimited runtime, hardware-bound license file, support + updates.

View full edition details →

RelayQ's roadmap is not additive; it is disciplined.

  • • Bounded behavior
  • • Isolated failure
  • • Zero mandatory dependencies

Evaluate the runtime under real-world failure conditions, not just ideal scenarios.

Request Evaluation Access