OpenMediaVault
OpenMediaVault (OMV) is a free, open-source network-attached storage operating system built on Debian Linux. Where TrueNAS centers everything on ZFS and Unraid sells a parity-protected array, OMV takes the plainest path of the three: a standard Debian base, mdadm software RAID, and a plugin system, all run from a web browser. It’s also the only one of the three that runs on a Raspberry Pi.
License: OpenMediaVault is licensed under the GNU General Public License, version 3 (GPL-3.0), confirmed via the LICENSE-GPL3 file in the official GitHub repository. There’s no paid tier, no enterprise edition, and no dual licensing: the whole project is community-developed and funded through donations to lead developer Volker Theile.
Quick facts: Official site openmediavault.org · Documentation docs.openmediavault.org · Source github.com/openmediavault/openmediavault (GPL-3.0) · Current stable: OpenMediaVault 8.x “Synchrony”, built on Debian 13, now at 8.5.1 · OpenMediaVault 7.x (“Sandworm”, Debian 12) reached end-of-life alongside Debian 12 in mid-2026.
What OpenMediaVault actually is
Lead developer Volker Theile started OpenMediaVault in 2009, after working on FreeNAS, the FreeBSD project that later became TrueNAS. He wanted a Linux rewrite instead of another BSD fork, so he built OMV on Debian and shipped the first release in October 2011. The idea hasn’t really changed since: a familiar Linux base with a PHP and Angular web interface on top, plus a modular plugin framework so services like file sharing, backups, or a media indexer install from the GUI instead of a config file. There’s a bit of NAS history buried in that origin story, since TrueNAS and OpenMediaVault effectively grew out of the same FreeNAS codebase Theile was maintaining back in 2009.
Storage, RAID, and the plugin system
Storage in OMV is Linux-native rather than ZFS-first. Software RAID runs through mdadm, with levels 0, 1, 4, 5, 6, and 10 plus JBOD, and an LVM plugin handles more flexible volume management on top. Default filesystems are ext4, Btrfs, XFS, JFS, NTFS, and FAT32; ZFS is available only as a third-party plugin, not the built-in default it is on TrueNAS. That’s the real trade-off against TrueNAS: OMV assumes comfort with mdadm and standard Linux filesystems, not ZFS pool planning, and its plugin catalog, split between officially maintained plugins and the community-run omv-extras.org repository, covers everything from antivirus to VPN servers to media tools.
Hardware: OMV’s documented minimum is 1 GiB of RAM and a 4 GiB drive for the OS itself (an SSD or a USB stick with static wear leveling beats a plain flash drive). That floor is real: OMV runs on far less than TrueNAS or Unraid ask for, though Docker containers and extra plugins want more headroom once they’re actually running.
Installing OpenMediaVault
Installing OpenMediaVault means picking one of two paths: a dedicated ISO install, or adding OMV on top of a Debian box that’s already running.
- Download the installer ISO from the official downloads page, or run the official one-line script on an existing Debian install (see below).
- Complete the base setup: hostname, root password, and network configuration.
- Open the assigned IP address in a browser, log in, and enable the omv-extras repository under System for the wider plugin catalog.
- Build a RAID array or single-disk volume from the remaining drives, add SMB or NFS shares, and install plugins as needed.
wget -O - https://get.openmediavault.io | sh -OMV expects to own the whole OS. Its own documentation says plainly that it can’t run inside a container and shouldn’t share a machine with a desktop GUI. Give it dedicated hardware or its own VM, not a spot on a general-purpose Debian box doing other jobs too.
Docker, plugins, and Raspberry Pi
Docker itself isn’t part of a stock install. Getting a GUI for it means enabling the omv-extras.org repository and installing the openmediavault-compose plugin, which adds a docker-compose-style interface inside OMV instead of requiring Portainer or a terminal. On amd64 PCs, that repository has to be added by hand; on Raspberry Pi and other ARM boards, OMV’s own SBC images ship with omv-extras already installed. That’s the detail that actually matters for a lot of homelabs: OMV runs on a Raspberry Pi in a way neither TrueNAS nor Unraid does, since neither one publishes an ARM build. For a Pi 4 or Pi 5 with a couple of USB drives attached, OMV is genuinely one of the few options with a real web GUI behind it.
Homelab use cases
OMV’s natural home is a small, low-power NAS: a Raspberry Pi or an old mini PC with two or three drives in mdadm RAID1, sharing files over SMB to the rest of the house. It also works well as a lightweight VM inside Proxmox VE, handling storage and a couple of containers for anyone who doesn’t want ZFS’s RAM appetite or Unraid’s license fee for what’s ultimately a modest amount of data.
OpenMediaVault vs. TrueNAS vs. Unraid vs. Synology/QNAP
Homelabbers comparing OpenMediaVault usually have TrueNAS, Unraid, and Synology/QNAP on the same shortlist.
| Category | OpenMediaVault | TrueNAS | Unraid | Synology/QNAP |
|---|---|---|---|---|
| Cost | Free, GPL-3.0 | Free, LGPL-3.0 core | Paid, $49–$249 one-time | Proprietary appliance, often bundled subscriptions |
| Storage | mdadm software RAID, LVM, ZFS via plugin | ZFS-first: RAID-Z, mirrors, checksums | Parity array, mismatched drives | Proprietary RAID (SHR/QTS) |
| Apps | Docker via the omv-extras compose plugin | Docker Compose apps plus KVM VMs | Docker via Community Applications, plus KVM VMs | Vendor app store, some Docker support |
| Hardware | x86 and ARM, including Raspberry Pi | x86-64 only, 8 GB+ RAM baseline | x86-64 only | Vendor-locked appliance hardware |
| Best fit | Small, low-power NAS and Raspberry Pi builds | Data integrity, open hardware choice | Mismatched drives, Docker-first beginners | Turnkey hardware, least setup |
OpenMediaVault: pros and cons
- Free and fully open-source under GPL-3.0, with no paid tier anywhere in the project
- Runs on modest hardware, including Raspberry Pi and other ARM boards that TrueNAS and Unraid don’t support
- Built on Debian, so package management and hardware support are familiar to anyone who’s used Linux before
- Modular plugins cover file sharing, backups, and VPNs without leaving the web interface
- Docker needs the third-party omv-extras repository and compose plugin; it isn’t built in
- ZFS is a bolt-on plugin here, not the native, self-healing storage layer TrueNAS is built around
- Plugin quality varies, since a lot of them come from community maintainers rather than the core team
- Less out-of-the-box polish than a commercial NAS appliance, since nobody’s paid to make the defaults pretty
FAQ
Is OpenMediaVault free?
Yes. It’s fully open-source under GPL-3.0, with no paid tier and no feature gate anywhere. The project runs on community contributions and donations to lead developer Volker Theile.
Does OpenMediaVault run on a Raspberry Pi?
Yes, and it’s one of the main reasons to pick it over TrueNAS or Unraid. OMV supports ARM alongside x86-64, with dedicated Raspberry Pi images that even ship the omv-extras plugin repository pre-installed. Neither TrueNAS nor Unraid publishes an ARM build.
Can OpenMediaVault run Docker containers?
Yes, but not by default. Enabling the omv-extras.org repository and installing the openmediavault-compose plugin adds a Docker Compose GUI inside OMV. That repository already exists on Raspberry Pi images; on amd64 PCs it has to be added first.
OpenMediaVault earns a Medium difficulty label less from its web interface, which is genuinely easy to use, than from what sits behind it: mdadm RAID, a Debian base that occasionally wants a terminal, and Docker support that depends on a third-party repository instead of shipping by default. It’s the right call for a Raspberry Pi or a low-power box doing one job well; TrueNAS or Unraid usually take over once the job is a heavier Docker host or a large media library. It pairs naturally with the same hardware covered in our homelab setup guide for beginners.