Supported KVM devices
KVM Remote speaks each device’s own protocol rather than wrapping its web page. That is what makes hardware-decoded video and true keyboard passthrough possible, and it is also why support is listed per backend. Here is where each one stands.
Supported
GL.iNet Comet
Comet; Comet PoE and Comet Pro share its protocol
The primary backend. Multipart login with optional TOTP, WebRTC video, KVMD input and the full device settings surface.
- Video
- H.264 over WebRTC with live bitrate, frame rate, keyframe and encoder presets.
- Audio
- Separate audio connection from the Session menu; opt-in microphone, press-to-talk and camera sharing on supported firmware.
- Input
- Full keyboard passthrough, absolute and relative mouse, scroll, shortcut bar and macros.
- Power, media and admin
- ATX power, virtual media (ISO as CD-ROM or writable USB), EDID presets, snapshots, network, Wi-Fi, USB gadget, security, firmware, boot screen and Fingerbot administration.
The Supported label reflects sessions against a Comet. Comet PoE and Comet Pro use the same protocol but still need model-specific hardware checks. Physical-approval login is not supported. H.265 is implemented but this firmware never offers it.
Experimental
PiKVM
PiKVM hardware and DIY builds running KVMD
Cookie login, Janus uStreamer receive-only video and audio, KVMD input and automatic reconnect.
- Video
- H.264 over WebRTC through Janus. Requires Janus and uStreamer to be enabled on the device.
- Audio
- Received where the device advertises it, with volume and mute controls.
- Input
- Full keyboard passthrough, absolute and relative mouse, scroll, shortcut bar and macros.
- Power, media and admin
- ATX power and mass-storage actions where the device hardware has them enabled. Reports HDMI signal presence separately from stalled video.
Verified against the KVMD source and protocol fixtures rather than a physical session. GL-specific administration and encoder tuning are not shown.
Experimental
JetKVM
JetKVM
Local cookie login, device-offered WebRTC and the reliable HID and JSON RPC channels.
- Video
- H.264 over WebRTC on the local network or a routed VPN.
- Audio
- Not implemented.
- Input
- Full keyboard passthrough, absolute and relative mouse, scroll, shortcut bar and macros.
- Power, media and admin
- None yet. Cloud login and relay, extensions, virtual media and vendor administration stay in the JetKVM web interface.
LAN and VPN path only. Verified against the JetKVM source and wire fixtures rather than a physical session.
Experimental
NanoKVM
Original NanoKVM on current binary-HID firmware
Cookie or token login, device-offered H.264 and binary USB HID reports on current firmware.
- Video
- H.264 over WebRTC, applying the STUN and TURN servers the device advertises.
- Audio
- Not implemented.
- Input
- Full keyboard passthrough, absolute and relative mouse, scroll, shortcut bar and macros.
- Power, media and admin
- None yet. Power, media and administration stay in the NanoKVM web interface.
Targets the current binary-HID firmware protocol. Firmware with authentication disabled is handled. Verified against the NanoKVM source rather than a physical session.
Experimental
NanoKVM Pro
NanoKVM Pro
A separate backend for the Pro’s H.264 endpoint, binary HID and token-to-cookie login.
- Video
- H.264 over WebRTC.
- Audio
- Not implemented.
- Input
- Full keyboard passthrough, absolute and relative mouse, scroll, shortcut bar and macros.
- Power, media and admin
- None yet. H.265, audio and Pro administration are not implemented.
Verified against the NanoKVM Pro source rather than a physical session.
What every backend gets
Hardware-decoded video with Lanczos scaling and Pixel Perfect sizing, a shortcut bar for keys the host operating system intercepts, keyboard macros, View Only and Observe Only modes, per-device console preferences, multiple simultaneous sessions, a diagnostics log with redacted exports, and certificate pinning for the self-signed certificates these devices ship with.
What “experimental” means here
The PiKVM, JetKVM and NanoKVM adapters were written against each project’s published source and checked with deterministic protocol fixtures. That establishes wire compatibility with the reviewed revisions. It does not establish compatibility with every shipped firmware, and no physical session with those devices had been performed when this page was written. A backend moves to Supported only after login, first frame, keyboard modifiers, both mouse modes, scrolling, focus-loss cleanup and a clean reconnect have been recorded on real hardware.
Connecting over a VPN
KVM Remote talks to the device directly, never through a vendor cloud. Any route that reaches the device works: the same LAN, a site-to-site VPN, Tailscale or WireGuard. Connections to a VPN address or DNS hostname are treated exactly like a local address. Read the guide on what an IP KVM is and how it differs from remote desktop if you are choosing hardware.
Device and brand names belong to their respective owners. KVM Remote is an independent client and is not affiliated with GL.iNet, PiKVM, JetKVM or Sipeed.