Editions
RelayQ editions — one runtime, two deployment models.
One Runtime, Two Editions
RelayQ is a single binary with full capabilities in every deployment. There are no capability tiers, no artificial limitations, and no stripped-down versions. The edition is determined at runtime by the presence of a license file.
| Evaluation | Production | |
|---|---|---|
| Best for | Assessment, proof-of-concept, development | Deployed systems, production infrastructure |
| License required | No | Yes (hardware-bound) |
| Runtime limit | 24 hours per start | Unlimited |
| Features | All | All |
| MQTT 3.1.1 broker | ✓ | ✓ |
| TLS + mTLS | ✓ | ✓ |
| Auth, ACL, audit log | ✓ | ✓ |
| Sparkplug B Aware | ✓ | ✓ |
| Rules engine + historian | ✓ | ✓ |
| Device shadow + OTA | ✓ | ✓ |
| Protocol translation (Modbus + DNP3 + OPC-UA) | ✓ | ✓ |
| Binary integrity (Ed25519 signed) | ✓ | ✓ |
| Support + updates | - | ✓ |
| Request Evaluation Binary | ||
How it works
1. Download the binary. One binary, full capabilities, all architectures.
2. Run it. Without a license file, the runtime operates in Evaluation mode — full capabilities, 24-hour runtime per start. 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
RelayQ is available as a single full-featured binary for all major architectures.
| 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-gnueabihf | Raspberry Pi 3, BeagleBone, industrial ARM gateways |
All architectures ship the same capabilities: TLS, WebSocket, persistence, auth, ACL, metrics, admin, rules engine, historian, device shadow, OTA, provisioning, and Modbus + DNP3 + OPC-UA protocol translation.
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 — 24 hours (Evaluation) vs unlimited (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. Restart it for another 24 hours. There is no cumulative limit.
- What happens when my license expires?
- Your deployed runtime continues to run indefinitely. Core operation never stops. What expires is your support and update entitlement.
- How is RelayQ delivered?
- As a self-contained binary. No installer, no package manager, no external dependencies. Copy the binary, provide a config file, run it.
- Can I get source access?
- Source access is available under a separate written agreement, subject to additional terms and confidentiality obligations.
- Is MQTT 5.0 on the roadmap?
- Yes. MQTT 5.0 support is planned for 2027.