The Problem
Railway signalling and fleet management systems operate for 20–30 years. Every software component must be maintainable, auditable, and free from supply-chain risks that compound over decades. A broker with 200 dependencies today will have 200 potential vulnerabilities to track for the next 25 years.
How RelayQ Solves This
Long-lifecycle design. Zero dependencies means zero dependency maintenance over the system’s 20+ year life. No forced upgrades, no abandoned crates, no breaking API changes from upstream.
EN 50128 evidence path. Independent formal verification and comprehensive protocol test coverage provide evidence that maps to EN 50128 Software Safety Integrity Levels.
Power-cycle resilient. WAL persistence survives unexpected shutdowns. < 50ms startup means the broker is ready before the train’s systems finish initializing.
Key Features for Railway
| Feature | Benefit |
|---|---|
| Zero dependencies | No supply-chain maintenance over 20+ year lifecycle |
| WAL persistence | Messages survive power loss |
| < 50ms startup | Ready before vehicle systems initialize |
| Formal verification | EN 50128 SIL evidence |
| 826KB binary | Fits on trackside controllers |
| Rate limiting | Prevents sensor floods from disrupting signalling |
| OOM protection | Never crashes — graceful degradation |
Deployment
- Trackside controller: Static binary on ruggedized Linux
- On-board gateway: Embedded in train communication system
- Fleet management: Docker container at operations centre
Next Steps
Ready to evaluate RelayQ?
Full-featured pilot. No credit card. Direct support.
Start Free 90-Day Pilot