See the screen, control the computer, install an OS, and manage power remotely—with no agent software on the target computer.
English · 简体中文
Online Demo · Downloads & Updates · Documentation · Hardware & Accessories · Report an Issue
BliKVM is a hardware and software KVM over IP solution. Connect it to a computer's HDMI and USB ports, add a network connection, and use your browser to see the actual display and operate its keyboard and mouse.
From BIOS/UEFI and boot menus to the operating system desktop, control does not depend on remote desktop software running on the target. When its OS will not boot, its network configuration fails, or it needs a fresh installation, an independently powered and connected BliKVM can still help you recover it.
Try it first: Open the online demo to explore the BliKVM interface.
This page describes the new BliKVM software. Available features, firmware availability, and upgrade compatibility vary by model. Refer to the relevant release notes.
| What you need | How BliKVM helps |
|---|---|
| Access when the OS cannot help | Reach the HDMI display and USB keyboard and mouse for BIOS setup, boot troubleshooting, and OS installation. |
| Hardware-encoded live video | Operate through H.264 and WebRTC, with image quality, bitrate, and frame rate settings. MJPEG is also available. |
| Rich OpenAPI support for AI and automation | Connect screen capture, keyboard and mouse input, power control, and other APIs to your own programs so AI agents and automation tools can operate physical computers. |
| USB workflows beyond keyboard and mouse | Configure virtual media, USB networking, and camera and microphone forwarding as needed. |
| Your choice of network access | Use BliKVM independently on your LAN, or configure WireGuard, Tailscale, or ZeroTier for your remote network. |
| Updates with a recovery path | The new system uses A/B updates with signature verification, boot health confirmation, and fallback. The App supports independent updates and rollback. |
| Multiple platforms, a familiar interface | CM4, Pi 4B, H616, and RV1126B share a consistent Web interface, with settings shown according to device capabilities. |
- View the target computer's HDMI output and use keyboard, mouse, and common shortcuts.
- Stream hardware-encoded H.264 video, with H.265 on supported models.
- Adjust video settings to suit image quality, bandwidth, and responsiveness.
- Listen to the target computer through supported audio capture paths.
- Use fullscreen, screenshots, browser recording, text input, and keyboard macros.
- Customize your workspace with languages, themes, and toolbar settings.
Choose USB functions for the task at hand:
| Function | What it enables |
|---|---|
| Keyboard and mouse | Absolute or relative mouse modes for different operating systems and workflows. |
| Virtual media | Present a virtual optical drive or storage device for OS installation, recovery, and maintenance. |
| USB virtual network | Provide compatible target systems with a USB network connection and optionally share the KVM's network. |
| Browser camera and microphone forwarding | Make your remote browser's camera or microphone available to the target computer. |
| External USB camera | Add a view of the site, instruments, or rack environment on supported devices. |
| Local USB keyboard and mouse forwarding | Forward physical input devices plugged into the KVM on supported hardware. |
Simultaneous combinations depend on USB controller resources and firmware support. The interface checks relevant capabilities and resource limits. See the documentation for your model.
- Power management: Use an ATX connection to control power and restart, or Wake-on-LAN to wake compatible systems.
- Terminal and serial console: Manage the KVM itself in your browser, or troubleshoot equipment through a configured serial connection.
- Automation: Combine keyboard macros, custom scripts, and APIs to integrate repetitive tasks into your workflow.
- Monitoring and diagnostics: Inspect status, network addresses, logs, and diagnostics, with Prometheus integration for monitoring.
- Network management: Configure Ethernet, supported Wi-Fi, VPNs, and DDNS for your deployment.
BliKVM provides both a browser interface and a broad set of APIs described with OpenAPI 3. They cover screenshots, keyboard and mouse input, text and shortcuts, power control, virtual media, and device management. Use your preferred language and tools to connect these capabilities to an operations platform, automation script, or AI agent.
Combined with an AI model that can interpret images, the APIs enable a feedback loop:
- Observe: Capture the computer's current screen.
- Understand and plan: Let your AI analyze the interface and choose the next action.
- Act: Send keystrokes, pointer movement, clicks, or text through the APIs.
- Verify: Capture the screen again to check the result and decide what to do next.
Automation can extend beyond the target computer's existing remote desktop services or software APIs. Build workflows for graphical interfaces, installation checks, repetitive maintenance, or assisted BIOS/UEFI operation. BliKVM provides hardware access and control; you choose and integrate the AI model and task orchestration.
Start with your device's API documentation: Visit https://<device-address>/docs for interactive documentation, or retrieve https://<device-address>/openapi.yaml to generate clients and explore request parameters. API calls use an authorized device API token and are subject to account permissions and hardware capabilities.
BliKVM supports HTTPS, account permissions, two-factor authentication, and revocable API tokens. Assign administrator, operator, or viewer access and enable the remote access methods you need.
LAN use does not require a BliKVM cloud account. VPNs, online services, and optional cloud features depend on the model and firmware and may require network configuration or service accounts.
The new BliKVM software maintains the system and App separately, so routine application updates do not require reflashing the storage device.
- A/B system updates: Write the new system to the inactive slot and confirm its health after reboot. Failed trial boots can fall back to the previous slot through the update mechanism.
- System and bundled App switching: System updates also handle the included App, helping prevent a new system from continuing to run an incompatible old application.
- Independent App updates and rollback: Install an App update package when only the interface or application needs updating.
- Pre-update checks: Verify package signatures, hardware compatibility, versions, and compatibility requirements. Use release checksums to verify downloads.
- Persistent configuration: User configuration and working data reside on persistent storage during routine updates. Back them up separately before factory resets or reflashing.
System and App version numbers may differ. Check the versions on your About page and the release compatibility notes before choosing an update package.
Python screenshot and keyboard/mouse demo: call the OpenAPI endpoints from your computer using Python 3.10+, with no third-party dependencies. Includes screenshots, coordinate clicks, relative movement, keys, and key combinations. See the example README for authentication, certificate settings, and commands.
BliKVM offers hardware based on Raspberry Pi CM4, Pi 4B, Allwinner H616, and Rockchip RV1126B, plus switches, ATX accessories, and capture boards.
 BliKVM v1 CM4 |
 BliKVM v2 PCIe |
 BliKVM v3 HAT |
 BliKVM v4 Allwinner |
Visit the official store for all products and accessories
See the official website for model details and specifications. Video, USB resources, and expansion capabilities vary. Match the image to your hardware model and capture chip.
Identify your hardware first, then choose a file for your task. Available files depend on the selected release:
| Your task | File type | How to use it |
|---|---|---|
| First installation, reinstallation, or migration from an older system | Full image, such as .img.xz / .img.gz |
Decompress and flash to the appropriate storage medium as instructed. The image includes the App. |
| Update a compatible A/B system | System update package, .raucb |
Upload it in the system update interface and follow the instructions. |
| Update only the App | App update package, .tar.gz |
Install it in the application update interface after checking minimum system requirements. |
Older releases may use different partition layouts, package formats, and update methods. Follow the target release's migration instructions rather than inferring compatibility from filenames or version numbers.
- Connect: Connect the target computer's HDMI output and USB port to BliKVM. Add ATX wiring if you need power control.
- Add network and power: Connect the KVM to your network and power it according to its model's instructions.
- Open your browser: Find its address on the device display or your router's DHCP list. Open the HTTPS interface and complete first-time login and password setup.
- Take control: Open the video stream and test keyboard and mouse input. Enable audio, virtual media, or other USB functions as needed.
See the documentation for wiring, flashing, and model differences. Where new firmware differs from older documentation, follow the relevant release notes.
blikvm/blikvm is BliKVM's public product and release hub. This branch contains the English and Chinese READMEs, supporting images, and API examples, with links to downloads, release notes, documentation, hardware, and community support.
Historical source code, build scripts, images, and development notes remain available in Git history. They are not the build entry point for current firmware. Removing them from the current tree does not change their existing licenses.
- Online experience: BliKVM demo
- OpenAPI documentation:
/docson your device; interface definition at/openapi.yaml. - Official website: blikvm.com
- User documentation: BliKVM docs
- Downloads and release notes: GitHub Releases
- Issues and feature requests: GitHub Issues
- Community:
- Product inquiries and customization: info@blicube.com
When reporting a problem, include your hardware model, system version, App version, reproduction steps, and relevant logs.
Thank you to PiKVM, TinyPilot, and the open-source projects supporting the KVM ecosystem.
The license for historical code is preserved in the historical LICENSE file. Components and third-party dependencies in release packages retain their respective licenses and terms.
The website and bilingual manuals are maintained in this repository. See website maintenance for local development, deployment and demo synchronization.