Product Roadmap

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

The core remains unchanged: a single, dependency-free runtime 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

Core runtime is production-ready and in active pilot deployments, with General Availability targeted for Q3 2026.

Core Runtime

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

MQTT 3.1.1 Broker
Full QoS 0/1/2, retained messages, Will, session persistence, WAL
Sparkplug B Aware
Topic validation, metric stability, bdSeq detection, birth/death sequencing
Zero Dependencies
<1MB binary, ~2.8MB container, trivial SBOM, no supply-chain risk
Formally Verified
Mathematical proofs, concurrency analysis, 6M-input fuzz, 1,837+ tests
Production Security
TLS 1.3, mTLS, ACL, brute-force protection, IP filter, rate limiting, audit log
Full Observability
Prometheus, $SYS, health checks, admin API, JSON logs, systemd watchdog

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
Q3 2026

General Availability

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

  • Platform management UI — browser-based administration
  • Stable API and configuration format
  • Long-term support (LTS) commitment
  • Production deployment guides and runbooks
  • Commercial support and SLA options
Post-GA

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
2027

Extended Capabilities

MQTT 5.0
Adds advanced protocol capabilities while preserving the same execution model
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
  • • A dependency-free runtime

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

Request Evaluation Access