What is an IP KVM, and how is it different from remote desktop?

An IP KVM is a small box that plugs into a computer’s HDMI output and a USB port, then puts both on the network. From anywhere that can reach it, you see exactly what a monitor would show and the computer believes a keyboard and mouse are attached. The initials stand for keyboard, video and mouse.

Why not just use remote desktop?

Screen Sharing, VNC and RDP are software running on the computer you want to control. They only work once the operating system has booted, the network is up and the service is logged in. That excludes most of the situations where you actually need to reach a machine: it is powered off, stuck in the BIOS, waiting on a full-disk encryption password, half way through an OS install, or the network driver just broke.

A hardware KVM has none of those dependencies. The target does not know it is being remoted. It sees a monitor and a USB keyboard, which is why you can enter a firmware setup screen, type a pre-boot password or install an operating system from an ISO the KVM presents as a virtual CD-ROM.

The trade-off is that the KVM only has the HDMI signal to work with. It cannot read the target’s clipboard, transfer files through an agent, or show a display the target has not rendered. Sending text works by typing it. Reading text works by recognising it on screen.

What the popular devices have in common

GL.iNet Comet, PiKVM, JetKVM and NanoKVM all follow the same pattern. A capture chip encodes HDMI to H.264, a small computer streams it over WebRTC or MJPEG, and a USB gadget controller emulates a keyboard, mouse and mass-storage device. Most add ATX power headers so you can press the power and reset buttons remotely, and all of them ship a web interface.

That web interface is where the differences between devices matter least and the limits of a browser matter most.

Where a browser tab falls short

A browser cannot receive Cmd-Q, Cmd-Tab, Ctrl-Alt-Delete or the Spaces gestures because the operating system takes them first. Video is decoded and scaled however the page’s canvas decides, which usually means blurred text at fractional zoom levels. Every device you own is a separate tab with its own login, and closing the laptop lid drops all of them.

A native client such as KVM Remote decodes the same H.264 stream in hardware, scales it to exact device pixels, captures the chords the host would otherwise intercept, and keeps a library of devices with per-device preferences. Read how to send Ctrl-Alt-Delete and other shortcuts through a KVM for the keyboard side, and how to get sharp text from a KVM video stream for the video side.

Choosing a device

Think about where you will be when you need it. If the answer is “on the same network or a VPN”, any of the devices above will do and you can avoid vendor cloud services entirely. If you need power control, check for an ATX adapter or a smart-plug integration. If you will install operating systems, virtual media over USB matters more than video quality. And if you will read a lot of text, look for a device that lets you control the encoder rather than one fixed quality setting.

KVM Remote lists what each backend supports on the compatibility page.