Editions
RelayQ editions, one runtime, two deployment models.
One Runtime, Two Editions
RelayQ is one runtime in two build variants, Full for edge gateways and Lite for constrained armv7 devices (Lite omits the TLS listener, WebSocket, the terminal UI, protocol translation, the MQTT bridge and the replay journal). There are no capability tiers or artificial limitations within a variant. The edition: Evaluation or Production, is determined at runtime by the presence of a licence file and changes runtime limits, never capabilities.
| Evaluation | Production | |
|---|---|---|
| Best for | Assessment, proof-of-concept, development | Deployed systems, production infrastructure |
| License required | No | Yes (hardware-bound) |
| Runtime limit | 24 h per start · 72 h cumulative · 30 days from first run | Unlimited |
| Features | All | All |
| MQTT 3.1.1 + 5.0 broker | ✓ | ✓ |
| TLS + mTLS | ✓ | ✓ |
| Auth, ACL, audit log | ✓ | ✓ |
| Sparkplug B validation | ✓ | ✓ |
| Rules engine + historian | ✓ | ✓ |
| Device shadow + OTA | ✓ | ✓ |
| Protocol translation (Modbus + DNP3 + OPC UA + BACnet/IP), Full variant | ✓ | ✓ |
| Binary integrity (Ed25519 signed) | ✓ | ✓ |
| Support + updates | - | ✓ |
| Request Evaluation Access | ||
How it works
1. Download the build for your device. Full for gateways and servers (Linux x86_64, ARM64, ARMv7, Windows x86_64); Lite for constrained ARMv7 devices.
2. Run it. Without a license file, the runtime operates in Evaluation mode, full capabilities; 24 hours of runtime per start, 72 hours cumulative, within 30 days of the first run. The hardware fingerprint is displayed at startup.
3. Request a license. Send us your hardware fingerprint. We issue a license file bound to your hardware.
4. Deploy. Place the license file next to the binary. Restart. Unlimited runtime.
Supported Platforms
Static musl binaries for Linux, no shared libraries, plus an Authenticode-signed Windows x86_64 package. Linux covers every placement from resource-constrained edge hardware to servers; the Windows build is for the Windows machine or VM in a site's OT zone and for Windows data-centre hosts.
| Platform | Architecture | Target hardware |
|---|---|---|
| Linux x86_64 | x86_64-unknown-linux-musl | Servers, industrial PCs, edge gateways |
| Linux ARM64 | aarch64-unknown-linux-musl | Raspberry Pi 4/5, NVIDIA Jetson, ARM servers |
| Linux ARMv7 | armv7-unknown-linux-musleabihf | Raspberry Pi 3, BeagleBone, industrial ARM gateways |
| Windows x86_64 | x86_64-pc-windows-msvc | Windows machine or VM in the site OT zone beside SCADA, DCS, OPC Classic and historians; Windows data-centre hosts (Full variant, Authenticode-signed, publisher Precocity Research Limited) |
The Full variant ships the same capabilities on every architecture: TLS, WebSocket, persistence, auth, ACL, audit chain, metrics, admin, rules engine, historian, device shadow, OTA, provisioning, and Modbus + DNP3 + OPC UA + BACnet/IP protocol translation. The Lite variant (ARMv7) keeps everything except the TLS listener, WebSocket, the terminal UI, protocol translation, the MQTT bridge and the replay journal.
OEM / Embedded Licensing
RelayQ can be embedded directly into your products. OEM licensing grants redistribution rights with per-device licensing. Source access is available under separate agreement.
Use cases
- Battery monitoring and energy storage systems
- Industrial power devices and UPS
- Edge gateways connecting Modbus field devices
- Vehicle telematics and fleet management hardware
- Medical device gateways and clinical infrastructure
Frequently Asked Questions
- Are features different between Evaluation and Production?
- No. Both editions have identical capabilities. The only difference is runtime duration, capped in Evaluation (24 h per start, 72 h cumulative, 30 days from first run) vs unlimited in Production.
- How do I get a license?
- Run the binary. It prints your hardware fingerprint at startup. Send us the fingerprint and we issue a license file bound to that hardware.
- What happens after 24 hours in Evaluation?
- RelayQ shuts down gracefully, connections are drained, data is flushed to disk, and a clear message is logged, and you can restart it for another 24 hours. Remaining time in the current session is published on
$SYS/broker/evaluation/remaining_secs. Across restarts, Evaluation allows 72 hours of cumulative runtime within 30 days of the first run; after that the runtime will not start without a licence. - What happens when my license expires?
- A running instance will not be remotely disabled, we do not kill live deployments. However, if the runtime restarts after license expiry (power cycle, watchdog, maintenance), it will fail license validation and will not resume. For safety-critical or always-on deployments, renew before expiry or maintain a valid license file on the host.
- How is RelayQ delivered?
- As a tarball containing a self-contained static binary, a config file, and an optional install script that registers a systemd service. No package manager, no external runtime dependencies. Extract, configure, and run, or use the installer for managed systemd deployment.
- Can I get source access?
- Source access is available under a separate written agreement, subject to additional terms and confidentiality obligations. Contact us to discuss terms.
- Does RelayQ support MQTT 5.0?
- Yes. RelayQ implements the full MQTT 5.0 specification alongside MQTT 3.1.1, both protocol versions on the same listener, with every normative statement traced to a test and exercised on the signed release binary.