Hardware for Proxmox: When Virtualization Is Worth Planning For

Proxmox has come up several times already in this module, always as a preview, never fully explained. This lesson finally opens that door: what Proxmox actually gives you, how it changes your hardware shopping list, and, just as importantly, when it's genuinely overkill for what you're trying to build.

What Proxmox gives you, and why we're talking about it here

Proxmox is free, open-source virtualization software that turns one physical machine into a host for several independent virtual machines, each behaving like its own separate computer with its own operating system. Instead of buying one box for Home Assistant and another for a media server or a network ad-blocker, Proxmox lets you run all of them on a single piece of hardware, isolated from each other, each restartable and manageable independently. It's covered here in the hardware module specifically because the decision to use it changes what you should actually buy, before you've bought anything.

How Proxmox changes your hardware requirements

Every VM you run needs its own slice of RAM and storage carved out and reserved, on top of what Proxmox itself needs to operate. That's why 16GB of RAM becomes a much more comfortable starting point than the 8GB that's plenty for Home Assistant OS running alone, and why storage sizing needs headroom for multiple operating system installs rather than just one. A genuine SSD, not spinning storage, is effectively mandatory here, several VMs competing for disk access will expose a slow drive's limitations fast.

When Proxmox is overkill

If Home Assistant is the only thing you'll ever run on this hardware, Proxmox adds a genuine layer of setup complexity, another system to learn, patch, and troubleshoot, with no corresponding benefit for a single-purpose server. This describes the majority of readers starting this course. There's no shame in installing Home Assistant OS directly and skipping virtualization entirely, you can always add Proxmox later on new hardware if your ambitions genuinely grow beyond Home Assistant alone.

What not to do with Proxmox at the start

Don't install Proxmox purely because it sounds advanced and impressive, added complexity without a real reason to use it just adds more surface area for something to go wrong while you're still learning Home Assistant itself. Don't undersize RAM planning to "add VMs later," retroactively squeezing a new VM onto an already-tight system is a common source of frustrating performance problems. And don't skip learning basic Proxmox backup and snapshot features before relying on it, they're one of its best features and easy to overlook while focused on getting Home Assistant running.

Mini PC versus thin client for Proxmox

Both hardware categories from earlier lessons can run Proxmox well, a mini PC with 16GB of RAM is the more comfortable default choice given its newer processor generation and typically easier RAM upgrade path. A higher-RAM thin client, 8GB or more, can handle light Proxmox use too, particularly if you're only planning two or three lightweight VMs rather than a heavier multi-service setup. Either way, prioritize RAM capacity and a genuine SSD over raw processor speed when shopping specifically for a Proxmox host.

Typical setups: what people run alongside Home Assistant

Common companion VMs include a network-wide ad-blocker, a lightweight media server, a personal cloud storage tool, or a second, separate testing copy of Home Assistant for trying out changes safely before applying them to your main instance. None of these individually demand much, but stacked together they're exactly the scenario 16GB of RAM and a genuine SSD are meant to comfortably absorb, plan your hardware around the household you're actually building, not just today's starter kit.

Proxmox and a NAS: how they connect

Some readers run Proxmox and point its VM backups at a separate NAS over the network, combining Lesson 6's NAS-as-backup-destination idea with this lesson's virtualization host, two devices each doing the job they're genuinely good at rather than one device awkwardly trying to do both. This is a genuinely solid setup for anyone who already owns both pieces of hardware, no need to consolidate everything onto one box just because it's technically possible.

Home Assistant inside a VM: what to plan for

Running Home Assistant OS as a Proxmox VM, rather than Home Assistant Container directly on the host, is the recommended approach, it preserves the full Supervisor experience, add-on store, and one-click backups you'd get on bare metal. Plan for USB passthrough if you'll be using a Zigbee dongle, covered when you reach Module 6, Proxmox handles this reasonably well but it's worth reading the specific setup steps before you're standing in front of a non-working dongle.

Snapshots and backups: why they justify a bigger disk

Proxmox's snapshot feature lets you save a VM's exact state before a risky change and roll back instantly if something breaks, genuinely one of its best features for anyone still learning. Snapshots and backups both consume real disk space though, which is exactly why the storage sizing guidance in this lesson and the next one runs meaningfully higher than what a single bare-metal Home Assistant install needs, budget generously rather than filling a drive to its absolute limit.

Updates: two systems, two separate risks

Just as with the NAS route in Lesson 6, running Proxmox means keeping both Proxmox itself and Home Assistant updated on separate schedules. Proxmox releases are generally infrequent and stable, and its snapshot feature makes testing updates before committing to them genuinely low-risk, a real advantage this route has over the NAS Container approach discussed earlier in the module, since a failed update can simply be rolled back in a couple of clicks rather than requiring a manual, time-consuming, and genuinely stressful recovery process to undo it afterward.

What it costs in electricity, and whether "just start with Proxmox" makes sense

A Proxmox host running several VMs draws only modestly more power than the same hardware running Home Assistant OS alone, VMs mostly sit idle just like the host itself does most of the time. The real cost of "starting with Proxmox just in case" isn't electricity, it's the added learning curve while you're already absorbing everything else this course covers. Unless you already know you want to run other services soon, it's genuinely fine to start simple and add Proxmox later.

Proxmox hardware checklist: quick summary

What this looks like for your mini smart home

For this course's starter kit, Proxmox is entirely optional and, for most readers, not necessary yet. Keep it in mind as the natural next step once you're comfortable with Home Assistant itself and start wanting to run other self-hosted services alongside it, the mini PC and higher-RAM thin client options from earlier lessons both leave that door open without forcing the decision now.

An alternative to Proxmox worth knowing about

Docker Compose, running Home Assistant Container alongside other containerized services directly on a Linux host, achieves a similar goal to Proxmox with a lighter resource footprint and a gentler learning curve for anyone already somewhat comfortable with Linux and the command line. It trades away Proxmox's clean VM-level isolation and easy snapshot rollbacks, worth knowing this option exists even if it's outside this course's main recommended path.

The learning curve, honestly assessed

Installing Proxmox itself is genuinely approachable, a guided installer not unlike installing any other operating system, and creating your first VM is a short, well-documented process with plenty of community tutorials to follow along with. Where the real learning curve shows up is afterward: understanding networking inside Proxmox, deciding how to structure storage across VMs, and troubleshooting the occasional VM that won't boot cleanly. None of this is beyond a motivated beginner, but budget real time to learn it properly rather than expecting to pick it up in the same afternoon you're also learning Home Assistant itself for the first time.

A staged approach: install Proxmox first, add services later

If you're leaning toward Proxmox but feeling uncertain about taking it all on at once, a genuinely reasonable middle path is installing Proxmox now, creating just one VM for Home Assistant, and deliberately leaving the rest of your planned services for later once you're comfortable with the basics. This gets you the hardware-sizing benefits of planning for Proxmox from day one, the extra RAM and storage headroom, without forcing you to learn everything about VM networking and additional services simultaneously while you're still absorbing this course's core material.

A real example: consolidating three devices into one

One reader started this course with Home Assistant already running on a dedicated Raspberry Pi, a separate old laptop quietly running a network ad-blocker, and a third small device handling a personal cloud backup tool, three separate pieces of hardware, three separate power cords, three separate things that could individually fail. After reading this lesson, they consolidated all three onto a single mini PC running Proxmox with 16GB of RAM, one VM per service, and reported both a noticeably tidier equipment shelf and a single coherent backup routine covering everything at once instead of three disconnected ones. Their appliances didn't get any less useful, they just stopped needing separate physical boxes to run on.

What happens if the physical host fails

Consolidating several services onto one Proxmox host does introduce a genuine tradeoff worth naming directly: if that single physical machine fails outright, every VM running on it goes down together, rather than just one isolated device the way separate hardware for each service would. This is exactly why regular VM backups to a separate destination, whether that's a NAS as covered in Lesson 6 or simple external storage, matter more here than in almost any other setup covered in this module. Plan for that backup routine from the start rather than treating it as an afterthought once you're already several VMs deep into a consolidated Proxmox setup.

Proxmox's own web interface: a quick preview

Once installed, Proxmox is managed almost entirely through a clean web browser interface accessible from any device on your network, no separate software to install on your everyday computer. From there you create VMs, allocate RAM and storage to each, take and restore snapshots, and monitor resource usage across the whole host at a glance, genuinely approachable once you've spent an evening clicking through it, and well-documented enough that a beginner comfortable with Module 2's networking concepts should find it a manageable next step rather than an intimidating one.

Where to learn Proxmox properly

This lesson deliberately stays focused on the hardware-sizing decisions Proxmox introduces, not a full tutorial on using it, that's genuinely a separate, worthwhile topic beyond this course's scope. Proxmox's own official documentation is thorough and beginner-friendly, and the wider self-hosting community around it produces a steady stream of current, well-explained video walkthroughs, worth searching out once you've decided this route is genuinely right for you and are ready to actually sit down and install it on your chosen hardware for the first time.

Key takeaways

Lesson 8 zooms into the individual specs, disk, RAM, processor, and power, that actually matter across every hardware option this module has covered, cutting through the marketing noise.