Proxmox vs TrueNAS for a Home Server: Hypervisor First or Storage First
Duncan Hale
November 19, 2026
You have a box with a handful of drives, a list of services you want to run, and two installers on a USB stick: Proxmox VE and TrueNAS. Both are free, both use ZFS, and both can run virtual machines and containers, so the comparison looks close on paper. In practice they start from opposite ends. Proxmox is a hypervisor that can manage storage. TrueNAS is a storage system that can run workloads. The right pick depends on which layer of your home server you want to be the one that never surprises you.
Two starting points: a hypervisor that stores, a NAS that computes
Proxmox Virtual Environment is a Debian-based virtualization platform. It runs KVM virtual machines and LXC containers, clusters several hosts together, and supports a long list of storage back ends, ZFS among them. Its web interface is organized around guests: create a VM, attach disks, take snapshots, back it up, migrate it to another node.
TrueNAS Community Edition is built around ZFS pools and the data in them. Its interface is organized around pools, datasets, shares, snapshot schedules and replication. Docker-based apps, virtual machines and, more recently, LXC containers sit on top, but the project’s own messaging is clear that Community Edition remains a storage product first.
That difference explains most trade-offs below. If you have compared Proxmox with Unraid, the pattern will look familiar; Proxmox vs Unraid for a first home server covers that pairing.
Where both projects stand in November 2026
Proxmox VE is on the 9.x series, which moved the platform to Debian 13 “Trixie” in August 2025. Version 9.1 added the ability to create LXC containers from OCI images, the same image format Docker and Podman use. Version 9.2, announced in May 2026, moved to Linux kernel 7.0 by default and ships ZFS 2.4.
TrueNAS has been renamed and renumbered more than once. With 25.04 “Fangtooth” in April 2025, what had been TrueNAS SCALE became TrueNAS Community Edition, and the FreeBSD-based CORE line was folded into the same Linux-based product. 25.10 “Goldeye” (October 2025) is the current stable line. The next major version was tested as TrueNAS 26 but, according to iXsystems, was renamed TrueNAS 27 starting with RC.1 on October 6, 2026, to match a yearly release cadence. iXsystems plans 27.0 for early December 2026 and advises production systems to wait for it.
Layer by layer: what each platform does natively
The table compares what each web interface manages out of the box; either platform can do more with extra software.
| Layer | Proxmox VE 9.x | TrueNAS Community Edition 25.10 / 27 |
|---|---|---|
| Storage | ZFS pools created from the GUI, used mainly as VM and container storage | Full ZFS management: datasets, quotas, snapshots, scrubs, SMART tests, permissions |
| File sharing | None built into the GUI; usually a container or VM running Samba or NFS | SMB, NFS and iSCSI configured from the GUI, plus NVMe over TCP since 25.10 |
| Virtual machines | KVM with mature tooling: templates, live migration in clusters, PCI passthrough | KVM VMs on the Virtualization screen; usable but less central |
| Containers | LXC, including containers created from OCI images since 9.1 | Docker-based apps since 24.10; LXC experimental in 25.10, fully supported in 27 |
| Backup | vzdump to any storage; Proxmox Backup Server for deduplicated, incremental backups | Periodic snapshots, ZFS replication to another system, cloud sync tasks |
| Updates and licensing | Free; enterprise repository needs a subscription, no-subscription repository available | Free Community Edition; Enterprise is a separate commercial product |
The storage layer: ZFS as the product versus ZFS as a back end
Both platforms run OpenZFS, so a pool built on one is the same file system on the other. The difference is how much of ZFS each interface exposes.
In TrueNAS, the pool is the main object. You create datasets with their own compression, record size and quotas, set ACLs for SMB users, schedule snapshots with retention, scrubs and SMART tests, and get alerts when a disk degrades. Replacing a failed disk is a guided workflow. Routine storage hygiene is visible and hard to forget, which is the main reason people who care about their files choose TrueNAS.
In Proxmox, ZFS is mainly where guest disks live. You can create a pool under the node’s Disks menu, add it as storage, and Proxmox takes ZFS snapshots of VMs and containers. Dataset-level snapshot schedules for plain file data, SMB permissions and share management are not part of the GUI; you handle them from the shell or hand the job to a container or VM. The Proxmox ZFS documentation also notes that new installs since 8.1 limit the ARC by default to 10% of host memory, capped at 16 GiB, so ZFS does not compete with your VMs for RAM. TrueNAS, being storage-first, lets the ARC take much more.

The compute layer: mature KVM versus TrueNAS’s shifting virtualization
Virtual machines are where Proxmox is clearly ahead. Templates, cloning, snapshots with memory state, well-documented PCI and GPU passthrough, cloud-init and clustered live migration have been stable for years. For Windows, an OPNsense firewall, Home Assistant OS or several Linux VMs, Proxmox is the more comfortable home.
TrueNAS virtualization has been through a lot of change. 25.04 replaced the earlier libvirt-based VM system with Incus. After user feedback, 25.04.2 brought back the classic VM implementation, and 25.10 presents KVM virtual machines on a Virtualization screen with experimental LXC containers on a separate one. The TrueNAS 27 documentation says LXC containers are now fully supported, and that VMs created on the 25.04.0 and 25.04.1 Instances screen are not migrated automatically: the disks stay on the pool, but the VM configuration, UEFI variables and TPM state have to be re-created. 25.10 added VM Secure Boot and virtual disk import and export, so the direction is positive, but the history argues for keeping important VMs on Proxmox.
The app layer: Docker apps on TrueNAS, LXC on Proxmox
TrueNAS switched its apps from Kubernetes to Docker in 24.10 “Electric Eel”. The catalog installs common self-hosted apps with forms for storage paths and ports, and you can also deploy your own Docker Compose YAML as a custom app. Apps sit directly next to their data on the same pool, which is convenient for media servers, photo libraries and download tools.
Proxmox has no Docker app store. The usual pattern is a Debian VM or LXC container running Docker and Compose, managed with your own tools. That is more setup, but your Compose files are portable and the Docker host can be backed up and restored as one unit. Since 9.1, you can also create an LXC container straight from an OCI image, which covers simple single-container services without a separate Docker host. Whether the extra layer is worth it is covered in do you need Proxmox if everything already runs in Docker.
TrueNAS as a VM on Proxmox: the HBA passthrough combo and its traps
A popular way to avoid choosing is Proxmox on the hardware with TrueNAS as a VM that owns the data disks. It works well when done the way iXsystems recommends, and badly when it is not.
The TrueNAS hardware guide states that running TrueNAS virtualized on virtual disks is fine for proof-of-concept testing but is not a supported configuration for production or critical data. The recommended approach, repeated in the TrueNAS blog’s guidance on virtualization, is to pass the entire storage controller to the VM with PCI passthrough, ideally an LSI/Broadcom HBA flashed to IT mode, so the TrueNAS VM sees real disks and the hypervisor never touches them. That requires IOMMU support (VT-d or AMD-Vi) enabled in firmware and a controller in its own IOMMU group. On Proxmox, you can check that IOMMU is active and attach the controller like this:
dmesg | grep -e DMAR -e IOMMU
lspci -nn | grep -i -e LSI -e SAS
qm set 100 -hostpci0 0000:01:00.0
The risks come from shortcuts:
- Virtual disks or a ZFS pool on top of a Proxmox zvol. ZFS inside the VM loses direct knowledge of the physical disks, and you end up with ZFS on ZFS with no clean recovery path if the outer layer fails.
- Passing individual disks by ID instead of an HBA. This is common on machines without a spare PCIe slot. The disks still go through the hypervisor’s virtual controller, so TrueNAS may not see SMART data or real serial numbers, and the host can still see the disks. If the Proxmox host ever imports the same pool while the VM is running, two systems write to one pool, which is the scenario ZFS cannot protect you from.
- Hardware RAID cards. Both the TrueNAS hardware guide and the Proxmox ZFS documentation warn against putting ZFS behind a RAID controller; use HBA or IT mode.
- Boot order dependencies. Guests that use NFS or SMB shares from the TrueNAS VM must start after it and stop before it, or they hang. Set Proxmox’s start order and delay accordingly.
Backups: Proxmox Backup Server and ZFS replication
Proxmox backs up guests. The built-in vzdump tool writes full backups of VMs and containers to any storage, and Proxmox Backup Server, a separate free product whose 4.x series arrived alongside VE 9 in August 2025, adds incremental, deduplicated backups with optional client-side encryption and verification jobs.
TrueNAS backs up datasets. Periodic snapshot tasks keep local history, and replication tasks send those snapshots incrementally to another ZFS system, either a second TrueNAS box or any host you can reach over SSH. Cloud sync tasks push files to S3-compatible storage. Because only changed blocks move, replication suits large file data. Proxmox can replicate ZFS-backed guests between cluster nodes, but that is aimed at failover rather than long-term backup history.
A combined setup often uses both: Proxmox Backup Server for VMs and containers, and ZFS replication for the bulk data on the TrueNAS side. For how PBS compares with file-level tools, see Proxmox Backup Server vs restic for VMs.

Licensing: Proxmox’s subscription repository and the nag dialog
Both platforms are free to use with all features. The difference is in updates. A fresh Proxmox VE install is configured for the enterprise repository, which according to the Proxmox wiki requires a valid subscription key. Without one, package updates fail until you switch to the no-subscription repository, which the wiki describes as suitable for testing and non-production use because its packages are not always as heavily tested. The web interface also shows a “No valid subscription” dialog at login. On Proxmox VE 9, the no-subscription repository uses the deb822 format:
# /etc/apt/sources.list.d/proxmox.sources
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
Disable the enterprise entry in pve-enterprise.sources at the same time. Many home users run this way permanently; a subscription buys the more tested repository and funds development. TrueNAS Community Edition has no comparable repository split or login prompt. iXsystems sells TrueNAS Enterprise on its own hardware, and some newer features, such as Object Lock in the S3-compatible object service previewed in 27 RC.1, require a paid license.
Hardware: boot drives, RAM, HBAs and the ECC argument
TrueNAS installs to a dedicated boot device, and that device cannot hold your data pool, so plan for a small SSD just for the OS. Proxmox can install to a ZFS mirror and use leftover space on those drives for guests. For memory, the TrueNAS hardware guide suggests at least 8 GB for basic operation with up to eight drives, and the Proxmox ZFS wiki says ZFS needs at least 8 GB to start, with more RAM welcome on both. VM-heavy hosts need RAM for the guests on top of that; how much RAM a home server needs for Proxmox, Docker and ZFS breaks that down.
ECC memory is the long-running debate. The TrueNAS hardware guide says most users strongly recommend ECC as another data integrity defense, while noting that many TrueNAS systems run every day without it. The Proxmox ZFS documentation recommends high-quality ECC RAM to help prevent data corruption. Neither treats it as a hard requirement. ZFS co-creator Matt Ahrens has argued that nothing about ZFS requires ECC more than any other file system; ECC protects data in memory whatever file system sits underneath. If your platform supports it cheaply, use it; if it means a different motherboard and CPU class, it is a judgment call, not a blocker.
Matching the platform to what the box will actually do
- Mostly a file server with a few apps. Photos, laptop backups, a media library and a handful of containers: TrueNAS on bare metal.
- Mostly VMs and services, little bulk data. Home Assistant OS, a firewall VM, a Windows VM, several LXC containers and a Docker host: Proxmox on bare metal, with ZFS for guest storage and a small Samba container for the few shares you need.
- Serious amounts of both. Many terabytes of data and several important VMs: either Proxmox with a TrueNAS VM on a passed-through HBA, or two separate machines. Two machines cost more but remove the passthrough complexity.
- No spare PCIe slot and no HBA. Do not virtualize TrueNAS on passed-through individual disks for data you care about. Pick one platform for bare metal instead.
- You plan to add a second or third host. Proxmox clustering, live migration and Proxmox Backup Server make it the better base for growth on the compute side.
Whichever you start with, the data on a ZFS pool is portable: a pool created on Proxmox can be imported on TrueNAS and vice versa, as long as the pool’s feature flags are supported by the OpenZFS version you move to. That makes the decision less permanent than it feels on install day.