The fleet
The machines themselves: the overlay network, every seat and its measured headroom, the fleet's own events, and what it remembers.
Every screen in this group is (Advanced).
About the pictures on this page. They are rendered from the built console over a demonstration data set, not from a live fleet — a screenshot of somebody's real record would publish their work. What the pictures are evidence of is the layout, the chips and the acts; every number in them is sample data.
Mesh
The machines on the overlay network: provider, tailnet, whether the control plane is reachable, egress-mesh dials allowed and refused today, telemetry posture. A tile row counts them — on the mesh · admitted · on the mesh but not admitted · direct or relayed · reach policy revision — and the table carries machine, role, mesh name and address, path, admitted, trusted since, seats.
Mesh membership is not admission. A machine can be reachable and still refused work until it is admitted with its binaries and its class.
Acts: the reach policy with its revision, and Add a machine.
Machines and seats
Every seat on every admitted machine: backend, model, the last measured usage window, sessions and
headroom — always with the instant it was measured, never a stale number presented as
current.
See Machines and seats for what a seat is, and Roles for how the fleet chooses one.
Log
The fleet's own events, filterable by machine, kind and time.
Memory
What the fleet remembers per repository and per role — the lessons a second leg reads before it
starts.
