Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.

Poolsman is a commercial ZFS-management module for Cockpit that adds a browser interface to an existing Linux server. It can manage pools, datasets, ZVols, snapshots, clones, and disk-maintenance tasks while showing the commands it is about to run. It is not a storage operating system or a complete NAS suite: you still provide and maintain Linux, OpenZFS, file sharing, security, and backups.

As of August 2026, the vendor offers Preview 10 through its Early Access Program (EAP), not a final 1.0 release. It is worth considering if you want to keep your Linux or Proxmox host and prefer a graphical ZFS workflow. Preview-stage maturity, a paid per-host license, and the need to understand ZFS make it a poor fit for anyone who needs a proven appliance platform or expects a GUI to make storage operations risk-free.

What Poolsman does—and what it does not

Cockpit provides the web-based server-management framework; Poolsman adds a ZFS-specific module, shown as the ZFS storage tab. The module works with the OpenZFS installation and tools on the host. It does not replace OpenZFS or insert a separate storage layer between ZFS and your disks.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Linux host
├── OpenZFS
├── Cockpit
│   └── Poolsman (ZFS storage module)
└── Browser

Cockpit itself is free and LGPL-licensed, but that does not make Poolsman open source or free. The vendor sells Poolsman under an EAP license. Cockpit’s default web interface is available on port 9090; access it over HTTPS at https://<server-address>:9090. See the Cockpit project and the Poolsman overview.

Poolsman is not, by itself, a TrueNAS-style storage distribution, a file-sharing suite, or a backup system. Its core job is ZFS administration on a Linux system you already operate. The vendor lists Samba, NFS, iSCSI, and cloud-sync capabilities as possible additional or future modules; do not assume those are included in the core ZFS feature set.

What you can manage

The vendor’s current feature list and release notes describe a broader tool than a simple pool-status dashboard. Poolsman advertises:

  • Pools and vdevs: create, destroy, import, and export pools; view topology; scrub pools; trim, attach, detach, online, offline, and replace disks. Release notes also describe dRAID-related functionality.
  • Datasets and volumes: create and manage filesystems and ZVols, mount filesystems, and set properties such as compression, encryption, deduplication, quotas, and reservations. ZVol provisioning includes thin and thick modes.
  • Snapshots and clones: create and manage snapshots and clones. These can help with point-in-time recovery and workflows, but snapshots remain part of the pool and are not independent backups.
  • Monitoring: inspect pool and disk status, temperature, drive health, S.M.A.R.T. information, and ZFS memory use. S.M.A.R.T. reporting requires smartmontools 7 or newer and is optional. Health indicators can be useful, but they cannot predict or prevent every drive failure.
  • Command Preview: inspect and copy the command generated by a UI action before running it. This makes the workflow more transparent and gives experienced administrators a way to compare the UI action with the underlying CLI.

Command Preview is visibility, not a dry run, transaction, or safety guarantee. A command can be clearly displayed and still destroy the wrong pool or disk if you approve it without checking the target and consequences.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

For feature details and the vendor’s own current list, see the Poolsman EAP page and its release history.

Preview 10: active development, not a 1.0 guarantee

The vendor identifies Preview 10 as the current build in its August 2026 materials. The April 2026 release announcement describes a redesigned interface aligned with newer Cockpit releases, compatibility handling for older Cockpit versions, and support for newer ZFS versions. Earlier releases added capabilities including disk replacement and scrubbing, additional dataset properties, encryption controls, pool import, ZFS send/receive over SSH, quotas, reservations, and more explicit confirmation for destructive actions. See the Preview 10 announcement and release notes.

That history shows meaningful expansion, but it does not establish production reliability or make Preview 10 a stable 1.0 release. The vendor still labels the program Early Access and has described general availability as expected later in 2026; that is a vendor expectation, not a guaranteed date. There is no basis here to claim independent performance testing, third-party security auditing, or broad production reliability studies.

Compatibility and prerequisites

The vendor’s EAP page lists x86_64 and aarch64 systems, Cockpit 200 or newer, and OpenZFS 2 or newer. Its named operating systems are Debian 12 and 13; Ubuntu 22.04 and 24.04; RHEL, Oracle Linux, and Rocky Linux 8, 9, and 10; openSUSE Tumbleweed; Arch Linux; Proxmox VE 8 and 9; and Proxmox Backup Server 4. Other distributions may work when prerequisites are present, but that is not the same as vendor-tested support. “OpenZFS 2+” is a broad prerequisite, not a promise that every distribution, kernel, and OpenZFS combination behaves identically.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Before installing, check the current requirements and installation manual against the exact host and ZFS build you run. The installation page uses package filenames containing 0.10.0-1; do not assume, without an explicit vendor mapping, that this package number is definitively identical to the Preview 10 label.

Installation overview

Prepare the Linux host first: install and verify OpenZFS, ensure Cockpit is available, and confirm that the account you will use has appropriate administrative privileges. Follow the current vendor instructions for your distribution, because repository keys, package versions, Cockpit dependencies, and service setup can change.

Debian, Ubuntu, and Proxmox

The vendor’s repository-based instructions add its APT source and signing key, refresh package metadata, and install Poolsman:

echo "deb [arch=all] https://download.poolsman.com/repository/debian/ stable main" | 
  sudo tee /etc/apt/sources.list.d/poolsman.list > /dev/null

wget -qO- https://download.poolsman.com/keys/poolsman.gpg | 
  sudo tee /etc/apt/trusted.gpg.d/poolsman.gpg > /dev/null

sudo apt-get -y update
sudo apt-get -y install poolsman

Then open https://<server-address>:9090 and select ZFS storage. Review the current installation manual before running repository and key commands on a production host.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Proxmox and lightweight Debian caution: installing the full Cockpit package can pull in dependencies such as NetworkManager, which may alter how a carefully configured host behaves. The vendor provides a path that installs only the basic Cockpit components it needs. Review the dependency changes and use that minimal path when appropriate rather than blindly installing the full package.

RHEL-family systems and openSUSE

The vendor’s current RHEL-family example imports its signing key and installs the RPM directly:

sudo rpm --import https://download.poolsman.com/keys/poolsman.asc

sudo dnf install 
  https://download.poolsman.com/repository/rhel/any/stable/poolsman-0.10.0-1.el.noarch.rpm

For openSUSE, its example is:

sudo rpm --import https://download.poolsman.com/keys/poolsman.asc

sudo zypper install 
  https://download.poolsman.com/repository/suse/any/stable/poolsman-0.10.0-1.suse.noarch.rpm

In either case, Cockpit’s socket must be enabled, and the host firewall may need to permit access to Cockpit. Use the current manual to confirm service and firewall steps for your system.

Arch and other distributions

For Arch, the vendor instructs users to configure its repository and key, then install with sudo pacman -Syu poolsman. Because repository and key setup are easy to get wrong and can change, copy those exact steps from the current installation page rather than relying on a stale article.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

For systems without a repository package, the manual documents a ZIP path using a versioned download and extraction into /usr/share/cockpit/. A manual install makes you more responsible for verifying the download and managing updates; prefer the vendor’s current package route when your distribution is supported.

Access and license activation

Once Cockpit is running, browse to https://<server-address>:9090, sign in with an appropriate system account, and open the ZFS storage tab. The vendor says a free 30-day trial can be obtained in the Poolsman UI. For a purchased license, download the license key from your Poolsman account and activate it from that tab. Trial availability and terms can change, so check the current manual and account flow.

Cockpit may reject direct root login by default. The vendor documents changing /etc/cockpit/disallowed-users as a workaround, but enabling root access should not be the routine fix on a production server. Prefer a properly privileged administrative account; if you deliberately enable root login, understand and document the additional security exposure.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Safety checklist before changing a pool

A web interface does not change the consequences of ZFS operations. Before creating, importing, exporting, replacing, rolling back, or destroying anything:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  1. Confirm the host and target. Check the machine, pool name, dataset, and intended operation. Read Command Preview, but do not treat it as approval-by-default.
  2. Identify disks by stable IDs. Linux names such as /dev/sda can change across boots or when hardware is rearranged. Verify serials or other stable device identifiers before selecting a disk.
  3. Understand the topology. Know the vdev layout, redundancy, and failure consequences before creating or changing a pool. A GUI cannot repair a poor topology choice.
  4. Keep an independent backup. Snapshots reside in the same pool and can be lost with it. Replication using ZFS send/receive can be part of a backup plan, but it does not by itself provide independent retention, off-site protection, monitoring, or tested recovery.
  5. Protect encryption keys. Confirm you can recover the keys and know how encrypted datasets will be unlocked and mounted after a migration or reboot.
  6. Plan replacement and maintenance. Check that a replacement disk meets the pool’s size requirements and understand that resilvering and scrubbing take time and put the pool under activity.
  7. For imports, avoid split-brain handling. Confirm the source pool is healthy, the destination sees the intended devices, feature compatibility is understood, and the old host is offline before importing the pool elsewhere.
  8. Do not experiment on the only copy. Test unfamiliar workflows on disposable storage or a non-production host.

Poolsman added stronger destructive-action confirmations in Preview 9, but confirmation prompts are friction, not a data-protection mechanism. Consult the OpenZFS documentation for the concepts and operations behind the interface.

How Poolsman compares with the main alternatives

Option Operating model Best fit Main caveat
Poolsman ZFS module layered onto Linux and Cockpit Administrators who want to keep an existing Linux host and add a ZFS-focused GUI Commercial Preview/EAP software; not a complete NAS platform
TrueNAS Community Edition Dedicated storage-platform approach Users who want an integrated NAS operating model rather than a module on a general-purpose Linux server Different host and administration model; not simply another Cockpit plugin
OpenZFS command line Native tools and documentation on Linux Experienced administrators seeking direct control and no Poolsman license fee Requires command-line familiarity and careful operational practice
45Drives Cockpit ZFS Manager Community Cockpit-oriented ZFS project Readers seeking a Cockpit-based alternative to evaluate before paying for Poolsman Check its current maintenance, feature set, compatibility, and support independently; parity is not established here

Webmin and other broad server panels may be useful if you already operate them, but their ZFS depth should be checked against the tasks you need rather than assumed equivalent.

Price and licensing: what the EAP costs

Prices observed on August 16, 2026 on the vendor’s EAP page are annual and per host:

Tier Price Support listed
Community $49 per host/year Updates and forum/community support
Standard $149 per host/year Professional support and three support tickets
Premium $299 per host/year Remote SSH support and ten support tickets

The vendor says EAP access includes the complete feature set and one year of updates; sales are non-refundable. It also says the final 1.0 licensing model may change, while current EAP licenses remain active through expiration. Verify the current price, terms, and support details on the EAP page before purchasing.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Who should use it?

Consider Poolsman if you already run a supported Linux host, want to retain that operating system, need substantial ZFS management rather than a status-only view, and value a GUI that exposes generated commands. It is a more natural fit if Cockpit is already part of your workflow and you accept paying for the module and support.

Look elsewhere if you need an integrated NAS operating system with sharing, applications, identity management, and appliance-style administration; require mature stable software without preview-stage uncertainty; need open-source-only or no-cost software; or expect one panel to manage every network, storage, container, backup, and sharing function. If your distribution or OpenZFS combination is outside the vendor’s named list, treat compatibility as something to validate, not assume.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.