The PiKVM feature table is where DIY ends and the sold hardware begins

The job is the machine whose operating system no longer answers

PiKVM is built for a specific failure: the target is on, but you cannot log in. The project states that its device manages servers or workstations remotely regardless of the health of the operating system or whether one is installed, and that you can fix a problem, enter the BIOS, or reinstall the OS through the emulated virtual CD/DVD or flash drive. That is the whole reason the storage emulation exists. Images can be kept on NFS rather than on the SD card of the Pi itself. The framing also sets the scope. One PiKVM unit addresses one machine, and multiport work is a separate product: the PiKVM Switch is a separate add-on described as transforming a PiKVM into a multiport device.

Two capture paths decide your build, and the OS image is read only

FullHD video arrives through one of two routes, an HDMI-to-CSI bridge or a USB dongle.. The Pi side is unusually open: a device can be based on Raspberry Pi 2, Pi 3, Pi 4, Pi 5 or Zero2W. The system itself is provided as a ready-made OS with a read-only filesystem, so the Pi is not treated as a general purpose machine you log into and modify, which suits an appliance in a rack or a closet. What you cannot do is treat the SD card as scratch space for your own tooling.

Audio, microphone and web camera stop at the DIY line

This is the sharpest cut in the platform table. HDMI audio capture, the microphone for two-way audio and the web camera for video calls are marked present on the V4 Plus, the V4 Mini and the V3, and marked absent on DIY V2 and DIY V1. Input is not affected, since USB keyboard and mouse emulation is marked on every platform including both DIY lines, and super fast H.264 and MJPEG video up to 1080p 60fps is marked on every platform too. So a DIY unit is not a reduced V4, it is a video and keyboard device. The table does not list those audio and webcam features for its DIY configurations; that table alone does not establish what every possible third-party capture device can support. Anyone planning a DIY build for a shared desk or a recording setup should read the video row before the input row.

Sixty hertz modes stop at the V4 line, and local passthrough stops at the Plus

Two display capabilities narrow the choice further. HDMI 1920x1200 at 60Hz, offered for big displays, and HDMI 1920x1080 at 60Hz, offered for BIOS and UEFI compatibility, are marked on the V4 Plus and V4 Mini and not on the V3 or on either DIY line. Video passthrough to a local display is narrower still, marked only on the V4 Plus, so a PiKVM with its own screen next to the machine is a single-model feature. The same table separately claims streaming at up to 1080p 60fps for every platform. These rows describe different aspects of input compatibility and encoded output, so check the actual capture hardware and supported input modes rather than treating either row as a universal guarantee. The BIOS line is the one to watch, because the stated reason for the 1080p60 mode is UEFI compatibility, and that is exactly the situation a KVM exists to handle. Buying the Mini gets the refresh modes; buying the Plus is what adds a physical console screen.

Host power arrives through ATX, and out of band control through IPMI or Redfish

PiKVM reaches the target in two distinct ways, and they solve different problems. Direct control of server power is done using ATX functions. Separately, the device can use IPMI BMC, IPMI SoL, Redfish and Wake-on-LAN to control the server. The project also lists control of GPIO ports and USB relays. What you cannot do is expect PiKVM to power-cycle a machine that exposes none of these interfaces.. The practical consequence is a wiring decision made before assembly: which of ATX, IPMI, a front panel button or a relay the target machine exposes decides whether your build can cold boot it, cycle it or only watch it.

Input emulation is broad, and delivery stops at the web UI or VNC

The emulation side covers more than a plain keyboard. USB keyboard and mouse emulation is listed with LEDs and the wheel, there is Bluetooth HID, a mouse jiggler, and full support of PS/2, so older machines and BIOSes that predate USB input are inside the stated scope rather than an afterthought. Delivery is narrower. Access is through the web UI or VNC, and video is offered as WebRTC, H.264-over-HTTP and MJPEG, so the transport is a choice between browser friendly paths and a classic remote framebuffer client rather than an open plugin protocol. Security is handled by extensible authorization and HTTPS out of the box, which for a device sitting on a management network is the part to verify before you point it at production. On latency the project claims a proven 35-50ms H.264 figure and links a latency page in its documentation. Treat that as a claim from the project, and read that page if the number has to hold a budget for your own use.

The repository is documentation and a product table, with no release stream

The repository root is not a source tree you can build. Its top level holds README.md, LICENSE, a docs directory, an img directory, mkdocs.yml, a .github directory and .gitignore, and the project publishes its documentation at docs.pikvm.org with mkdocs.yml as the site configuration. The software stack itself is common to every platform, which is stated as the reason V1 through V4 share one codebase, and the documentation is where assembly and configuration live. There are no GitHub releases on this repository, so there is no version to pin and no release notes to read before an update; the last push to master is dated 2026-10-27. What you cannot do is treat the repository as the place where firmware versions are announced. Two consequences follow for anyone planning a rollout, because a deployment has no rollback target in the shape of a tag, and because the assembled V4 and V3 are devices you buy while V2 and V1 are builds you assemble, which means the hardware variant and the software variant are chosen at different moments.

Editorial conclusion

PiKVM is the right tool when a server needs a console that survives a reinstall, and the DIY V2 on a Pi 5 or Pi 4 is the sensible starting point for a homelab. For HDMI 1080p60 input compatibility, the table lists the assembled V4 models; it also lists HDMI audio capture, microphone and webcam features for V3 and V4 but not the DIY variants. Verify the capture hardware and current documentation before buying. Before ordering anything, confirm the target exposes ATX, IPMI, Redfish or Wake-on-LAN, or plan on GPIO and USB relays, and read the platform table rather than the general feature list, since the two do not agree.

Frequently asked questions

Official sources

1. Issues
2. License: GPL-3.0
3. pikvm/pikvm on GitHub
4. Project website
5. README