NanoKVM

🌟 What is NanoKVM?

NanoKVM is a series of compact, open-source IP-KVM devices based on the LicheeRV Nano (RISC-V). It lets you remotely access and control computers as if you were sitting in front of them, making it useful for servers, embedded systems, and other headless machines.

📦 Product Family

Choose the NanoKVM model that best fits your deployment:

• NanoKVM-Cube Lite: A barebones kit for DIY users and bulk deployments.
• NanoKVM-Cube Full: A ready-to-use kit with a case, accessories, and a pre-flashed system SD card.
• NanoKVM-PCIe: A PCIe-bracket form factor for internal chassis mounting. It draws power from the PCIe slot and supports optional Wi-Fi and PoE.
• NanoKVM-Pro: A higher-performance version with major upgrades:
  • Resolution: Up to 4K@30fps / 2K@60fps.
  • Network: 1Gbps Ethernet + PoE + Wi-Fi 6, upgraded from 100Mbps Ethernet.
  • Latency: Hardware-accelerated encoding reduces latency from 100-150ms to 50-100ms.

If you are looking for a USB-based KVM solution, check out NanoKVM-USB.

🛠️ Technical Specifications

📂 Project Structure

├── kvmapp          # APP update package
│   ├── jpg_stream  # Legacy support for direct updates from older versions
│   ├── kvm_new_app # Triggers components for kvm_system updates
│   ├── kvm_system  # Core KVM application
│   ├── server      # Front-end and back-end integration
│   └── system      # Essential system components
├── web             # NanoKVM Front-end (UI)
├── server          # NanoKVM Back-end (Service)
├── support         # Auxiliary modules (Image subsystem, status, updates, OLED, HID, etc.)
├── ...

💻 Development

Start with the guide that matches the part of NanoKVM you want to work on:

• System support modules: Build and update the low-level hardware support components in support/sg2002/README.md.
• Backend service: Set up, build, and understand the Go service in server/README.md.
• Frontend UI: Develop, lint, and build the React interface in web/README.md.
• Release packaging: Assemble the nanokvm_<version>.tar.gz update package in scripts/README.md.

Backend compilation and runtime validation require the target toolchain or a NanoKVM device. See the module-specific guides above for the latest development workflow.

Dev container (optional)

The repository ships a Dev Container setup (.devcontainer/) that layers the frontend toolchain (Node 22, pnpm 11) on top of the release builder image (RISC-V cross toolchain, Go, MaixCDK), so one container covers Go, C support-layer and web development. It is a convenience for IDE users; the make targets in the repository root remain the canonical CLI workflow.

• Requirements: Docker plus an editor or CLI with dev container support (e.g. the VS Code "Dev Containers" extension, or devcontainer up).
• On creation the container prepares itself automatically: support/sg2002/build update_lib (resyncs MaixCDK components with the checkout) and pnpm install for the frontend.
• Backend: run server/build.sh for a release-equivalent binary (BoringCrypto + dl_lib RPATH). make app builds a plain development binary without those, so prefer server/build.sh whenever the result should match a release.
• Support layer: cd support/sg2002 && ./build kvm_system (the MaixCDK virtualenv is part of the container environment).
• Frontend: cd web && pnpm dev (VS Code forwards port 3001 automatically; other clients may need to map it themselves); see web/README.md for pointing it at a device.
• The base image ghcr.io/sipeed/nanokvm-builder:latest is x86-64 only; on Apple Silicon it runs under emulation (works, but C builds are slow). You can also build the image locally first (make builder-image) and point the BASE_IMAGE build arg at it (e.g. via build.args in devcontainer.json). On Linux hosts the first container creation also takes a while: the container user is remapped to your uid, which re-chowns its home directory once.
• Hardware-dependent verification still requires a real NanoKVM device; the container covers compiling, linting and mock-mode web development only.

🔩 Hardware Platform (NanoKVM Cube/PCIe)

NanoKVM is based on Sipeed LicheeRV Nano. You can find specifications, schematics, and dimensional drawings in the download station.

The NanoKVM Cube/PCIe hardware is built from these components:

• NanoKVM Lite: LicheeRV Nano plus the HDMI-to-CSI board.
• NanoKVM Full: NanoKVM Lite plus the NanoKVM-A/B boards and enclosure.
• HDMI-to-CSI board: Converts the HDMI input signal.
• NanoKVM-A board: Provides OLED, ATX control output through USB-C, auxiliary power, and physical ATX power/reset buttons.
• NanoKVM-B board: Connects NanoKVM-A to the host computer's ATX pins for remote power control.

The NanoKVM image is built with the LicheeRV Nano SDK and MaixCDK. It is intended for NanoKVM hardware and is not a general-purpose KVM software package for other LicheeRV Nano or SG2002 products. If you want to build an HDMI input application on LicheeRV Nano or MaixCam, please contact us for technical support.

Note: Of the 256MB memory on SG2002, 158MB is currently allocated to the multimedia subsystem for video capture and processing.

• NanoKVM-A Schematic
• NanoKVM-B Schematic
• NanoKVM-PCIe Schematic
• NanoKVM image

🤝 Contributing

We welcome contributions. To get started:

1. Fork the repository.
2. Create a feature branch.
3. Commit your changes.
4. Push to the branch.
5. Open a Pull Request.

Please keep your pull requests small and focused to facilitate easier review and merging.

🎁 Contributors who submit high-quality Pull Requests may receive a NanoKVM Cube, PCIe, or Pro as a token of our appreciation!

🛒 Where to Buy

• AliExpress (global, except USA and Russia)
• Taobao
• Preorder for other regions

💬 Community & Support

• Discord
• QQ group: 703230713
• Email: support@sipeed.com
• FAQ

📜 License

This project is licensed under the GPL-3.0 License. See LICENSE for details.