VÖRNCONTROL PLANE

Operator console

Authenticate with the tenant and operator token issued when the tenant was created. The token is kept in this browser only and sent as a bearer header to this control plane.

AGENTS·
ONLINE·
OFFLINE·
POLICY DRIFT·
UPDATE FAILURES·
DESIRED POLICY·
EGRESS ENFORCEMENT PATH
WORKLOAD local models WORKLOAD apps · cloud AI VÖRN egress proxy :7433 loopback POLICY engine default-deny ALLOW → internet DENY unapproved AI

NEEDS ATTENTION

PLAN & ENTITLEMENTS

SEATS

HOSTOS / ARCHVERSIONSTATUS POLICYDENIES 24HWORKLOADSLAST SEEN
Loading fleet…

ENROLL A WORKSTATION

Onboard a host by minting a one-time enrollment token, installing the Vörn agent as a native service, and pointing it at this control plane. The host self-enrolls on first start and appears under FLEET within about a minute.

Generate an enrollment token

Tenant-scoped and single-use. The host credential minted from it only ever reaches this tenant, so a token handed to the wrong host still cannot cross tenants.

Download the agent and install it as a service

One static binary, no dependencies. Download it for the target machine, drop in the config block above, and start it. Pick the OS:

Place the binary:

chmod +x vorn-linux-amd64
sudo mv vorn-linux-amd64 /usr/local/bin/vorn

Create /etc/vorn/config.yaml with:

Register and start the systemd service:

sudo vorn install

Verify your download against SHA256SUMS.

Confirm a good connection

  • The agent log shows enrolled as <id> with . Linux: journalctl -u vorn -f · macOS: the vorn log file, or log stream --predicate 'process=="vorn"' · Windows: the log file or Event Viewer.
  • The agent's local health endpoint returns ok: curl http://127.0.0.1:7433/healthz gives {"status":"ok"}. Loopback only; the agent is headless with no web UI.
  • Within about 60 seconds the host appears under FLEET with status active and a recent last-seen that keeps advancing as heartbeats arrive.
Waiting for the first host to connect…
TIMEAGENTMODULEKIND DECISIONSEVERITYRULETARGET
Loading events…

ACTIVE POLICY

DEFAULT POSTURE

RULES

First match wins, top to bottom. When no rule matches, the default posture applies.
Publishing bumps the version, records the structural diff in the audit trail, and queues a signed push to every active agent. Agents ack when applied; drift is visible on the fleet view.
ADVANCED · EDIT RAW POLICY
Full policy JSON, synced from the guided editor above when you expand this. Power-user path: supports fields the guided editor keeps read-only (cidr, ports, protocol).

VERSION HISTORY

VERSIONBYCOMMENTAT
Loading…
What AI ran across the fleet and where it talked. Built from the event lake; nothing here was blocked.
Loading shadow-AI report…
Every operator mutation, immutably recorded.
TIMEACTORACTIONRESOURCEFROM
Loading audit trail…