# ESP-KVM > An open-source IP-KVM: firmware that turns a ~$40 ESP32-P4 board and a TC358743 > HDMI bridge into a KVM-over-IP. It captures a target machine's HDMI, presents > itself to that machine as a USB keyboard and mouse, and serves both to a browser > over HTTPS - enough to reach a machine with no working OS (a BIOS screen, a boot > menu, a kernel that will not come up). Free and open source, Apache-2.0. Key facts: - Hardware: an ESP32-P4 plus a TC358743 HDMI-to-MIPI-CSI-2 bridge. Reference build is a Waveshare ESP32-P4-ETH with a Geekworm C790; fourteen other P4 boards have their own images, among them the Espressif ESP32-P4 Function EV Board. The one exception to the bridge is the M5Stack Unit PoE-P4, whose Add-on Display In carries a Lontium LT6911D instead - that add-on fits M5Stack's own units and nothing else. - Video: follows the target's resolution automatically (a 640x480 BIOS through a 1080p desktop); MJPEG or hardware H.264. - Input: a composite USB HID device - keyboard, absolute and relative pointer, media keys. - Text screens can be read back as characters: a BIOS, a boot loader or a console can be selected with the mouse and copied, or copied whole. Not OCR - the characters are read from the character grid the firmware draws them on, so a reading is either exact or refused. Graphical UEFI setups have no grid and are not read. - The device can watch a text screen while nobody is connected: give it phrases (`no boot device`, `kernel panic`) and it raises an alert, in its log and in Home Assistant, when one appears. Off by default. - Runbooks: a script of keys to send and phrases to wait for (`wait Press F2`, `key f2`), run on the device itself so it carries on with the browser closed; each one is a button in Home Assistant. Macros are the same language without the waits, played by the console. The language: https://espkvm.io/scripts/ - ESP-KVM Tools (espkvm-tools), an optional program for the target (Linux, Windows, macOS), talks to the device over the USB cable: the machine's name and addresses, the clipboard both ways, a clean shutdown. Reading the clipboard and power are allowed only by flags on the target. https://espkvm.io/espkvm-tools/ - A scheduler: five-field cron lines that fire an action on the device on a timetable - Wake-on-LAN, an ATX button, a runbook, or a restart, and recording or a timelapse. The device sets its clock over SNTP (a LAN time server works with no internet) or takes the browser's time when you sign in; the time zone is picked from a list of cities in Settings. - A KVM switch in front of several machines: one GPIO to the switch's select button (the device counts the presses), or a TESmart switch over the network (the same TCP commands as PiKVM). Picked from the console's Power menu, a schedule, a button, the screen menu, MQTT or POST /api/v1/power/switch. - HDMI-CEC, on boards with a TC358743 capture chip: the device sits on the HDMI cable as a TV would, shows what the source says it is (name, CEC version, on or in standby) and gives a remote for it - arrows, OK, Back, volume, playback keys, standby and wake. Also in the API, in runbooks (`hdmi standby`, `hdmi key up`) and in Home Assistant. TV boxes, consoles and a Raspberry Pi speak CEC; ordinary PCs do not. - Notifications: when a watched phrase appears, the screen goes blank, a dashcam clip is saved or the Tailscale key is about to run out, the device sends a message to Telegram (with a screenshot), to a webhook as JSON, to browsers as Web Push and to an ntfy topic, with a table of which event goes to which channel. Off by default. - Upload: recordings, dashcam clips and screenshots go from the card to a WebDAV folder (Nextcloud, ownCloud, a Synology or QNAP share), by hand or as soon as they are saved. Files wait on the card while the server is down. - Pasting text types it out as keystrokes, so it follows the target's keyboard layout: US English, Russian, Czech, Ukrainian and Lithuanian. A character the layout cannot type is reported rather than guessed at. - Recording: a button writes the screen to the device's own microSD card as H.264 in .ts files - the same stream the viewers get, so nothing is encoded twice - and another saves a JPEG. A dashcam keeps the last minutes of the screen (in PSRAM, or on the card on boards short of it) and saves them as an MP4 with a chapter per event when the screen stays one flat colour, a watched phrase appears, the target's power LED goes off, or the operator asks; with notifications on the clip goes to Telegram as a video. Keystrokes can be written into a .srt beside the video, masked as dots by default. A timelapse keeps one frame every few seconds and plays back at 25 fps. Recordings play in the console, streamed from the card, and what the screen said during a recording is searchable (character screens only). Recording needs H.264 and a writable card. - Virtual media: boot the target from a disk image on a microSD card, a small image in the device's own flash, an image on a web server (HTTP Range requests, nothing copied to the card) or a file on the computer the console is open on. - Networking: Ethernet, or WiFi on boards with an ESP32-C6 (the Function EV Board) - station or the device's own access point. On boards with both, "Auto" keeps WiFi as the backup for the cable and switches both ways on its own. A rescue hotspot and a captive portal keep a device reachable, and set up from a phone, when its network is out of range. mDNS (espkvm.local), DHCP or static addressing, and IPv6 alongside IPv4 (autoconfigured from the router, nothing to fill in). - An optional status screen on the device (I2C OLED, or a round SPI LCD) shows the link, address, capture state and health with no browser. The round one also shows a code a phone scans to join the rescue hotspot, and fills a ring while the recovery button is held. Either can be mounted upside down and turned over in the settings. - An optional battery-backed clock: a DS3231 module on the capture chip's I2C bus (a "DS3231 for Pi" module plugs onto pins 1-9 of a Raspberry Pi header) keeps the time across a restart with no network. Without one the device learns the time from NTP or from a browser signing in. - Security: HTTPS with a certificate the device issues itself, plus a login with optional two-factor sign-in (a TOTP app, with recovery codes). It is not meant for the public internet - keep it on a trusted network, or reach it over the built-in WireGuard client (split-tunnel, generates its own key). - Updates install over the network into a spare slot, with rollback. The console shows the version and state of both slots and can boot the other one on demand. The device never reaches the internet on its own. - Experimental: ESP-KVM terminal, separate firmware for the M5Stack Tab5 that shows an ESP-KVM device's screen on the Tab5 and controls the target by touch and keyboard, with no browser. MJPEG only (the Tab5 chip has no H.264 decoder). - It builds on jrowny/p4kvm, which brought up the TC358743 on the ESP32-P4 first. ## Links - [Website](https://espkvm.io/) - [Flash from the browser](https://espkvm.io/flash/) - [Supported boards, rated for an IP-KVM out of five, with capture boards and cases](https://espkvm.io/boards/) - [Every ESP32-P4 board, supported or not, and why some cannot work](https://espkvm.io/boards/all/) - [JetKVM Mini and Mini W: custom firmware, tested on a real Mini](https://espkvm.io/boards/jetkvm-mini/) - [Integrations: Home Assistant, MQTT, Tailscale, WireGuard, Telegram, Web Push, ntfy, webhook, WebDAV](https://espkvm.io/integrations/) - [Serial monitor in the browser](https://espkvm.io/serial/) - [Tools: read a firmware image, decode a panic, inspect an EDID](https://espkvm.io/tools/) - [ESP-KVM terminal on an M5Stack Tab5 (experimental)](https://espkvm.io/terminal/) - [Comparison with PiKVM, JetKVM, JetKVM Mini, NanoKVM, PicoKVM and GL.iNet Comet](https://espkvm.io/compare/) - [For writers: descriptions, facts, logo files, pictures](https://espkvm.io/press/) - [Interactive demo, no hardware needed](https://demo.espkvm.io/) - [Blog: what each release changed, and how](https://espkvm.io/blog/) - [Source code on GitHub](https://github.com/espkvm/espkvm) - [README](https://github.com/espkvm/espkvm/blob/main/README.md) - [Releases](https://github.com/espkvm/espkvm/releases) - [Discussions](https://github.com/espkvm/espkvm/discussions) - [Telegram group, to reach me](https://t.me/espkvm) - [X / Twitter](https://x.com/espkvm) - [YouTube channel](https://youtube.com/@espkvm)