Advanced Usage
Security
JetKVM runs locally with no internet required. Remote access is off by default, sessions are encrypted end to end, and the software is open source.
Report a vulnerabilityFound a security problem? Report it privately.Summary
| Area | Details |
|---|---|
| Internet | Not required. Works offline on a local network. |
| Remote access | Off by default. JetKVM Cloud, self-hosted, or Tailscale. |
| Session encryption | End-to-end WebRTC (DTLS and SRTP). |
| Updates | Over HTTPS. Stable releases signed with OpenPGP and verified on-device. |
| Security updates | At least until 31 December 2032. |
| Source code | Open source on GitHub (firmware, web UI, cloud). |
| Company | BuildJet, Inc. (United States). |
| Manufactured in | China. |
Local access
- Open the web UI at the device's local IP.
- Local password is optional (recommended), prompted on first setup.
- Passwords stay on the device, hashed with bcrypt (JetKVM) or PBKDF2-HMAC-SHA256, 200,000 iterations (Mini / Mini W).
- 5 failed logins lock that client out for 15 minutes, up to 1 hour.
- Sessions last 7 days, one browser at a time.
- JetKVM serves HTTP by default, with optional HTTPS (self-signed or custom cert). Mini / Mini W serve HTTP only.
Session encryption
- Browser and device connect directly over WebRTC (DTLS and SRTP) for all video, input, and data, even when the local UI is loaded over HTTP.
- If NAT or a firewall blocks direct traffic, Cloudflare TURN relays the encrypted packets without inspecting them.
JetKVM Cloud
- Off by default until you adopt the device with a Google account.
- The device verifies each session itself and only accepts the adopting account.
- All cloud traffic is encrypted: HTTPS for the web app, WSS for signaling, WebRTC (DTLS/SRTP) for sessions.
- The cloud only handles signaling. Video, keyboard, and mouse never pass through it.
- Open source and self-hostable, or skip it and use Tailscale.
Stored for adopted devices:
| Record | Data |
|---|---|
| Account | Google account ID, email, profile picture URL |
| Device | Device ID, name, last-seen time, access token |
| Relay usage | Bytes relayed via TURN, per account |
Network connections
On a local network, JetKVM requires no internet access. When internet is available, outbound connections are limited to firmware updates, NTP time sync, and JetKVM Cloud (if enabled).
The firmware includes no analytics and no crash reporting. Update checks send only the device ID and model. A cloud connection also sends the firmware version.
Network RequirementsUpdates
- Firmware updates are delivered over the air over HTTPS. Auto Update is on by default and can be turned off in Settings.
- Stable releases are signed with OpenPGP using a release key pinned in the firmware (
AF5A 36A9 93D8 28FE FE7C 18C2 D1B9 856C 26A7 9E95). The device verifies both the SHA-256 hash and the signature before installing. - Signatures are not verified when you manually install a specific version or opt in to pre-release builds.
- Security updates for JetKVM, JetKVM Mini, and JetKVM Mini W are provided until at least 31 December 2032.
The ATX and DC extensions do not update over the air. To install a fix, flash the new firmware from a computer over USB.
Shell access
- JetKVM: SSH is off by default. Enabling Developer Mode turns on key-based SSH only (no password logins).
- JetKVM Mini and Mini W: No SSH and no shell access. USB debugging is off by default.
Wireless setup
JetKVM Mini W receives wireless network credentials over Bluetooth LE during setup. The exchange is encrypted and requires a 6-digit code shown on the device's display. The code rotates after 3 wrong attempts, and setup mode times out after 10 minutes.
Physical access
Anyone with physical access to the device can flash custom firmware over USB. JetKVM Mini and Mini W do not use secure boot or flash encryption. Deploy them in physically controlled environments.
Erasing a device
A factory reset wipes all settings, passwords, TLS certificates, SSH keys, and cloud registration. On JetKVM Mini and Mini W, disk images stored on a removable TF card are kept.
Factory ResetHardware
| Model | Processor | Firmware / OS |
|---|---|---|
| JetKVM | Rockchip RV1106G3 | Linux |
| JetKVM Mini and Mini W | Espressif ESP32-P4 | ESP-IDF firmware (no Linux) |
JetKVM Mini W adds an Espressif ESP32-C5 for wireless connectivity.
Source code
The firmware, web interface, and cloud are open source. You can read, audit, and build them yourself.
| Product | Repository | License |
|---|---|---|
| JetKVM | jetkvm/kvm | GPL-2.0 |
| JetKVM Mini and Mini W | jetkvm/mini | MIT |
| JetKVM Cloud | jetkvm/cloud-api | GPL-2.0 |
Vulnerabilities
Report security issues privately on GitHub or by email. We publish advisories on GitHub.
Report a VulnerabilityDisclosure PolicyCompany and manufacturing
JetKVM is designed and operated by BuildJet, Inc. (United States). Hardware is manufactured in China.