Command Center

On-premise control plane for enrolling, monitoring, and updating fleets of RelayQ edge devices. In development; evaluation opens at release candidate.

One control plane for the whole fleet

RelayQ Command Center is an on-premise control plane that manages fleets of RelayQ edge devices, from ten to a thousand, from a single operator server on your network.

It follows the same failure-containment principle as the runtime itself: edge devices operate independently. Command Center enrols, observes, and updates them; it never sits in the data path. If it stops, every edge device keeps collecting and delivering data exactly as before.

RelayQ Command Center dashboard, fleet health trend, device status counts, and active jobs The Command Center dashboard: fleet health at a glance, active rollouts, and change-impact correlation.

What it does

Device registry & enrolment

Every device enrols over TLS with its own revocable credential, no shared secrets in the fleet. Track identity, status, version, and last check-in.

Signed configuration distribution

Config bundles are cryptographically signed before they leave the control plane. Devices verify signatures before applying anything.

Fleet health monitoring

Aggregated heartbeats and health scores across the fleet, with per-device drill-down and change-impact correlation after every rollout.

Staged rollouts with rollback

Version updates deploy in canary and wave phases. Any phase can be rolled back, failure containment applied to change management.

License management

Issue, rotate, and revoke hardware-bound licenses across the fleet without touching individual devices.

Dashboard & REST API

A real-time web dashboard for operators, and a REST API for CI/CD and automation.

Command Center fleet view, device table with status, version, architecture, and health score
Fleet view, status, version, and health score per device
Command Center rollouts view, staged canary and wave deployment with per-phase progress and rollback
Staged rollouts, canary and wave phases, rollback at any point

Deployment model

  • A single binary on an operator server at the site centre, no external database, no cloud dependency
  • Communicates with edge devices over MQTT through the RelayQ runtime
  • Works in air-gapped networks; nothing calls home
  • Optional by design: RelayQ edge devices are fully functional without it

Availability

Command Center is in development and not yet available for evaluation. Evaluation access opens when it reaches release-candidate stage; the roadmap targets a fully supported release at General Availability (Q4 2026), alongside the runtime’s LTS commitment. If fleet management matters to your deployment, mention it in your evaluation request.

Ready to evaluate RelayQ?

Full-featured runtime. No credit card. Direct support.

Request Evaluation Access

Not ready to talk? Start with the evidence: conformance report · benchmarks