Reserve the 01

Waitlist

Stay in the loop.

Launch news and new dispatches. Unsubscribe any time.

WarpKVM 01 · ships Q2 2027
← Transmission log

October 21, 2026Review

TinyPilot Voyager 3 Review: Premium Polish, Premium Price

The best-built, best-packaged IP KVM we own. Also the most power-hungry and most expensive, and slower than a PiKVM on the same Raspberry Pi.

By Andrew Douglass · Founder

TinyPilot Voyager 3 unit

Disclosure: Our articles contain affiliate links, including Amazon. If you buy through one, we may earn a commission at no extra cost to you, and as an Amazon Associate we earn from qualifying purchases. It never affects our testing, measurements, or verdicts. Full disclosure.

TinyPilot makes the most polished IP KVM we own, and this is the hardest review to write, because the numbers are unkind to it. We bought a Voyager 3, ran it, measured it, and opened it up. It has the best build quality and the nicest packaging of any device on our bench. It also posted the highest power draw of any mainstream KVM we tested and was slower than the PiKVM (61.3 ms against 57.3 ms glass-to-glass), on the same Raspberry Pi and the same open-source software that powers a cheaper rival. What you are really paying for here is polish, support, and a turnkey experience, not performance.

A KVM over IP gives you keyboard, video, and mouse control of a machine at the hardware level, so you can reach a server in BIOS or mid-reinstall. TinyPilot has been doing this longer than most, and it shows in the finish. Whether that is worth the price is the whole question.

The verdict up front

What it is, and the lineup

TinyPilot sells the Voyager 3, a PoE-equipped Voyager 3 Plus, and a Pro software tier, following earlier models like the Voyager 2a. The software is open source on GitHub, and you can build your own on a Raspberry Pi if you want. The company's whole pitch is that you should not have to: buy the finished unit, plug it in, and it works, with a warranty and ongoing updates behind it.

Founded by Michael Lynch, who documented the entire business publicly, TinyPilot built a reputation as the friendly, well-supported option. One thing worth knowing: Lynch sold the company in April 2024 to a private owner, and assembly had already moved to a contract manufacturer in Vietnam. So it remains a US-registered company (TINYPILOT LLC, Massachusetts), but it is Vietnam-made and no longer founder-run. We cover the ownership map across the market in who makes each IP KVM.

Build quality and what is inside

This is where TinyPilot wins outright. Unboxing the Voyager 3 gives you the nicest presentation of anything we tested: the unit, a set of branded HDMI and USB cables, and a branded power adapter, all in retail-grade packaging. The technical requirements on the target are minimal and standard, an HDMI output and a USB port plus Ethernet to your network, with no software to install on the host. The chassis is solid metal with a front status display. In design and hardware improvements over the older Voyager 2a, the 3 moved from a MacroSilicon MS2109 USB capture to the Toshiba TC358743 CSI bridge, and TinyPilot's changelog highlights reduced disk writes and a faster update process. It feels like a finished product from a real company, because it is.

Flat-lay of the Voyager 3 packaging and branded accessories, the best-presented unboxing on our bench.

We opened it. Inside is a Raspberry Pi CM4 (Broadcom BCM2711, quad Cortex-A72, 2 GB) with a soldered Samsung 32 GB eMMC, capturing HDMI through a Toshiba TC358743 bridge. That capture chip is an upgrade over the MacroSilicon MS2109 USB capture the older Voyager 2a used; the CSI path is the right choice. It runs uStreamer (the streaming engine from the PiKVM project) plus Janus on Raspbian. In other words, the Voyager 3's core hardware and its video engine are the same ones the PiKVM ecosystem uses. That is not a criticism of the engineering; it is legitimate reuse of good open-source work. It just matters a lot for the price. Full internals are in our teardown and capture-chip database.

Macro of the Voyager 3 internals with the CM4 module and Toshiba TC358743 capture bridge, the same core as the PiKVM.

The uncomfortable part: performance

Updated October 2026: we re-measured every KVM with a new two-monitor glass-to-glass rig at each device's best settings on current firmware. The figures below replace our July click-to-photon numbers; why they changed. To feel these delays rather than read them, try our latency page.

Here is the problem. We time glass-to-glass latency: an HDMI splitter feeds one source to a reference monitor on a straight cable and to the KVM, whose stream we show full screen on an identical viewer monitor, and two light sensors time the same on-screen change on both. The figure is the viewer's time minus the reference's, so it is the video delay the KVM path adds over a direct cable: capture, encode, network, decode and the viewer's display. Each figure is the median of 300 timed changes per side at 1080p60 in Chrome over wired gigabit LAN, and we quote the higher of a scrolling-text and a still screen. It is a video-path number only: it does not include the input path. At its best setting (H.264 over WebRTC at 5000 kbps, with High-performance mode on) the Voyager 3 measured 61.3 ms on scrolling text and 60.7 ms on a still screen, at about 51 fps. With the mode off, as we found it, it sends only 30 fps and measured 68.1 ms, so turn it on. Even at its best it has a long tail: about a quarter of our measurements landed near 170 to 190 ms, so its slow moments are much worse than its median. That puts it just behind the PiKVM, the GL.iNet Comets, the JetKVM and the Sipeed NanoKVM Pro, though quicker than the Luckfox PicoKVM (90.0 ms), the NanoKVM Full (144.8 ms) and the BliKVM (185.9 ms). It also drew 4.11 W streaming, the highest power in our fleet. At 1080p120 it stalled.

What makes that striking is the comparison to PiKVM. The PiKVM V4 Plus runs the same CM4, the same TC358743 capture, and the same uStreamer engine, and it measured 57.3 ms with its H.264 boost (60.9 ms at stock settings, which also deliver only 30 fps), about 4 ms faster, at a lower 3.53 W. Same silicon, same software core, a modest but real gap. We expected the Voyager 3 to land near the PiKVM and it landed close behind, and the gap looks like tuning. TinyPilot's High-performance mode, in its video settings and off on our unit as we found it, raises the frame rate and GPU clock; it took the Voyager 3 from 30 fps to about 51, but not to the 60 fps the PiKVM's boost option delivers. TinyPilot notes the mode increases power use and heat. This is a software and configuration outcome, not a hardware limit. Our unit also flagged undervoltage and throttling, which points at the power supply or cable and is worth ruling out, though we did not test whether it affects latency. The numbers are in our latency benchmarks and power comparison.

TinyPilot web interface with its video settings dialog
TinyPilot's video settings. Turn on High-performance mode: it took our unit from 30 to about 51 fps.

TinyPilot vs PiKVM

This is the comparison buyers actually make, and our testing gives a clear answer on the hardware: they are built on the same foundation. A DIY PiKVM or a pre-built PiKVM V4 gives you the same capture and streaming stack, faster in our measurements, and PiKVM's is the more mature ecosystem. What TinyPilot adds on top is finish and service: nicer packaging, a cleaner out-of-box experience, a warranty, indefinite software updates, and a US company to call. If those matter to you, TinyPilot is the more comfortable product. If raw performance per dollar matters, PiKVM wins, and both lose on price to the newcomers.

The TinyPilot Voyager 3 beside the PiKVM on the bench.

Software and features

Updated November 2026: TinyPilot has shipped four Pro releases since we first wrote this review, and one of them fixes the limitation we originally flagged.

The HTML5 web interface needs no client software, which is a genuine selling point over old enterprise KVMs. In use cases that means the usual out-of-band jobs: recovering a headless server that dropped off the network, installing an OS on bare metal via virtual media, reaching a colocated or edge box, and standardizing remote access across a mixed fleet of machines that lack IPMI or Intel AMT. Virtual media lets you mount an ISO for a remote OS install, there is a serial console (which needs a specific USB-to-serial adapter), and updates are frequent, with a stated commitment to indefinite free updates even after the 12-month warranty ends.

What changed in 2026, from TinyPilot's changelog:

  • Relative mouse mode (Pro 3.1.0, July 2026). A Mouse Mode toggle in System settings now switches between absolute and relative input. Relative mode sends how far the mouse moved rather than where it is, which is what BIOS and UEFI menus that ignore absolute positioning need. Click the stream to capture the mouse and press Esc to release it. TinyPilot's release post has the details.
  • Two-factor authentication (Pro 3.2.0, August 2026), with TOTP codes, rate limiting on login, and API keys for the REST API.
  • Lower-latency H.264 and LAN Monitor (Pro 3.3.0, October 2026). This is the release that added the High-performance mode we tested above, plus LAN Monitor, which discovers and watches up to 25 devices on the local network.
  • A security fix (Pro 3.3.1, November 20, 2026) that closes two NGINX vulnerabilities TinyPilot says could allow unauthenticated code execution. If you own one, install it.

One caveat on updates: moving from 3.0.2 or earlier to 3.1.0 required a factory reset, because that release moved the base OS to Debian 13. Plan for it on a unit that is already deployed.

A correction. An earlier version of this review said the Voyager 3 had absolute mouse input only, with no relative mode. That was out of date: TinyPilot shipped relative mode in 3.1.0 in July 2026, and our October retest ran 3.3.0, which includes it. Thanks to TinyPilot for pointing it out. The case that bit us was a target with a secondary monitor. Relative mode is the usual fix for that, but we have not yet retested it on our unit.

Setup itself is quick, 1:30 to a first stream, though a required update pushed a fully-ready state to about 5:44, and you have to enable SSH in settings before you can reach a shell.

In-situ shot of the Voyager 3 deployed on a real machine, showing its finished, professional presentation.

What owners say, and the price

Across three video reviews and their 34 comments, the split is consistent. Owners like the build and the software. The dominant theme, by a wide margin (we counted nine separate mentions), is that it is overpriced against sub-$100 alternatives. Commenters repeatedly line the Voyager 3 up against the GL.iNet Comet, JetKVM, and NanoKVM and conclude the finish does not justify a 4x price. One owner reported BIOS screens not showing on their earlier units, and a few argued it does little that free remote software cannot, which misunderstands hardware-level access but reflects real sticker shock.

“Seems like a quality product but compared to a sub $100 GL.iNet Comet or a JetKVM it's hard for me to justify the price even with its feature set.”
Owner comment on a TinyPilot Voyager 3 review

Alternatives

DevicePriceGlass-to-glass latency, 1080p60 (our test)Open sourceNotable
TinyPilot Voyager 3~$39961.3 msYesBest build and support, priciest, slower than PiKVM
PiKVM V4 Plus~$40057.3 ms (H.264 boost)YesSame core hardware, about 4 ms faster, more mature
JetKVM~$10359.8 msYesA quarter of the price, open firmware
GL.iNet Comet~$9054.1 msNoTied for fastest third-party KVM we tested, feature-packed
Sipeed NanoKVM~$50144.8 ms (MJPEG)PartialCheapest, security caveats

If you want the same capability for far less, the JetKVM at around $103 is the value benchmark, and the GL.iNet Comet tied for the fastest third-party device we tested. If you want the TinyPilot's foundation done faster, the PiKVM V4 Plus costs about the same and measured about 4 ms quicker. TinyPilot's case is specifically for buyers who value a polished, warrantied, US-vendor product over price and raw speed.

FAQ

FAQ

They share the same foundation: both use a Raspberry Pi with a Toshiba TC358743 capture chip and the uStreamer streaming engine. PiKVM is the more mature open-source ecosystem and, in our testing, faster (57.3 ms versus 61.3 ms for the Voyager 3). TinyPilot's differentiator is finish and service: nicer packaging, turnkey setup, a warranty, and a US company.

The Voyager 3 is $399, and the Voyager 3 Plus, which adds PoE and a second LAN port, is $549 (TinyPilot's store, November 2026). That is several times the price of newcomers like the JetKVM ($103) or GL.iNet Comet ($90) that do the same core job.

Michael Lynch, an American engineer who built and documented the business publicly. He sold TinyPilot in April 2024 to a private owner, so it remains a US-registered company but is no longer founder-run, and assembly has moved to a contract manufacturer in Vietnam.

Only if you specifically value turnkey polish, a warranty, and a US vendor with support. On measured performance it was the most power-hungry mainstream KVM we tested and slower than a PiKVM on the same hardware (61.3 ms against 57.3 ms, with High-performance mode on). For most buyers the JetKVM or GL.iNet Comet deliver the same job for a quarter of the price.

The PiKVM V4 Plus for the same foundation done faster, the JetKVM for most of the capability at around $103, and the GL.iNet Comet, tied for the fastest third-party device in our testing, for around $90.

Bottom line

We measured every number here ourselves and opened the unit. See the teardown, latency benchmarks, and power comparison for the full picture.

From the bench · ours

Reserve yours for $10.

Fully refundable until it ships, and credited against the $240 price. The first 1,000 reservations also get a WarpKVM ATX card. Ships Q2 2027.
Our own product, measured with the same method as every device on this site: 1080p60 in Chrome, median of 300 runs, video path only. The $10 deposit is fully refundable and credited against the $240 price.
Today
$10 deposit
Refundable
Fully, any time
At launch
$240, deposit credited
Ships
Q2 2027
Founders batch
First 1,000: free ATX card with the 01

Waitlist

Stay in the loop.

Launch news and new dispatches. Unsubscribe any time.