Unraid vs Proxmox for Home Server: Which One to Run

Unraid vs Proxmox: pick Unraid if the box is mostly storage, meaning mixed-size drives behind parity, Docker apps installed from templates and a VM or two, for a $49 to $249 perpetual licence. Pick Proxmox VE, which is free, if the box is mostly virtual machines on matched ZFS disks, or you want clustering and Proxmox Backup Server.

The two get compared as if they were rivals, and they mostly are not. Unraid is a storage operating system that learned to run Docker containers and virtual machines. Proxmox VE is a hypervisor that expects you to build the storage layer yourself. On one mini-PC with mismatched drives, that difference decides the outcome before any feature list does. You can also run Unraid as a VM on Proxmox, covered below.

What this comparison is judged on

The workload is the usual single-box home server: a few terabytes of media and backups, a dozen Docker apps, one or two VMs, and a wish to add a drive whenever one goes on sale. Every claim below comes from the two projects’ own documentation, current as of Unraid 7.3.3, released 8 October 2026, and Proxmox VE 9.2, released 21 May 2026. Nothing here is a benchmark.

Spec table

Storage is where they diverge

Unraid’s array is the whole reason it exists. The array documentation is blunt about the trade: “Unraid stores each file on a single disk. This means read speeds won’t be boosted by the combined speeds of multiple drives.” In return, up to two parity drives protect disks of any mix of sizes, with one rule: “No disk can be larger than your smallest parity drive.” Adding a disk needs no re-layout, and losing more disks than you have parity costs only the files on those disks. The mechanism is walked through in how Unraid storage works.

Proxmox gives you nothing of the kind. Its ZFS guide covers mirrors, RAIDZ1 through RAIDZ3 and dRAID, says “you need at least 8GB to start,” and adds that the project “recommend[s] the use of high quality ECC RAM.” Unraid has offered ZFS pools since 6.12, and its own ZFS page carries the same expansion caveat: “you can’t add a single disk to an existing vdev using the WebGUI.”

The practical reading: three drive sizes bought over four years means Unraid, because it uses all of that capacity without a plan. If they are matched pairs and you want checksums on every block, either works, and Proxmox does it for free. Both now ship OpenZFS 2.4, so a ZFS pool behaves much the same on either; the parity array is what Proxmox lacks. Against a NAS appliance or TrueNAS, see Unraid vs Synology (and TrueNAS); for the drives themselves, best hard drives for Unraid.

Apps: Docker on Unraid, Docker-in-a-VM on Proxmox

Most comparisons get this part wrong. Proxmox has containers, but they are LXC system containers, not Docker. The container docs describe them as sharing the host kernel with runtime costs that are “low, usually negligible.” Since 9.1 an LXC container can be created from an OCI image, but the FAQ still says “It is not recommended to run docker directly on your Proxmox VE host” and calls application containers as Proxmox Containers “currently a tech preview.” The supported path for a compose stack is a Debian VM with Docker inside it: one more layer to patch, back up and feed RAM. Proxmox LXC vs VM covers when each fits.

Unraid runs Docker on the host and wraps it in templates. Community Applications is “a curated catalog of over 2,000 free Docker containers and plugins” behind an app-store style Apps tab, with appdata on the cache SSD and media on the array. If your dozen apps are the ones everyone runs, it is an afternoon, and how to set up Unraid Docker containers walks through it. The caveat: once you want a multi-container stack with shared networks and healthchecks, you are writing a compose file by hand anyway.

VMs: both run KVM, only one is built around it

Unraid’s VM documentation lists the same stack Proxmox uses: KVM, QEMU, libvirt and VFIO with IOMMU for passthrough. It asks for at least 4 cores and 8 GB of RAM, with 16 GB recommended. For one Windows VM or Home Assistant OS next to the array, it is fine.

Proxmox is the hypervisor story: clusters, live migration, high availability, and a backup system with stop, suspend and snapshot modes, scheduled jobs and deduplication on Proxmox Backup Server. The 9.2 release added a dynamic load balancer for HA guests, which tells you who the product is for. On an N100 with 16 GB you will admire most of that and never touch it. But none of it is bolted on, and the day you want a second node, Proxmox already knows what one is.

Cost, and the boot drive nobody mentions

Unraid is paid software: $49 for Starter with 6 attached devices, $109 for Unleashed, $249 for Lifetime, all perpetual, as listed on Unraid’s store in October 2026. The licensing FAQ says Starter and Unleashed include one year of updates, then an optional $36 annual extension, and that without it “you keep your license and can use your current version of Unraid OS indefinitely.” Unlimited means “not limited by the license, but by hardware and OS constraints,” and the array caps at 30 devices, 28 data plus 2 parity. Two SSDs and four drives already fill Starter’s six slots.

Proxmox VE is free under the AGPLv3. The package repositories page says the no-subscription repository “can be used for testing and non-production use,” and the community subscription is 120 EUR per socket per year as listed in October 2026. At home nearly everyone runs the no-subscription repository and clicks through the login nag.

Boot media bites late. Unraid long required a USB flash drive holding the licence, and cheap flash drives die. The 7.3.0 release adds Internal Boot from NVMe, SSD or eMMC and moves new keys to TPM-based licensing “because it is more reliable than flash-based licensing.” If the USB dongle was your reason to skip Unraid, that reason ended in May 2026, on bare metal at least. Inside a Proxmox VM the licence still needs a flash drive.

Can you run Unraid on Proxmox?

Yes. The usual hybrid puts Proxmox VE on the hardware and Unraid in a VM that owns the data drives through a passed-through SATA controller or HBA. Two limits apply: Lime Technology does not officially support virtualized Unraid for production data, and the licence must stay on a USB flash drive passed into the VM.

New keys use TPM licensing “when possible,” but the TPM licensing FAQ answers “No, this is not supported” for TPM inside an Unraid VM, and a forum moderator confirms “TPM only works with a bare metal install.” A key already on TPM has to move back to a new flash drive. Booting is a separate choice: the Unraid Installer targets “remote or virtualized environments,” so the OS can boot from a virtual disk while the flash drive, labelled UNRAID per the internal boot FAQ, only carries the licence.

The setup on Proxmox VE 9.2:

1. Enable IOMMU. Set VT-d or AMD-Vi to Enabled in firmware; the passthrough wiki warns that “Auto” is not the same. Kernel 7.0 needs no boot flag: per the PCI(e) passthrough guide, AMD’s IOMMU is on by default and Intel’s has been since kernel 6.8.
2. Load VFIO. Add vfio, vfio_iommu_type1 and vfio_pci to a file in /etc/modules-load.d/, run update-initramfs -u -k all and reboot. Check that the disk controller has an IOMMU group to itself with pvesh get /nodes/<node>/hardware/pci --pci-class-blacklist "".
3. Create a q35 VM with OVMF. PCIe passthrough “is only available on q35 machines.” Add the EFI disk; per the admin guide, pre-enrolled keys enable Secure Boot by default, and Unraid’s fix for “prohibited by secure boot policy” is to turn Secure Boot off. Unraid’s own guide sizes a test guest at 2 to 4 cores and 4 to 8 GB.
4. Pass the flash drive under Hardware, Add, USB Device, by vendor and product ID, and put it first in the boot order.
5. Pass the controller with qm set <vmid> -hostpci0 01:00.0,pcie=on. The host “cannot use that device anymore,” so Proxmox’s own boot drive and VM storage need a different controller, typically NVMe.
6. Build the array from the passed-through disks as on bare metal.

The trade-offs are concrete. A VM with USB passthrough cannot move online to another host. VMs inside the Unraid guest need nested virtualization (qm set <vmid> --cpu host plus kvm-intel nested=Y on the host), which Proxmox’s nested virtualization page treats as fit for testing, not production; Docker containers need none of it. The split that holds up: Proxmox runs the VMs, Unraid runs the array, shares and Docker.

Proxmox Backup Server on Unraid

Proxmox Backup Server runs on Unraid two ways: as a VM installed from the official PBS 4.2 ISO in Unraid’s VM manager, or as the proxmox-backup-server container in Community Applications. The VM runs Proxmox’s official build. The container is quicker, but it is an unofficial build without ZFS, shell access or PAM logins.

The PBS installation guide calls installing it on the Proxmox VE host “not recommended,” so that backups survive a failed host, which makes an always-on Unraid NAS a natural home for it.

As a VM:

1. Download the PBS 4.2-1 ISO (1.48 GB, updated 29 April 2026) and create a Linux VM from it.
2. Give it at least 4 cores and 4 GiB of RAM plus 1 GiB per TiB of backup storage, with a 32 GiB OS disk; the 2-core, 2 GB minimum is for evaluation only.
3. Put the datastore on its own vdisk or a passed-through drive, formatted ext4, XFS or ZFS. The storage docs need at least 65538 subdirectories per directory, and FAT is not supported.
4. Prefer an SSD pool. PBS recommends fast local storage with high IOPS, ideally enterprise SSDs, and on hard drives a metadata cache such as a ZFS special device mirror. A vdisk on the parity array pays the parity write penalty on every chunk.
5. Add it to Proxmox VE as backup storage.

The Community Applications template runs ayufan/proxmox-backup-server with host networking and the web UI on port 8007, config under /mnt/user/appdata/pbs/, the datastore at /mnt/user/pbs_backup/, a 2 GB memory cap and /run on tmpfs, without which logins fail. Change the default admin / pbspbs login first. The upstream project calls itself an “Unofficial, and unmaintained build of proxmox-backup-server”: fine for a lab, weak for the only copy of your VMs.

Where each one wins

Unraid wins on mixed-drive storage, time to first app, file shares in the web UI, and being something a household can leave alone. Its failure mode is graceful: lose more disks than parity and you lose those disks, not the pool.

Proxmox wins on virtualization depth, backups, clustering and price, and on not painting you into a corner: underneath it is plain Debian, ZFS and QEMU. Its cost is that “build your own storage” and “Docker goes in a VM” are two jobs Unraid does for you.

What we’d actually run

For one mini-PC with a drawer of odd-sized drives, a media library, a dozen apps and maybe one VM, buy Unraid Unleashed and stop thinking about it. The $109 buys a storage layout no free project matches for that drive mix, and the catalogue turns most self-hosting into clicking Install. Extend in a year or do not; the box keeps working either way.

If VMs are the point, the drives are matched, or a second node is a “when” rather than an “if”, run Proxmox on the no-subscription repository with ZFS mirrors underneath and Docker in one Debian VM. Hardware sizing for an Unraid build is in the Unraid hardware guide; for a Proxmox box see Proxmox VE hardware requirements.

Want both a real hypervisor and the parity array? The Proxmox-host, Unraid-guest split works, provided there is a spare controller to hand to Unraid and you accept that Lime Technology will not support it.

Either way, parity and RAIDZ are not backups. Point a scheduled job at a second box or a bucket before month nine.

Related across the network

• How to Install Proxmox VE: Step-by-Step Install Guide — proxmoxguide.com
• Proxmox ZFS Storage Setup: Zvols, volblocksize, and ARC — proxmoxguide.com
• Proxmox VE Hardware Requirements for a Home Lab Build — proxmoxlab.org
• Best Docker Containers for Your Home Server in 2026 — dockerhomelab.com
• LM Studio on Unraid: Headless Server Setup — lmstudioguide.com

FAQ

is unraid or proxmox better for a beginner?

Unraid. Its web UI handles shares, the parity array and Docker apps from a catalogue of over 2,000 containers and plugins, and the 30-day trial, extendable twice by 15 days, costs nothing. Proxmox expects you to design the ZFS layout, run Docker inside a VM and serve files from a guest, which is more to learn.

can proxmox back up to an unraid share without pbs?

Yes. Export an NFS share from Unraid and add it to Proxmox VE as backup storage; Proxmox’s backup guide calls an NFS server a good alternative to Proxmox Backup Server. The catch is that Proxmox VE backups are always full backups, and on NFS each is stored whole, without the deduplication, live-restore and single-file restore a PBS target adds.

do you have to pay for unraid every year?

No. Every Unraid licence is perpetual: Starter ($49) and Unleashed ($109) include a year of updates, then an optional $36 a year, and a lapsed licence keeps its current version. Lifetime ($249) never needs the extension. Moving up later costs $69 from Starter to Unleashed, or $209 from Starter to Lifetime. Prices checked October 2026.

unraid vs ubuntu server: which is better for a home server?

Unraid, unless you want to build everything yourself. Ubuntu Server is free, and 26.04 LTS, released April 2026, gets five years of standard security maintenance, but it is a general-purpose OS: storage layout, shares and Docker are yours to assemble from the command line. Unraid packages the parity array, shares and app templates in a web UI.