Fleet Management

Hardware test labs rarely outgrow their first box — they outgrow their first ten. Once a fleet spans multiple benches, sites, or subsidiaries, engineers lose the ability to answer basic questions: which boxes are online, which instruments are wired to which net, who is using what, and which version of the Lager runtime each box is running. Stout closes that visibility gap with a single dashboard that continuously probes every registered Lager box and surfaces status, capabilities, and connected hardware in real time.

Each box reports a heartbeat every 30 seconds over an authenticated WebSocket channel. The control plane marks a box offline after 10 minutes of silence and emits an alert; when it comes back, its devices, nets, and host metadata are refreshed automatically. You can see USB instruments, configured nets, running firmware versions, and attached webcams without SSHing into anything. Bulk import a CSV of existing boxes and Stout will probe their HTTP ports, verify Lager is reachable, and register them against your organization with the right team assignments.

Resource locking prevents the classic two-engineers-one-oscilloscope problem: a lock records who acquired the box, when, and for what job, and the CLI and dashboard both surface the current holder so nobody interrupts an in-flight test. Locks release automatically on job completion or after an idle timeout. Combined with maintenance windows — scheduled periods where a box or specific device is exempt from job dispatch — teams can coordinate hardware swaps, firmware updates, and calibration without blocking the rest of the fleet.

Every state change is audited. Box registration, API-key rotation, lock acquisition, device disconnection, and manual overrides are all recorded with actor, timestamp, and correlation ID. For teams operating under SOC 2, ISO 27001, or internal compliance review, this turns "which engineer ran what on which piece of hardware last Tuesday" from an SSH-log archeology expedition into a filtered query.