TrueNAS is a Debian-based storage operating system built around OpenZFS, with SMB, NFS and iSCSI sharing, replication, snapshots and a Docker-based application catalog. The free build is called Community Edition; the paid, hardware-backed build is TrueNAS Enterprise.
Our verdict on TrueNAS Community Edition#
Get the naming right before you read any older guide. TrueNAS 25.04 "Fangtooth" folded the FreeBSD-based CORE and the Linux-based SCALE into a single product, and the free build is now called TrueNAS Community Edition; the current release is 25.10 "Goldeye", on 25.10.7 as of September 2026, with TrueNAS 26 in beta and an annual cadence after that. Documentation URLs still say /docs/scale/, which is why the old names persist. If you are on FreeBSD CORE 13.0 or 13.3, the honest answer is that you cannot upgrade through the UI to anything past 24.04: do a clean install from ISO and restore your config file, and know it is a one-way trip because rolling back to a FreeBSD boot environment can break the system. 25.10 also drops the built-in certificate authority, removes SMART test scheduling from the UI, and requires Turing or newer NVIDIA GPUs.
Who TrueNAS Community Edition is for#
Choose it if
- Someone who wants ZFS done properly: scrubs, snapshots, checksums and replication to a second box, configured in a UI
- A household or small office serving SMB shares to Windows and macOS clients that need to be reliable and boring
- A person migrating off a Synology who wants to keep the drives under a filesystem that tells them when data rots
Look elsewhere if
- Your hardware is ARM or has under 8 GB of RAM, both of which are below the documented floor
- You want the box to be a general-purpose Linux server, since TrueNAS treats the OS as an appliance you should not modify
- You need the old FreeBSD CORE jails and plugins, which are gone and not coming back
What running it actually looks like#
Install from ISO to a dedicated boot device of 16 GB or more, ideally an SSD, and do not put it on one of your data disks. Minimum documented hardware is a 2-core 64-bit CPU and 8 GB of RAM, with about 1 GB more per drive past eight. First boot gives you a console menu and a web UI on 80 and 443. Create a pool from at least two identically sized devices, then a dataset per share. Applications need you to nominate an apps pool, which creates an ix-apps dataset and starts the Docker service; picking a pool you later want to destroy is a decision you will regret. ECC RAM is recommended but not required, and the docs say so plainly. Upgrades within a release line use boot environments, so a failed update reverts by picking the previous entry at boot.
Resource profile#
- Memory
- 8192 MB idle, around 16384 MB in ordinary use. The documented minimum is 8 GB with a 2-core 64-bit CPU and a 16 GB SSD boot device, plus roughly 1 GB more per drive beyond eight; the typical figure assumes apps and a working ARC.
- CPU and acceleration
- ZFS checksums, compression and any encryption run on the CPU, and SMB is single-threaded per connection, so single-core speed matters more than core count until you add apps or VMs.
- Storage growth
- The boot pool wants a dedicated 16 GB or larger SSD and holds nothing but the OS and config. Apps and their data live in an `ix-apps` dataset on a pool you nominate, which you cannot easily move later without redeploying.
- Operational load
- 3 of 5, Moderate. Upgrades within a line are clean and boot environments let you roll back, but major version jumps carry real deprecations, and the app platform has been rebuilt twice in three years. Restores need the config file and a pool import in the right order.
Figures describe a small single-household install and are the working assumptions behind our stack planner. Your numbers will differ with library size, user count and hardware. See methodology.
Data and backup surface#
Three separate things. First, the system configuration: download it from System then General then Save Config, and include the secret seed if you use encrypted datasets, or your keys are worthless. Second, ZFS datasets, which you protect with snapshots and replication to another TrueNAS or a remote ZFS target, not with file copies. Third, app data under the ix-apps dataset on your apps pool; snapshot that dataset before every app upgrade. The boot pool itself is disposable: a reinstall plus config restore rebuilds it. Do not treat snapshots on the same pool as a backup, and do not skip the encryption key export.
Derived backup shape
SQLite backup. sqlite3 <db> ".backup out.db" while running, or stop the container and copy. A live cp of a WAL-mode SQLite file can restore corrupt.
Traps and surprises#
CORE users cannot upgrade through the UI
Migrating from FreeBSD-based TrueNAS 13.0 or 13.3 to the Linux line only works through the UI up to 24.04. For 24.10 and later, including 25.10, the documented path is a clean ISO install followed by a configuration restore. Update to the latest maintenance release of 13.3 first, export your config, then reinstall. Activating or rolling back to a FreeBSD boot environment afterwards can break the system.
25.10 removed features you may be relying on
Goldeye drops the built-in certificate authority that let TrueNAS create and sign its own certificates, so you now need an external CA. It also removes the SMART test scheduling and monitoring interface in favour of middleware polling, retires the SMB recycle bin for new shares, and stops auto-starting VMs created before 25.04.2. Read the version notes before upgrading rather than discovering a missing scheduled SMART test months later.
NVIDIA GPUs older than Turing stopped working
25.10 switched to the open NVIDIA kernel drivers, which support Turing and newer only. Pascal, Maxwell and Volta cards are no longer supported, so a GTX 1050 or P400 used for Plex or Jellyfin transcoding will stop being available to apps after the upgrade. Check the card generation before you take the update; there is no supported way back to the proprietary driver on that release.
The apps pool choice is sticky
When you first enable apps, TrueNAS asks which pool to use and creates an ix-apps dataset there. Moving it later means redeploying applications, and destroying that pool takes every app configuration with it. 25.10 added automatic pool migration, which helps, but the safe move is to nominate a pool you intend to keep from the start, and to snapshot the ix-apps dataset before each app catalog update.
The apps platform has been rebuilt twice
TrueNAS SCALE originally ran applications on an embedded Kubernetes (k3s), then replaced it with Docker in the 24.10 Electric Eel release. Guides and YouTube walkthroughs written for the Kubernetes era describe a UI and a storage layout that no longer exist, including the old ix-applications dataset. If a tutorial mentions Helm charts, catalogs of trains for Kubernetes, or k3s, it predates the current platform.
Specifications#
- Category
- Platforms and container management
- Licence
- LGPL-3.0 (middleware) (Copyleft)
- Written in
- Python / TypeScript
- First release
- 2022
- Maturity
- Mature
- Datastore
- SQLite configuration database on the boot pool, plus ZFS datasets for everything else
- Default ports
80,443- Ships as
- ISO install to a dedicated boot device, preinstalled on iXsystems hardware
- arm64 builds
- No
- Identity
- Native OIDC. Active Directory and LDAP directory services, plus OIDC-based identity provider support in the recent releases for web UI login.
- Replaces
- Synology DSM, QNAP QTS, NetApp ONTAP, Windows Server file shares
- Project site
- www.truenas.com
- Source
- github.com/truenas/middleware
- Documentation
- www.truenas.com/docs
Alternatives to TrueNAS Community Edition#
Everything else in platforms and container management, closest in operational weight first.
| Tool | Ops load | Idle RAM | Licence |
|---|---|---|---|
| Coolify | 3, Moderate | 1200 MB | Apache-2.0 |
| Dokploy | 3, Moderate | 900 MB | Apache-2.0, with DSAL 1.0 reserved for a /proprietary path |
| Komodo | 3, Moderate | 250 MB | GPL-3.0 |
| CasaOS | 2, Light | 300 MB | Apache-2.0 |
| Docker Engine | 2, Light | 120 MB | Apache-2.0 (Engine and Compose); Docker Desktop is proprietary |
| Podman | 2, Light | 40 MB | Apache-2.0 |
Where TrueNAS Community Edition comes up elsewhere#
Head to head
Sources#
Facts on this page were checked against the project's own material. Where a number is our own estimate rather than a published figure, the text says so.
Published . Last reviewed . Found something out of date? Tell us and we will fix it and log the change.