Test BIOS and firmware changes
Observe the boot sequence after a firmware update, adjust BIOS or UEFI settings, and record errors.
Identify startup failures without staff at the bench
For R&D, life sciences, and aerospace & defense labs
Access BIOS, boot menus, OS installers, and serial consoles from a web browser.
TinyPilot Voyager 3 provides KVM over IP and serial console access. There is no agent to add to your test image or reinstall after reimaging.
Remote desktop tools require software running on the target system, which many test systems cannot have: a controlled software image, an embedded board, or a system halted at a boot error. TinyPilot connects through the system's video output and USB port, so the test system needs no network connection of its own for KVM access.
Observe the boot sequence after a firmware update, adjust BIOS or UEFI settings, and record errors.
Identify startup failures without staff at the bench
Mount an installation or recovery image as virtual media and complete OS setup from a browser.
Prepare the bench for the next run without a lab visit
Read boot output and run commands on embedded boards through a supported USB-to-serial adapter.
Debug embedded systems without a technician at the bench
Start with the benches that are reimaged most often or need frequent BIOS or serial access. TinyPilot stays connected beside the test system and requires no software on it.
Install one TinyPilot per test system and leave it connected, with serial to a dev board or network device.
Use HDMI and USB for a computer’s screen and keyboard. Add USB-to-serial adapters for boards and devices with serial consoles.
Use your VPN or an overlay such as Tailscale, with no open inbound ports. Keep TinyPilot private and turn on role-based access with 2FA.
Confirm you can reach BIOS, virtual media, and serial consoles before you leave the bench unattended.
Also Included: LAN Monitor
Discover devices on TinyPilot's connected local networks and track reachability for up to 25 selected devices.
Read the LAN Monitor guide
The Business Impact
When a system stops at a boot error or needs a reinstall, the next test waits for someone at the bench. With TinyPilot, the engineer responsible for the test can resolve it from their own workstation.
Because no software is installed on the test system, there is nothing to approve, document, or remove before a run.
Questions about your equipment?
Let's discuss your lab setupNo. TinyPilot captures the test system's video output and provides keyboard and mouse input over USB, so no software is installed on the test system. The system recognizes TinyPilot as a standard USB keyboard and mouse. You can work in BIOS or UEFI screens, boot menus, and OS installers. TinyPilot itself needs power and a network connection.
TinyPilot connects to a system’s HDMI video output and a USB port for keyboard and mouse control. Other video outputs may require an adapter. Serial access requires a supported USB-to-serial adapter and a compatible console interface.
Each TinyPilot directly connects to one computer for KVM access. For several systems, use additional TinyPilot devices for independent remote access. Supported serial connections can be used alongside KVM access.
No cloud account is needed. TinyPilot runs on your local network, and engineers reach it in a browser on that network or through your VPN or an overlay such as Tailscale.
Getting started
Bring an example test setup. We will discuss video and USB compatibility, serial connections, and how your engineers will reach the bench.