Most Pi homelab posts on this site are about running a service on a Pi. PiKVM flips that around: it turns a Raspberry Pi into the thing that manages every other machine, remotely, even when those machines are completely broken. It’s the one project here that’s genuinely “hardware hacking” rather than “another Docker container,” and it hasn’t had a write-up yet.
What PiKVM actually does
PiKVM is open-source hardware and software that turns a Raspberry Pi into a KVM-over-IP device – full remote keyboard, video and mouse control of another computer, delivered over the network. The critical difference from VNC, RDP, or any software remote-desktop tool is that PiKVM doesn’t depend on the target machine’s operating system being up at all. It works during POST, inside the BIOS/UEFI menu, during an OS installation, and during a failed boot – anywhere a physical monitor and keyboard would normally be needed.
The hardware, and the one exception worth knowing
The usual instinct on this blog is “use the newest Pi” – PiKVM is the exception. A Raspberry Pi 4 with 4GB of RAM is the recommended board, specifically because the Pi 5 lacks the GPU hardware video-encode path PiKVM’s video-capture pipeline relies on. Buying the newest board here would actually be the wrong call.
- Raspberry Pi 4 (4GB recommended) – the supported, tested target for the core PiKVM image
- A CSI-to-HDMI capture add-on board – this is what actually digitises the target machine’s video output
- An ATX/reset header cable – connects PiKVM to the target’s power and reset pins for remote power control
Setting it up
- Flash the official PiKVM image to a microSD card (or, better, an NVMe/SSD if the board supports it) using the standard PiKVM installer
- Connect the capture HAT between the Pi and the target machine’s video output
- Wire the ATX header cable to the target motherboard’s power/reset headers
- Boot the Pi, log into the PiKVM web interface over the local network, and confirm video and keyboard/mouse passthrough are both working before relying on it
Remote power control is the part that actually saves a trip
Beyond video and input, PiKVM’s ATX integration means power-cycling or hard-resetting the target machine remotely – not just soft-rebooting an OS that’s still responsive, but physically pressing the power button from anywhere. For a homelab server sitting in a cupboard, or a family member’s PC three hours away, that’s the difference between talking someone through a BIOS setting over the phone and just doing it yourself.
Scaling past one machine
The modular PiKVM Switch add-on lets a single PiKVM manage up to 20 hosts by switching which one it’s currently capturing, and a rack-mountable version supporting up to 64 hosts is in development, expected some time in late 2026 or 2027 – the same core idea, just built for a proper server rack rather than a homelab shelf.
Don’t expose it to the internet carelessly
A device with full physical-level control over another machine, including its BIOS, is an extremely high-value target if left open to the internet with weak credentials. The sane setup is PiKVM reachable only over a VPN (Tailscale or WireGuard, both already covered on this site) rather than a port-forwarded rule – the whole point of the tool is emergency access, and that should mean access for you, specifically, not anyone who finds the login page.
Leave a Reply
You must be logged in to post a comment.