Shop for a home lab server and the advice splits into two camps: a $150 used office PC and a prayer, or a $1,200-plus tower with more drive bays than you’ll fill in five years. This build takes the deliberate middle. For roughly $500–700 you get a machine that runs Proxmox VE, keeps a dozen services alive around the clock, and still has headroom to spin up a virtual machine just to see what happens. There are two ways to get there, a 12th or 13th gen Intel Core i5 mini PC or a compact ITX build with real drive bays, and they share the same brain: 32 GB of RAM, an NVMe drive for the fast stuff, a hard drive for the bulky stuff, and Intel’s Quick Sync media engine.
It’s aimed at the self-hoster who has outgrown a Raspberry Pi or a single Docker host on a repurposed laptop: you want snapshots before you break things, a proper VM for the smart home hub, containers for everything else, and some network storage without buying a dedicated NAS. Here’s the hardware, the reasoning behind it, and what it actually runs.
The build at a glance
| Component | This build |
|---|---|
| CPU | Intel Core i5-12450H/13500H mini PC, i5-12400 ITX, or N305 for lowest power |
| RAM | 32 GB (DDR4 or DDR5, platform-dependent) |
| Storage | 1 TB NVMe (OS, VMs, apps) + 4–8 TB CMR HDD |
| Transcoding | Intel Quick Sync: H.264, HEVC 10-bit |
| PSU | External power brick (mini PC) or 450 W 80 Plus Bronze (ITX) |
| Case | Palm-sized mini PC or compact ITX tower with 3.5-inch bays |
| Idle power | Roughly 15–40 W depending on route and drives |
| Noise | Quiet; a faint fan hum under sustained load |
| Indicative budget | $500–700 as of mid-2026, prices vary |
Route one: the mini PC
A barebones mini PC around an Intel Core i5-12450H or i5-13500H, roughly $250–350. This is the Beelink, Minisforum, and GMKtec class of machine: a mobile CPU, laptop-style cooling, an external power brick. Add 32 GB of SO-DIMM memory (around $80) and a 1 TB NVMe drive (around $80) and you have a complete Proxmox host for roughly $450–550 as of mid-2026, prices vary, one that sips power at idle and disappears onto a shelf. The Intel N305 variant swaps performance cores for eight efficiency cores: even lower draw and near-silence, but single-channel memory and a lower ceiling for how many VMs feel comfortable. It’s the right pick when the electricity bill outranks ambition.
The route’s trade-off is storage. Most mini PCs give you one 2.5-inch bay or a second M.2 slot, not a stack of 3.5-inch bays. The light-NAS part of this build then means a big 2.5-inch SSD or a USB-attached drive, both workable for documents, backups, and a modest media library, neither ideal for serious bulk storage. If terabytes are a headline requirement, take route two.
Route two: the compact ITX build
An Intel Core i5-12400 in a compact case, roughly $600–700 all in. The 12400 (around $150) brings six performance cores and the UHD 730 iGPU with the same Quick Sync engine. Pair it with an H610 or B760 board that has four SATA ports (around $120), 32 GB of DDR4 (around $70), the same 1 TB NVMe (around $80), and a 4 or 8 TB CMR NAS drive (around $100–180). A 450 W 80 Plus Bronze power supply (around $60) is more than this machine will ever ask for, the stock cooler is genuinely adequate for a 65 W chip, and a compact case with a couple of 3.5-inch mounts (around $80) keeps the footprint civil. Skip the hard drive on day one and the total lands close to $500; the SATA ports will still be there when the storage itch arrives.
Proxmox VE is what makes it balanced
The hardware is ordinary on purpose; the hypervisor is what stretches it. Proxmox VE costs nothing to run (the enterprise update repository is optional), and it turns one box into many: full virtual machines where isolation matters, lightweight LXC containers where it doesn’t, and snapshots plus scheduled backups over everything. Break a service at 11 p.m., roll back, sleep. That safety net, more than any line on the parts list, is the difference between a homelab you experiment with and one you tiptoe around.
Run Docker inside a VM, not inside an LXC container. Nesting Docker in LXC can be made to work, but it has a long history of breaking after kernel updates, and the Proxmox developers themselves recommend a VM for Docker workloads. One Debian VM carrying the whole Docker stack gives your containers a stable home, and snapshotting that single VM backs up all of them at once.
What this build actually runs
A sensible layout looks like this: Home Assistant OS in its own VM, where its update mechanism works exactly as designed, a Debian VM carrying the Docker stack, and an LXC container sharing the data drive over Samba as the light NAS layer. Inside the Docker VM sit the usual suspects: Jellyfin for media, Nextcloud for files, contacts, and calendars, Pi-hole for network-wide ad blocking, and the *arr suite, Sonarr, Radarr, and Prowlarr, keeping the library organized while qBittorrent handles downloads of legally distributed content.
Quick Sync means everyday media duty is covered: direct play on the local network, hardware transcoding when a phone or an aging tablet needs a smaller stream. Qualitatively, this is a machine for a household, not an audience. If 4K streaming to several TVs and remote family is the actual mission, the 4K Media Server Powerhouse is the purpose-built tool for that job; this build’s job is breadth, running the media server and the smart home and the file sync and the experiments at the same time.
Power draw and noise
Expect roughly 15–25 W at idle for the mini PC route and 25–40 W for the ITX box with a hard drive spinning, figures that make 24/7 operation a non-event on the electricity bill. Acoustically, the mini PC’s small fan is inaudible at idle and a soft hum under sustained load; the ITX build with a stock cooler and one slow case fan is effectively silent from a couple of meters away, with the hard drive as the loudest component. Neither machine needs a closet or a basement. Both can live on a bookshelf.
Upgrade paths
- 64 GB of RAM, the first upgrade most people actually make once the VMs start multiplying; both routes take it, N305 boards excepted.
- More disk: the ITX route has SATA ports and mounts waiting, while the mini PC grows through a larger NVMe or a USB enclosure.
- 2.5 GbE networking, already onboard on many of these machines; the switch is usually the missing piece.
- A second node: add a cheap N100 box later and Proxmox clustering turns the lab into a two-node setup with migration between machines.
- An Intel Arc GPU on the ITX route if AV1 encoding or heavier transcoding ever becomes the job.
This homelab build: pros and cons
- VMs, LXC containers, and a full Docker stack on one $500–700 machine
- Quick Sync covers everyday transcoding with no discrete GPU
- Low idle draw and near-silence make 24/7 operation painless
- Two form factors, one identical software stack: pick your size
- No ECC memory in this consumer platform class
- Mini PC route is thin on drive bays; bulk storage wants the ITX build
- 32 GB fills up faster than expected once VMs multiply
- Not sized for heavy multi-stream 4K transcoding duty
Who is this build for
Build this if you want one machine that does a bit of everything: the smart home, the media library, file sync, ad blocking, and a sandbox for whatever you read about next weekend. It’s the classic second server, the one you buy once the first taste of self-hosting turns into a habit, and Proxmox means it can reinvent itself for years without a reinstall. Skip it if a media library is the whole point, the dedicated 4K build serves that mission better, or if you’re not sure yet what you’d run; in that case our homelab setup guide for beginners starts cheaper and covers the fundamentals this build assumes. Somewhere between a first Raspberry Pi and a rack, there’s this: a balanced homelab that earns its keep every single day.