PICOTTY Turns Pi Picos Into a Networked Serial Console

The Homelab Problem Nobody Budgets For

Every homelab eventually hits the same wall: a machine stops responding to the network, and the only way to see what happened is to physically attach a keyboard and monitor. Commercial IP KVMs solve this properly but cost real money per port. PICOTTY, an open-source project detailed on August 6, 2026, takes a narrower and much cheaper approach — it gives you the serial console and keystroke injection, and skips the video.

• A Raspberry Pi Zero 2 W acts as the hub, running a web dashboard on port 8080 and a TCP server on port 9000
• Each managed target gets a node: either a Pi Pico or Pico 2 with a WIZnet W5100S Ethernet HAT, or an integrated W5100S-EVB-Pico board
• All nodes run CircuitPython firmware and connect back to the hub over a managed Ethernet switch
• The project ships STL files for a 3D-printed enclosure holding up to four nodes, and the source is on GitHub

What It Actually Gives You

The developer describes PICOTTY as an IP keyboard rather than an IP KVM, and that framing is precise. From a browser you can watch the serial console output of a connected machine and send it either HID keystrokes or raw serial commands. What you do not get is a video feed, so anything that only exists in a graphical BIOS or a GUI installer stays out of reach.

For a homelab running headless servers, that limitation matters far less than it sounds. Serial console plus keystroke injection covers the overwhelming majority of recovery scenarios: watching a boot sequence stall, catching a kernel panic, interrupting a bootloader, or logging in to a box whose network stack has fallen over. The developer's own use case is managing Proxmox VE hosts, which is exactly the profile this suits.

Why Split It Into a Hub and Nodes?

The architecture is the clever part. Rather than running a cable from every target back to one controller, each target gets its own inexpensive Pico node that speaks to the hub over Ethernet. That means adding a fifth machine is a matter of adding a fifth node and a patch cable, not rewiring the whole setup, and it means the nodes can be physically distributed across a rack or even across rooms.

Using WIZnet W5100S hardware Ethernet rather than Wi-Fi is also a deliberate choice. A remote management tool that depends on the same wireless network as the machines it manages has an obvious failure mode; wired Ethernet on a separate managed switch keeps the out-of-band path genuinely out of band.

The Dashboard Feature Set

The web interface covers more ground than a bare terminal. It offers macro editing, so a recovery sequence you run often becomes one click; event history, so you can review what a machine printed before it went quiet; a settings panel; over-the-air firmware updates for the nodes; and a node visualisation showing what is connected. OTA updates in particular are the difference between a fun project and something you will still be running in a year.

How It Compares to the ESP32 Alternatives

PICOTTY joins a small but growing family of open remote-management builds. We recently covered ESP-KVM, which turns an ESP32-P4 board into a $45 IP KVM — that project does capture video, so if graphical BIOS access is a hard requirement it is the better fit. PICOTTY trades video away for a cleaner multi-target story and CircuitPython firmware that is genuinely approachable to modify.

The Proxmox connection is worth flagging too, given that Proxmox VE just added official Arm64 support, which we wrote about in our Proxmox VE 9.2 coverage. An Arm-based homelab with cheap out-of-band serial access on every node is a genuinely attainable setup now.

Everything is on GitHub — CircuitPython firmware for the nodes and a Python application for the hub — so the total cost is a Pi Zero 2 W, some Picos, Ethernet hats, and filament.

More maker hardware in our mini computers section.

Sources: CNX Software — August 6, 2026; PICOTTY on GitHub — August 2026.