Skip to content

TinyPilot Setup

Experimental

TinyPilot support is Experimental. TinyPilot doesn't run kvmd, so the agent fronts its native web UI in raw reverse-proxy console mode.

How to connect a TinyPilot device to KVM Fleet.

Prerequisites

  • TinyPilot (Voyager or Community Edition) reachable on its local web UI
  • SSH access to the device
  • An enrollment token from the dashboard

Install the agent

The installer detects TinyPilot automatically (it looks for /opt/tinypilot). You can also force it with --device tinypilot:

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

If your TinyPilot web UI requires a login, pass those credentials so the agent can authenticate the proxied console:

... --kvmd-user <user> --kvmd-pass <password>

The agent installs to /usr/local/bin/kvmfleet-agent; state lives in /var/lib/kvmfleet/.

Console access

KVM Fleet wraps TinyPilot's own web console behind the platform's access governance and audit trail, then proxies it through the agent's outbound tunnel. You reach the TinyPilot interface in the browser — every session is gated by your JIT policy and recorded in the audit log.

Network considerations

The agent makes only outbound HTTPS connections to app.kvmfleet.io on port 443. No inbound ports need to be opened.

Troubleshooting

Symptom Fix
Agent won't start Check journalctl -u kvmfleet-agent -f
Device shows offline curl -I https://app.kvmfleet.io from the device
Console shows "device console unreachable" Confirm the TinyPilot web UI is up on http://localhost and re-run with the right --kvmd-user/--kvmd-pass if it needs auth