The Problem
Automotive edge computing demands brokers that fit in constrained ECUs, survive power cycles, and pass ISO 21434 cybersecurity audits. EMQX won’t fit. Mosquitto can’t prove memory safety. Neither validates Sparkplug traffic.
How RelayQ Solves This
826KB binary. Fits on any ARM-based ECU or gateway alongside your application code. No runtime, no interpreter, no garbage collector.
Memory safe by construction. Rust eliminates buffer overflows, use-after-free, and data races at compile time. 14 unsafe blocks total — all in OS interface wrappers, none in protocol handling.
Formally verified. Independent mathematical verification of protocol state machines, concurrency models, and 6M-input fuzz campaign on the packet codec. Evidence your ISO 21434 auditor can reference.
Key Features for Automotive
| Feature | Benefit |
|---|---|
| 826KB binary (no TLS) | Fits on constrained ECUs |
| mlockall + CPU affinity | Deterministic latency for real-time paths |
| Zero dependencies | Trivial SBOM for ISO 21434 |
| WAL persistence | Survives ignition cycles |
| Cross-compiled (ARM64, ARMv7) | Runs on any automotive-grade SoC |
| <50ms startup | Ready before vehicle systems initialize |
Deployment
- In-vehicle gateway: Static binary on QNX/Linux BSP
- Charging station controller: Docker on ARM64 edge compute
- Fleet management edge: systemd service on ruggedized hardware
Next Steps
Ready to evaluate RelayQ?
Full-featured pilot. No credit card. Direct support.
Start Free 90-Day Pilot