NanoKVM Full: the tiny IP KVM that knows almost everything
Take control of a server before the system even boots, drive its power supply, and build an ISO image with a chassis just four centimetres across.
A server that no longer responds to SSH or remote desktop normally requires a physical visit, finding a screen, a keyboard, and sometimes a free socket in an unwelcoming cabinet. The situation is even more frustrating after a failed update, when the system no longer boots or a setting needs to be changed in the UEFI.
The NanoKVM Full replaces this physical intervention with a browser. It captures the machine's HDMI output, emulates a keyboard, a mouse, and a USB drive, then transmits everything over the network. A separate ATX board also allows pressing the power and reset buttons remotely. The principle is not new; what is surprising here is finding these features in a cube of about four centimetres.
What is the NanoKVM Full actually for?
The device becomes interesting as soon as a machine runs without a screen: hypervisor, assembled NAS, lab mini-PC, home automation server, workstation placed in a workshop, or computer installed in a hard-to-reach location. It notably allows:
- observing POST messages and entering the BIOS/UEFI;
- regaining control after a network error or a faulty update;
- starting, stopping, or resetting the machine with the ATX interface;
- mounting an ISO image as a virtual USB drive and reinstalling a system;
- sending keyboard and mouse input from a browser;
- using Wake-on-LAN, a Web terminal, or custom scripts.
The Full version is a ready-to-use package. The Lite version retains the RISC-V core and HDMI capture, but is more aimed at integration and tinkering: no complete case, no OLED screen, and no ATX board provided.
Current technical specifications
| Element | NanoKVM Cube Full | Practical consequence |
|---|---|---|
| Platform | SG2002 RISC-V, 1 GHz, 256 MB DDR3 | Sufficient for a remote console, not to replace a general-purpose computer |
| Video | HDMI up to 1080p at 60 fps | Comfortable reading of BIOS and desktop, without aiming for multimedia use |
| Encoding | MJPEG and H.264 | Choice between simplicity, image quality, and bandwidth |
| Advertised latency | About 100 to 150 ms depending on mode and network | Very correct for administration, insufficient for competitive gaming |
| Network | Ethernet 10/100 Mbit/s | No Gigabit, but the throughput is generally sufficient for the KVM stream |
| Storage | 32 GB microSD card included | The system and virtual images share the card |
| Virtual devices | Keyboard, mouse, and USB storage | System installation without a physical USB key |
| Control | ATX board, Wake-on-LAN, two UARTs | Power and serial troubleshooting depending on integration |
| Local display | 0.96″ monochrome OLED, 128 × 64 | IP address, HDMI/USB status, and stream settings visible without scanning |
| Power | USB-C, about 0.2 A at 5 V | Very low consumption, but an independent source is recommended |
| Dimensions | 40 × 36 × 36 mm | The case is tiny; the cables take up more space than it does |
The Cube model does not transmit audio and has no HDMI loop-out. The original local screen must therefore be unplugged or powered by a suitable splitter if the machine must remain usable on site. These two limits clearly distinguish this product from a high-end rack KVM.
Box contents and physical quality
The Full version normally includes the case with its prepared system board, the NanoKVM-B board intended for the motherboard's front panel, two USB-A to USB-C cables, and a Dupont harness. The whole set is light, but the shell properly protects the circuits and the cooling remains completely passive.
The connectors are distributed across several sides:
- HDMI IN receives the image from the target machine;
- HID connects the NanoKVM to a USB port on this machine and carries keyboard, mouse, and virtual storage;
- AUX provides independent power;
- KVM-B connects the ATX control board;
- RJ45 connects the device to the local network.
The real physical challenge is not the case, but the five cables that can surround it. In a small bay or behind a mini-PC, short and flexible cables, ties, and a 3D-printed bracket make the installation much cleaner. The low weight of the NanoKVM is not enough to prevent a rigid HDMI cable from moving it.
Wiring: three paths and one power supply
The HDMI is an incoming stream: it goes from the server's video output to the NanoKVM. The HID cable is bidirectional from a functional point of view: it optionally powers the case and presents the USB devices to the host. The ATX board connects in parallel with the case buttons on the Power Switch, Reset Switch, and Power LED pins of the motherboard.
First connection and immediate security
Once the Ethernet is connected, the OLED screen displays the address obtained via DHCP as well as the status of the HDMI and USB links. Simply open this address in a recent browser. Older devices may still present the initial credentials admin/admin for the interface and root/root for SSH.
Recent versions improve this point: since application 2.1.5, a device whose password has never been set asks to change it. Version 2.5.1, released in September 2026, adds admin and user accounts, distinct roles, HttpOnly session cookies, and session revocation upon password change.
Before any remote access:
- update the application from a local connection;
- choose a unique and long password;
- create a non-administrator user account when multiple people need to intervene;
- reserve the DHCP address and place the device in an administration VLAN;
- never directly publish the Web interface or SSH on the Internet.
SSH is disabled by default on modern images, which is preferable. Only enable it for a specific operation and restrict its access via firewall. The NanoKVM controls keyboard, screen, and power: it must be treated as a privileged administration interface, not just a simple USB accessory.
Web interface and video quality
The interface focuses on the video and a floating toolbar. It provides access to the virtual keyboard, mouse mode, image mounting, terminal, Wake-on-LAN, ATX commands, scripts, and stream settings. The whole thing remains surprisingly responsive given the 256 MB of memory.
Four transmission resolutions are offered: 1080p, 720p, 600p, and 480p. This setting modifies the stream sent to the browser, not the HDMI resolution produced by the server. The codec choice depends on the situation:
- MJPEG sends independent frames, offers predictable behaviour and good readability, but consumes more bandwidth;
- H.264 significantly reduces the bitrate and generally gives a smoother experience, at the cost of a slightly more complex decoding chain.
Difference detection stops sending frames when the screen remains still. It saves traffic, but adds about 0.2 seconds when animation resumes. For installing a system or reading a console, the default setting is relevant. To monitor an animation, temporarily disable it.
1080p at 60 fps is a maximum capability, not a permanent guarantee. The result depends on the browser, the scene, the codec, the chosen quality, and the network. For administration, the advertised latency of about 100 to 150 ms is comfortable. For graphic creation, audio, or gaming, this is not the right tool.
ISO images and remote reinstallation
The free storage on the microSD card can be presented to the host as a virtual drive. You can place several installation images there, select the one to be mounted, and then choose this device in the server's boot menu. This feature transforms the NanoKVM into a permanent rescue kit.
The actually available capacity is not exactly 32 GB: the system occupies part of the card and the space varies according to the installed image. The Cube's microSD reaches about 12 MB/s in the official comparison. Booting and installation are therefore slower than with a USB SSD, but the goal is mainly to avoid a physical trip.
Prepare the images before the incident and verify their checksum. A corrupted image discovered during a remote outage is of no use. Also test that the UEFI properly detects the virtual drive and memorise the boot menu key.
ATX control: the feature that makes the difference
The control panel replicates the actions of the physical button. A brief press requests a normal start or stop depending on the host's state; a long press forces a power cut; Reset triggers a hardware reset. The status of the front panel LED is reported to the interface.
This capability must be used with caution. A forced power cut can damage a file system, interrupt an update, or corrupt a database. Always start by observing the screen and attempting a clean shutdown. The virtual emergency button is not a substitute for high availability.
Access from the outside: VPN before port forwarding
Tailscale is integrated and allows reaching the NanoKVM behind a connection without a public address, without opening a port on the router. After pairing to the same private network, the interface becomes accessible via the device's Tailscale address. In a professional environment, apply ACLs or Grants so that only administration workstations and accounts can reach the KVM.
A self-hosted VPN is also suitable. The main thing is to avoid direct exposure. Enable multi-factor authentication for the VPN account, remove devices that are no longer used, and regularly update both the client and the NanoKVM application.
What is appealing
- The form factor: the case fits next to a mini-PC or in a small cabinet without taking up a slot.
- System independence: BIOS, boot console, and installation remain accessible.
- Virtual media: several rescue tools can remain on site.
- The provided ATX control: the Full version is genuinely usable without soldering.
- The OLED screen: the IP address and link status are visible immediately.
- Open and active software: the public repository still receives features, fixes, and security improvements.
- Silence: no fan or moving parts.
What must be accepted
- A forest of cables: HDMI, HID, AUX, network, and ATX far exceed the volume of the case.
- Ethernet limited to 100 Mbit/s: sufficient for the intended use, but modest in 2026.
- No audio or HDMI loop-out: the NanoKVM Cube remains administration-oriented.
- A single host: managing multiple servers requires multiple cases or a true matrix KVM.
- A microSD as system storage: keep a backup image and avoid sudden power cuts.
- Security to configure: password, segmentation, updates, and VPN are not optional.
Full, Lite, or a more powerful model?
The Cube Full is the logical choice for a ready-to-run individual installation: case, OLED, board, and ATX control are provided. The Lite is suitable for serial integration or a project where one accepts building the case, power supply, and ATX control.
A more powerful KVM model is justified if you require Gigabit, a 4K image, audio, HDMI loop-out, multiple server ports, or lower latency. These needs exceed the vocation of the NanoKVM Cube Full. Its strength is not replacing all professional consoles, but making out-of-band administration accessible for every small server.
Verdict
The NanoKVM Full is one of those devices whose usefulness seems abstract until the first server is locked up remotely. At that moment, seeing the boot screen, sending a keystroke in the UEFI, or mounting an ISO image avoids a trip and can amortise the case in a single intervention.
Its limits are consistent with its form factor: 100 Mbit/s Ethernet, microSD storage, lack of audio, and delicate cable management. In return, the combination of HDMI, HID, virtual media, OLED, and ATX control forms a true out-of-band console. Properly powered, isolated in an administration network, and accessible only via VPN, this tiny cube becomes an excellent companion for a home server, lab, or small infrastructure.
Technical references
Read next
About the author
Jeremy Kraft runs the infrastructure and the self-hosted services of the IBCSC. These guides describe configurations that were actually deployed and re-checked before publication.
Discussion
Comments
No comment yet. Feel free to open the discussion with a question or your own experience.