TinyPilot adds REST API license for bare-metal automation

TinyPilot launched an Automation License that unlocks REST API control for Voyager KVM over IP devices, giving teams a way to automate physical systems outside the operating system. The company says the tool is meant for BIOS work, recovery tasks, legacy hardware and AI-assisted infrastructure workflows.

Why it matters: - TinyPilot’s Automation License gives teams a standardized way to automate bare-metal systems that traditional software tools cannot reliably reach. - The REST API can support BIOS changes, OS installs, firmware updates, recovery workflows and troubleshooting on legacy or air-gapped machines. - The model avoids installing agents on the target machine, which can simplify automation in restricted or fragile environments.

What happened: - TinyPilot introduced the TinyPilot Automation License on June 16, 2026. - The entitlement unlocks the REST API for TinyPilot Voyager KVM over IP devices. - TinyPilot says the license turns its hardware into a programmable access layer for connected physical infrastructure. - The Automation License is available now. - Organizations can buy TinyPilot directly or through select reseller and procurement channels.

The details: - TinyPilot devices connect to target machines through HDMI and USB. - The devices provide browser-based keyboard, video and mouse control outside the operating system. - With the Automation License, teams can send keystrokes, move and click the mouse, enter text and capture screenshots for real-time feedback. - The API can also support dashboards, monitoring tools, recovery workflows and AI-assisted operations around TinyPilot-connected systems. - The approach works across hardware vendors, operating systems and device types because the connection uses standard HDMI and USB. - TinyPilot says teams can build one automation layer for servers, workstations, appliances, lab equipment, industrial systems and legacy machines. - The company has shown early examples of dashboard and monitoring workflows that inspect multiple connected systems from a central interface. - The same automation layer can be adapted for lab automation, remote recovery, fleet monitoring and infrastructure testing.

Between the lines: - The launch positions TinyPilot as infrastructure automation infrastructure, not just a remote access device. - AI agents could use the same screenshots and input actions a human operator would use, which could make physical-system automation more practical before an operating system loads. - The strongest use case appears to be environments where normal remote access fails or is unavailable, including boot failures and firmware utilities.

What's next: - TinyPilot is betting customers will build custom workflows on top of the API rather than use only prebuilt ones. - The company’s early dashboard examples suggest more packaged monitoring and control use cases could follow. - Broader adoption will likely depend on how well teams can map existing infrastructure tasks onto the new automation layer.