Proxmox is the magic solution for self-hosters #

Open YouTube, type "home lab" and you'll find dozens of enthusiasts running Proxmox on their home server. Same thing on X (Twitter), Reddit, various forums... It's like the new religion for self-hosters. And just like any religion, questioning it gets you some interesting reactions.

Proxmox VE is an open-source virtualisation platform based on Debian that allows you to manage KVM virtual machines and LXC containers through a nice web interface. On paper that sounds great. In practice, for a home lab, I think it's massive overkill.

What Proxmox actually is #

Proxmox VE is fundamentally a management layer on top of KVM (hypervisor) and LXC (containers). It adds :

A web GUI to manage VMs and containers
Clustering support (manage multiple physical nodes)
HA (High Availability) features
A storage abstraction layer
Backup and snapshot tooling

All of this is great if you're running a small business with 3 or 4 physical servers, where you need to move VMs between nodes, do live migrations, or manage a team of peoples who need a GUI.

But for a home lab with one single machine ? Really ?

You are running a full Debian-based OS + a Proxmox management stack just to... run a few containers and maybe one or two VMs that you could run directly on the host.

The "YouTuber home lab" effect #

I think a big part of the Proxmox hype is driven by content creators. Running Proxmox "looks" profesionnal. The web interface is polished, the dashboards are cool, the screenshots look great in a thumbnail.

But most of these setups are a single mini-PC or a repurposed workstation running :

A Pi-hole VM
A Home Assistant VM
A VPN container
Maybe a Nextcloud instance

Obviously you'll need at least an Intel Core Ultra and 64GB of DDR5 for all of this. Don't cheap out.
... This is not a data center. This is a home server. You don't need HA, live migration, or a cluster management tool for this.

The gap between what Proxmox provides and what a typical home lab actually needs is enormous.

I've occasionally stumbled upon American Youtubers running full enterprise rack setups at home. Multiple 2U servers, proper patch panels, PDUs, the whole thing. In their living room. I have a lot of respect for the dedication, but also genuine concerns about their electricity bill and their relationship with their significant other. These people are built different 😅

What you actually need : containers #

The core need for a home lab is simple : isolation and BACKUP. You want your services isolated from each other, easy to backup individualy, and easy to restart independantly.

For this, full VMs are almost never necessary. Containers are the right tool.

FreeBSD jails #

I've been running all my services in FreeBSD jails for years. A jail is a lightweight OS-level isolation mechanism, native to FreeBSD since version 4.x (year 2000...).

A jail is not a VM. It shares the host kernel, which means :

Near-zero overhead (no hypervisor, no emulation)
Near-instant start/stop
Full network isolation
Full filesystem isolation
Easy to snapshot with ZFS

My entire stack — Nginx, Nextcloud, Gitea, Vaultwarden, MariaDB, Redis, Navidrome, Grafana, Garage S3, and more — runs on a single Intel N100 box with 16GB of RAM. The CPU is mostly idle.

No Proxmox. No cluster. No web GUI. Just jails, rc.conf, pf.conf and a backup script.

Linux LXC : the same idea ... well, kind of #

If you're running Linux and want the same lightweight isolation philosophy, LXC is the answer. LXC (Linux Containers) has been part of the kernel for a long time and provides the same OS-level isolation as FreeBSD jails without the hypervisor overhead.

You can use it directly, or through lxd which adds a management daemon and CLI on top.

The point is : this is already built into your OS. You don't need to install a separate platform on top.

note Docker is also built on top of the same Linux kernel primitives (namespaces + cgroups). The difference is that LXC gives you a full system container (like a minimal OS), while Docker is designed around single-process containers. For self-hosting services, both work fine.

When Proxmox actually makes sense #

To be fair, I don't want to dismiss Proxmox entirely. There are real use cases where it makes sense :

You have multiple physical machines and want to manage them from a single interface.
You need live migration of VMs between nodes (hardware maintenance without downtime). — At home. Really. Your Pi-hole can survive a reboot, I promise.
You're running Windows VMs (Jails/LXC won't help you here, you need full virtualisation — though Bhyve on FreeBSD or plain KVM on Linux will do the job just fine without Proxmox on top).
You need to onboard other people who are not comfortable with the command line. This can indeed be useful if you want your wife or your 5-year-old to start your VMs while you're away. :D
You want to learn virtualisation for professional purposes — even if there is a 99% chance your company runs VMware and not Proxmox 😄
And yes, I'll admit it : sometimes it's just nice to have a web UI to click around instead of a terminal. Not everything needs to be justified with performance metrics.

These are all legitimate reasons. And on that last point — Proxmox is probably a very solid VMware replacement for companies looking to escape Broadcom's... creative new licensing strategy. If your company is currently running vSphere and looking for an exit, Proxmox is worth serious consideration.

But in the typical home lab context described by most Youtubers — one box, Linux services, one person managing it — none of these reasons apply.

The hidden cost of Proxmox at home #

Running Proxmox on a home lab is not free (in the technical sense) :

Memory overhead : Proxmox itself + each VM has its own kernel/OS. Running 5 VMs means running 5 kernels, 5 init systems, 5 copies of various daemons. Containers are much more efficient.
Storage overhead : Full VM disk images consume significantly more space than container root filesystems.
Complexity : More components = more things to understand, to maintain, and to break. Your Proxmox cluster state, your VM configs, your storage pools... Another layer to backup, another layer that can fail.
Update surface : You're now running Proxmox (Debian-based), plus the guest OS of each VM, plus your applications. That's a lot of apt upgrade to run and a lot of potential breaking changes.

Reminder :
Overall system reliability is the product of the individual reliability of each component.
The more components, the higher the probability of failure.

Resist the hype : Install FreeBSD #

The home lab communauty is great, but it's also victim of its own content creation dynamic. Complex setups make better videos. Proxmox dashboards look impressive. But impressive is not the same as necessary.

If your goal is to run services reliably on a modest machine, keep it simple :

FreeBSD : use jails, they're built-in, lightweight, and battle-tested since 2000.
Linux : use LXC directly, or at worst Docker/Compose if you prefer that ecosystem.

You don't need a hypervisor layer, a web management platform, and a cluster engine for a single box at home. Save the RAM, save the complexity, and spend that time actually using your services instead of managing the infrastructure that runs them.

#self-hosting #FreeBSD #jails #infrastructure #Linux