Lenovo ThinkCentre Tiny Homelab: M710q, M720q, M920q, M10q

If you want the cheapest honest path into a Proxmox cluster, it runs through a pile of used Lenovo ThinkCentre Tiny machines. They are everywhere on the secondhand market, they take real desktop CPUs in a chassis the size of a hardcover book, and three of them line up across the front of a 10-inch rack in a single slot. Corporate refresh cycles dump them by the thousand, which keeps prices low and matched sets easy to assemble. This is a guide to doing that deliberately: what the Tiny actually is, how the M710q, M720q, M920q, and M10q differ, which upgrades are worth doing, the BIOS settings that will eat an evening if nobody warns you, and how to rack a stack of them without building a cable-trace puzzle.

What the ThinkCentre Tiny actually is

Lenovo's Tiny form factor is the 1-litre class of small-form PC, a slab roughly 35 mm thick and about 180 mm on its longer sides. Inside that volume Lenovo fits a socketed desktop CPU on an LGA board, two SODIMM slots for DDR4, an M.2 NVMe slot, a second M.2 for wireless, and on most models an internal 2.5-inch SATA bay. It runs from an external power brick, usually a 65 W or 90 W barrel-jack adapter depending on the CPU it shipped with.

The detail that matters for a homelab is the socket. Unlike many mini PCs that solder the processor down, the Tiny uses a standard LGA socket and accepts Lenovo's supported list of 35 W and 65 W desktop chips. A cheap base unit can be re-CPU'd later with a faster part pulled from another machine, and the silicon inside is a real desktop part rather than a thermally throttled laptop one. For a cluster you intend to lean on, that is the difference between a node that holds its clocks under sustained load and one that sags. It also means a chassis you rack today can be re-spec'd for years, which is why a generation-agnostic mount like the 10" Lenovo ThinkCentre M720q, M920q, M710 & M10q Tiny PC Rack Mount outlives any single CPU you put behind it.

Why Tiny is the cheapest way into a cluster

Proxmox wants an odd number of nodes to hold quorum when one drops, and three is the smallest number that gives you that. Three ThinkCentre Tinys, each with a couple of cores to spare and 32 to 64 GB of RAM, comfortably run a homelab's worth of services with one node's worth of headroom held back for migrations and failures.

The case for the Tiny specifically, over a tower or a single larger box, comes down to a few things:

• Secondhand supply is enormous. ThinkCentre Tinys came off corporate leases in vast numbers, so matching three identical units is easy and the per-node price is low. This is the single biggest reason they beat boutique mini PCs for a cluster.
• Power and noise disappear. Each node idles in the single-digit-to-low-teens watts from a small fan that, at idle, is close to silent. Three together draw less than one mid-tower and make far less noise than any 1U server.
• Real failure domains. Three physical machines mean you can pull the power on one and watch the cluster keep running. A single host with three VMs pretending to be a cluster teaches the software but not the recovery, and recovery is the part worth practicing.
• They mount in one rack slot. Three Tinys stand side by side across a 10-inch rack opening, so an entire cluster lives in a single 1U line instead of sprawling across a shelf. The 10-inch ThinkCentre Tiny rack mount is built around exactly that layout.

None of this is glamorous, and that is the appeal. A Tiny cluster is the boring, reliable substrate you run everything else on top of.

M710q, M720q, M920q, M10q: which to buy

The model names encode the generation and tier, and the same bracket fits all four because the chassis footprint is shared across them. What you are actually choosing between is CPU generation and how much BIOS control Lenovo left you.

• M710q. The oldest of the four, built around 6th and 7th-generation Intel. Cheapest by a clear margin and perfectly serviceable as a quorum node or a light worker. The limits are DDR4 at lower speeds and an older CPU list, so it is the budget end rather than the one you pin heavy VMs to.
• M720q. The value sweet spot for most homelabs. 8th and 9th-generation Intel, the fuller BIOS, both SODIMM slots, the M.2 NVMe slot, and the internal 2.5-inch bay. A used M720q with an i5 is enough for a node running a handful of VMs and containers, and it is common enough to buy three that match.
• M920q. The premium tier of that generation, with the best-supported CPU list including 65 W i7 desktop parts, vPro on many units, and the most complete feature set. If you want one strong node to pin your heavier VMs to, the M920q is where to spend.
• M10q. Lenovo's naming for the ThinkCentre M70q/M75q-class Tiny in some markets and listings, spanning newer generations. Treat the badge as a hint and read the actual CPU generation behind it, because that is what determines core count, power efficiency, and how long the box stays relevant.

Across all four, the generation of the chip matters more than the tier. For a 2026 build, aim for the newest generation your budget allows rather than the highest badge, and do not pay a premium for an old CPU in a fancy model number. Whatever mix you land on, the ThinkCentre Tiny 1U mount holds the M710q, M720q, M920q, and M10q chassis interchangeably, so a mixed-generation cluster still racks as a matched set.

RAM and SSD: the upgrades worth doing

Each Tiny takes two DDR4 SODIMMs. Most homelabbers land on 32 GB per node as the comfortable default and 64 GB as the ceiling the platform supports, which is generous for a three-node cluster. Memory is the first upgrade worth making, because RAM is what you run out of long before cores on a virtualization host, and used SODIMMs are cheap. Buy the machine with whatever it ships with, then top it up rather than paying the seller's premium for pre-maxed units.

Storage is where the Tiny is a little tight, and it is worth planning before you buy. You have one M.2 NVMe slot and, on most M720q and M920q units, one internal 2.5-inch SATA bay. That is enough for a fast NVMe boot drive plus a SATA data disk per node, which suits a Ceph-light or ZFS-replication setup where each node carries its own storage. What you do not have is room for a pile of disks, so if the plan involves serious shared storage, that lives on a separate NAS and the Tinys are compute. A cheap NVMe boot drive and a used 2.5-inch SSD per node is the standard recipe, and it keeps each box self-contained.

The networking reality

The ThinkCentre Tiny ships with a single onboard gigabit NIC. For a basic cluster that is workable, but the cluster heartbeat, live-migration traffic, and storage replication all share that one link, and gigabit is the ceiling. Two workarounds exist. Many Tinys have a Lenovo flex-I/O bay at the rear that accepts an optional second Ethernet or SFP module, which is the clean fix if you can find the module. Otherwise a USB 2.5-gigabit adapter or an M.2-to-NIC card is the homelab route, at the cost of the WLAN M.2 slot or a USB port.

Plan your switch ports around whichever you choose, and remember that whatever you uplink to has to be reachable from the front of the rack, which is half the reason the cluster wants a proper bracket rather than a shelf. A mount like the 10-inch ThinkCentre Tiny bracket keeps that single NIC, and any second adapter you add, at the front where you can actually trace the cables.

Mounting a stack in a 10-inch rack

A 10-inch rack has an internal mounting width that lines up neatly with three Tinys stood on edge side by side, which is the whole trick. A 1U opening is 44.45 mm tall under the EIA-310-D standard, and the Tiny at roughly 35 mm thick stands within that height on its broad face, so a row of three sits flush at the front plane of a single 1U slot. The ThinkCentre Tiny 10-inch rack mount is designed around that geometry, carrying the cluster across one rack line with the rear I/O of each unit presented where you can reach it.

A few practical notes once the bracket is in:

• Orient for the ports you touch. The Tiny puts Ethernet, USB, video, and power on the rear face. Mount so that face lands at the side of the rack you patch from, because a cluster node you reconfigure often is one you do not want to unseat to reach a cable.
• Power bricks are the hidden bulk. Three Tinys mean three barrel-jack adapters, and those bricks are larger than the computers. Decide where they live before you mount, whether that is a shelf below, a cable tray, or velcro to a rail, because three loose bricks behind the rack undo the tidiness the bracket bought you.
• Label the nodes at the front. node1, node2, and node3 look identical. A small label on each at the rack face saves tracing a cable to work out which box you are about to power down. The ThinkCentre Tiny 1U bracket presents all three faces in a row, so a label strip across the front is all it takes.

BIOS gotchas

A few Lenovo-specific settings reliably trip people up on the first cluster build, and all of them live in the BIOS:

• Virtualization is not always on. Intel VT-x and VT-d are the toggles Proxmox needs for full virtualization and PCI passthrough. On used units they are often disabled from whatever the previous owner did. Turn both on before you wonder why a VM will not start.
• After Power Loss. By default a Tiny may stay off after a power interruption, which is the wrong behavior for a headless node. Set "After Power Loss" to power on so the node rejoins the cluster on its own after an outage.
• Smart USB / wake behavior. Deep-sleep and USB-wake settings can interfere with wake-on-LAN and remote power-on. If you plan to wake nodes over the network, adjust these so the NIC stays alert.
• Secure Boot and boot order. Proxmox installs cleanly, but Secure Boot and a misremembered boot order send you to a black screen. Set the NVMe boot device explicitly and decide on Secure Boot before you install rather than after.

Set these once on each node, photograph the screens, and the next time you add or reimage a box you are not rediscovering them from scratch.

Wrap-up

A stack of used ThinkCentre Tinys is about as much cluster as most homelabs ever need: socketed desktop CPUs, room for 32 to 64 GB of RAM each, real failure domains you can pull the plug on, and a power and noise budget that vanishes into a quiet room. Buy the newest generation your budget reaches, top up the RAM and drop in an SSD, settle the BIOS toggles before you install, and keep the single-NIC limit in view.

Then rack them like the unit they are. Three identical boxes balanced on a shelf is a cable-trace puzzle waiting to happen, and a single 1U bracket that lines all three up at the front of a 10-inch rack turns a pile of mini PCs into a cluster you can actually service.