Documentation

Central Management

Outbound-only by design: the firewall dials out, the hub never dials in.

The free Orchestrator download is the fleet hub — it isn't a Business+ license feature. The firewall opens an outbound sealed channel; the hub never connects in, and enrolling adds no management listener on the box.

  • No inbound attack surface — no management port to scan, exploit or brute-force.
  • Works behind NAT/CGNAT — no inbound rules or port forwards.
  • Instant revocation — drop a device at the hub and its channel is dead.

Channel security

On top of TLS, payloads are sealed end to end with the device's identity key against the hub's pinned public key, so confidentiality and integrity survive a TLS-terminating load balancer. The agent refuses any peer that isn't the pinned one. The device identity key lives in the secret store, referenced by name. Validation refuses a hub URL that isn't HTTPS and requires a device id, identity key reference and pinned hub key before the feature can be enabled.

What the hub can do — per feature

Each capability is a separate toggle, so you can enroll for telemetry only. Capabilities include getting, committing and rolling back configuration (through configd's control API, with full validation and auto-rollback), reading active configuration and runtime state, pulling a disaster-recovery backup (the active revision), and the same image and service controls as a local operator.

Every hub-initiated change goes through configd's local control API — the same validate → render → apply → confirm/rollback path as a local change. The agent is a transport, not a second writer.

Installing the hub

# Debian/Ubuntu amd64 unzip orchd-*-linux-amd64.zip sudo ./install.sh --admin <user> # then enroll firewalls and pin the hub key

Something unclear? Tell us and we'll improve this page.