JetKVM in a Rack: Mounting One to Four KVMs in 1U

A JetKVM is small enough to lose on a desk, which is exactly the problem once you have two or three of them wired into different hosts. Each one needs a stable HDMI run, a USB-A tether into the target machine, and a network drop, and none of that holds still sitting loose next to a server. Add a second or third unit for a second or third host and the desk around your rack turns into a pile of small black boxes with cables running in every direction. Racking them fixes the cabling, not just the look.

The enclosure is small on purpose: roughly 31 mm tall, 43 mm wide, 60 mm deep. That is well under 1U (44.45 mm per EIA-310-D), so a single JetKVM in its own mount wastes most of the rack space around it. The better question is not whether it fits in 1U, but how many fit in that same 1U once you commit to a shared mount instead of a one-off holder sized for a single unit.

The mount for this build:

What a JetKVM mount actually holds

There is no cage-sized ambiguity here the way there is with a mini PC or a NAS enclosure, where a vendor refresh can quietly shrink or grow the chassis. The JetKVM body is one shape across every configuration, PoE or not, and the housing itself has not changed since launch. What has changed is the port face: a 2026 board revision replaced the mini-HDMI jack with a full-size HDMI connector and moved the extension port from an RJ-12 jack to a dedicated 5-pin connector. If a mount's front cutout is shaped tightly to the old port outlines rather than left as an open window, a current-revision unit can foul the bezel on the taller HDMI shell. An open-window front, cut wider than any single connector needs, does not care which board revision you are holding.

PoE is a build option on the JetKVM, not a separate model with its own dimensions, and it uses the same roughly 31 x 43 x 60 mm body as the standard unit. That is easy to get wrong when shopping, because "JetKVM PoE" gets used two different ways online. One is the integrated PoE unit with the splitter built into the board, which needs no extra room in the mount. The other is a standard JetKVM paired with an external PoE splitter dongle, which is common enough that competitors sell mounts built specifically around the combination. That dongle needs its own space on the plate, and a tight single-unit mount sized for the JetKVM alone will not have room for it. Worth confirming which version you actually have, or are about to buy, before ordering a multi-unit mount sized with no slack.

One unit or four in the same 1U

Because the JetKVM body is so far under 1U height, the practical design decision is how many units you fit into one row rather than whether a single one fits. A single-unit order ships with a half-width blank so the row still looks finished instead of leaving an open gap next to one small device. Two sit side by side with room to spare between them. Three or four is where a shared mount earns its keep: a homelab running separate hypervisor hosts, each with its own out-of-band KVM for when the host locks up or the network stack is the thing that is broken, consolidates four JetKVMs into the same 1U a single mini PC mount would occupy on its own.

The tradeoff is cable density, not mounting difficulty. Four JetKVMs in one row means four HDMI runs, four USB-A tethers, and four network drops all converging on the same few inches of rack. None of that is a mount problem exactly, the plate holds the units fine either way, but it is worth routing the cables before tightening anything down. Reaching behind a fully populated plate to redo one cable without disturbing the other three is its own kind of annoying, and it is the sort of thing you only think about after the first time you have to do it.

19" rack or 10" mini rack

Both sizes hold the same set of configurations: 1x, 2x, 3x, or 4x JetKVM in 1U. The call is really about what else lives in the same rack rather than anything specific to the KVM itself. A 19" rack already carrying switches, a firewall, and a couple of servers gets the 19" modular JetKVM mount, sharing rail space with everything else at standard rack width and taking up one more thin slice of a row that is already full of other 1U gear. A 10" mini rack dedicated to network equipment and a couple of mini PCs gets the 10" version instead, which keeps the KVM row proportional to a desk-sized enclosure rather than looking oversized bolted next to a mini PC a fraction of its width.

Side preference matters a little on the 19" version too. The multi-unit configurations are handed depending on which side of the rack you are filling from, left or right, so order the orientation that matches how your existing row is laid out rather than fighting a mismatched cutout after the mount arrives. It is a five-second decision when you are ordering and a much bigger one once the plate is already in the rack.

Thermals and why KVMs rarely need to think about it

A JetKVM draws very little power on its own, roughly in line with a small single-board computer, and the chip doing HDMI capture and network streaming is not working hard enough to need forced airflow. That is one real advantage of racking these over something like a mini PC: there is no exhaust direction to plan around, no vent to keep clear, and no fan noise to factor into where the mount sits relative to anything else in the rack. The mount's job is just to keep the unit still and the ports accessible, not to manage heat.

PoE shifts the power budget slightly, since the switch feeding that port is now doing more work, but it does not meaningfully change the thermal picture for a device this small. If you are running four PoE JetKVMs off the same switch, the thing worth checking is the switch's PoE budget, not the mount or the units themselves.

Cabling for a multi-host out-of-band setup

If the goal is out-of-band access to several hosts at once, plan the cable runs before racking anything rather than after. Each JetKVM needs its own HDMI source from the target machine and its own USB-A connection back into it for keyboard and mouse emulation, which means your rack needs that many free HDMI and USB ports somewhere nearby, not just network drops for the JetKVMs themselves. A patch panel or a labeled cable run at the back of the rack saves real time the first time one host locks up and you need to know, at a glance, which of the four JetKVMs in the row is actually watching it.

Power is the other detail worth totaling up front. Four standard JetKVMs means four small power adapters competing for outlets unless you are running the PoE variant, in which case the upstream switch needs the budget for it instead. Either way, it is worth adding up the draw before assuming a shared power strip or PoE switch has room left over, especially once the rest of the rack is already drawing from the same circuit.

Where this fits next to the rest of a homelab rack

A JetKVM mount is usually the smallest thing going into a rack that otherwise holds switches, a firewall, and one or two servers or mini PCs, and that is worth planning for rather than treating as an afterthought. Put the KVM row somewhere you can actually reach the front ports without unracking anything else, since you are far more likely to be plugging and unplugging HDMI and USB cables on these units than on almost anything else in the rack. A row near eye level, rather than buried at the bottom behind cable management arms, saves time on the one task you will repeat most often.

It is also worth deciding up front whether the KVM row is permanent or something you expect to grow. Going from a 1x to a 4x configuration later means swapping the whole mount rather than adding to it, since the plate is sized to the unit count at order time. If there is any chance a second or third host gets its own out-of-band KVM in the next year, ordering the larger configuration now, even partially populated, avoids a second order and a second cutout in the rail later.

Wrap-up

A JetKVM mount is a simple problem with a straightforward answer. Pick 19" or 10" to match the rest of the rack rather than the KVM itself, pick a configuration count that matches how many hosts you are actually watching, and confirm which port revision and PoE variant you are holding before ordering, since both affect what the mount needs to clear. The hardware does not ask for much beyond that. The real win is getting four loose dongles into one organized row with their cables planned out, instead of four cables draped over whatever surface happened to be nearby when you set them up.

Mounts in this build