Other Devices
Verified: PiKVM. That's the KVM-over-IP path we test end-to-end (console, HID, serial, ATX power).
Experimental: BliKVM, TinyPilot,
NanoKVM, JetKVM. These have dedicated install paths
and show an Experimental badge in your fleet. BliKVM runs the same kvmd
as PiKVM (full console); the others are fronted by the agent's raw
reverse-proxy console mode, which wraps the device's own web UI behind the
platform's access governance and audit trail.
By design the agent is a generic reverse tunnel — it forwards HTTP/WebSocket
traffic from the platform to a web UI on the device's localhost. So in
principle it can front any Linux-hostable KVM that exposes a local web UI.
Running a device that isn't listed above? Open an
issue — a real device in a real
deployment is what we promote from Experimental to Verified.
Generic Linux install (advanced)
The agent itself runs on any Linux host (x86_64 / aarch64 / armv7l,
kernel 3.10+) with outbound HTTPS to the platform. If the installer doesn't
recognise your device it falls back to a generic install:
- Binary:
/usr/local/bin/kvmfleet-agent - State:
/var/lib/kvmfleet/state.json - Service: systemd unit
If your KVM web UI is on a non-standard port, point the agent at it:
Running this against an unverified device is unsupported and best-effort — the tunnel may carry the UI, but we make no promise the full console/HID/power path works until that device is on the verified list above.