Skip to content

Other Devices

The KVM Fleet agent is device-agnostic. It works with any KVM-over-IP device that exposes a web UI on localhost — including TinyPilot, BliKVM, and custom builds.

Requirements

  • Linux-based OS (kernel 3.10+)
  • Architecture: x86_64, aarch64, or armv7l
  • KVM web interface accessible on localhost (any port)
  • Outbound HTTPS access to app.kvmfleet.io

Install

curl -sSL https://app.kvmfleet.io/install | sh -s -- --token <your-token>

If the install script doesn't detect your device type, it falls back to the generic Linux install:

  • Binary: /usr/local/bin/kvmfleet-agent
  • State: /var/lib/kvmfleet/state.json
  • Service: systemd unit

Custom web UI port

By default, the agent auto-detects the KVM web UI port. If your device uses a non-standard port, set it in the state file or via environment variable:

KVMFLEET_KVM_PORT=8080 kvmfleet-agent run

Or in the systemd unit:

[Service]
Environment=KVMFLEET_KVM_PORT=8080

TinyPilot

TinyPilot runs on Raspberry Pi with Debian. The agent installs via systemd like any generic Linux device. No special configuration needed.

BliKVM

BliKVM variants (v1–v4) use either a custom Linux or PiKVM OS. If running PiKVM OS, see the PiKVM guide. Otherwise, the generic install works.

Custom / DIY KVM

If you've built a custom KVM solution (e.g., Pi + USB gadget + uStreamer), the agent will work as long as your web UI is accessible on localhost. The agent doesn't interact with the KVM software directly — it tunnels HTTP traffic.