Skip to content

Free cPanel alternatives: CloudPanel, CyberPanel, HestiaCP

CloudPanel, CyberPanel and HestiaCP are the free cPanel alternatives most people consider. Compare who each suits and how much work leaving cPanel takes.

CloudPanel, CyberPanel and HestiaCP are the free control panels most often considered as a cPanel alternative. CloudPanel suits one owner running their own PHP or Node.js apps. HestiaCP suits a small multi-user server that still needs mail and DNS, and CyberPanel suits WordPress sites that want the OpenLiteSpeed web server. If you sell hosting to many customers, often through resellers, cPanel usually stays the better fit. A control panel is the web interface that creates websites, databases, mailboxes and DNS zones for you, and cPanel/WHM is the paid panel most hosting servers run. The licence saving is easy to see; the work of moving is not. The steps below have you inventory your cPanel server, try a candidate panel on a spare VPS, and list which parts of the move stay manual.

What you’ll accomplish

  • Match your server to the right kind of panel: a single-owner app server or a multi-tenant hosting server.
  • Compare CloudPanel, CyberPanel and HestiaCP on mail, DNS, backups, multi-user support and supported operating systems.
  • Take a real inventory of your cPanel server: accounts, domains, mailboxes, DNS zones and databases.
  • Install one candidate on a throwaway VPS (virtual private server) and move one real site as a trial.
  • Finish with a migration-effort checklist you can put numbers against, plus a clear answer on whether to stay on cPanel.

Prerequisites

  • Root SSH access to your cPanel/WHM server.
  • A spare VPS with a fresh, supported operating system. Each panel wants a clean install and will refuse or misbehave on a server that already runs a web or mail stack.
  • A domain you can test with, or the ability to edit your local hosts file.
  • About two hours for one trial. Plan more if you test two panels.
  • If you are also weighing the paid panels, read cPanel vs Plesk vs DirectAdmin vs Enhance first. This article covers only the free ones.

Supported operating systems change with each release, so check each project’s current list before you build the VPS. At the time of writing, CloudPanel and HestiaCP both target Debian and Ubuntu LTS (long-term support) releases, and CyberPanel’s install guide lists Ubuntu and AlmaLinux releases.

How it works

Control panels fall into two families, and most bad panel choices come from mixing them up.

A single-owner app server runs sites that all belong to one person or team. You want fast web serving, easy databases and good deploy tools. You rarely need a mail server on the same box. CloudPanel is built for this.

A multi-tenant hosting server runs sites for many separate customers. Each customer needs a login, limits, mailboxes, DNS and backups they can restore themselves. Hosting companies often add a reseller tier, meaning customers who resell space to their own clients. cPanel/WHM is built for this, and CyberPanel and HestiaCP cover part of it.

Feature and fit matrix comparing cPanel/WHM, CloudPanel, CyberPanel and HestiaCP on web server, mail, DNS, resellers, operating systems and best fit

Here is each free panel in plain terms.

CloudPanel is a free panel built on NGINX and PHP-FPM (the FastCGI process manager that runs PHP), with site types for PHP, Node.js, Python, static sites and reverse proxies. It has no mail server by design, and its documentation recommends an external mail provider or a separate self-hosted mail stack. It has no DNS server either, so your zones live with your registrar or a DNS provider. Users get one of three roles: Admin, Site Manager, or User restricted to assigned sites. Remote backups go to S3-compatible storage, Dropbox, Google Drive, SFTP or any target that rclone (a command-line sync tool) supports.

CyberPanel is built around OpenLiteSpeed, the free edition of the LiteSpeed web server, and can run LiteSpeed Enterprise with a paid licence. It bundles Postfix and Dovecot for mail, PowerDNS for DNS, and has reseller accounts. It also ships an importer for cPanel backup files. Its admin interface listens on port 8090 by default. In October 2024, attackers used a critical CyberPanel flaw to encrypt files on a large number of internet-facing servers, so keep it patched and restrict that port to your own IP addresses. If you are unsure how OpenLiteSpeed differs from the Enterprise edition, read LiteSpeed Enterprise vs OpenLiteSpeed.

HestiaCP is an open-source community fork of VestaCP, an older panel whose development had stalled. It runs on Debian and Ubuntu, serves sites with NGINX in front of Apache (or NGINX with PHP-FPM alone), and includes Exim and Dovecot for mail, Roundcube webmail, and BIND for DNS. It has admin and user accounts with hosting packages, but its documentation does not describe a reseller tier. Backups can go off-server over FTP, SFTP or rclone. It includes a v-import-cpanel command that turns a cPanel backup into a Hestia user.

aaPanel and Webmin with Virtualmin also come up in searches. aaPanel is a free panel with one-click web stacks and paid add-ons. Virtualmin is a hosting panel built on Webmin, the long-running web interface for Linux administration, and it has a free GPL edition and a paid Pro edition. Both are worth a look, but check carefully which features sit in the paid tier before you compare.

Looking for an alternative to CloudPanel, CyberPanel or HestiaCP?

The same two families answer that question. If CloudPanel is missing something you need, it is usually mail, DNS or separate customer logins, and HestiaCP and CyberPanel both include those. If you want something lighter than CyberPanel, or you would rather not run OpenLiteSpeed, HestiaCP and CloudPanel both serve sites with NGINX. If HestiaCP feels limited because you need a reseller tier, CyberPanel has reseller accounts, and cPanel/WHM remains the complete version of that model. aaPanel and Virtualmin, described above, are the other names worth testing.

Why leaving cPanel takes real work

Between two cPanel servers, pkgacct packs a whole account into one cpmove file and restorepkg unpacks it, so the WHM Transfer Tool moves accounts in a few clicks. No free panel restores that file completely. HestiaCP and CyberPanel importers give you a head start on files, databases and some mail, but you still check every account by hand. Mail needs rebuilding or copying with a tool such as imapsync, DNS records need recreating, and cron jobs, redirects and PHP settings need checking one by one. The move is also one-way: nothing goes back into WHM with restorepkg, so a return trip costs the same effort again.

Decision tree for choosing between staying on cPanel, CloudPanel, HestiaCP and CyberPanel based on resellers, customers, mail and web server needs

Step-by-step

  1. Count the accounts and domains on your cPanel server. Run these as root on the cPanel server:

    whmapi1 listaccts want=user | grep -c ' user:'
    grep -vc '^\*' /etc/userdomains
    cut -d: -f1 /var/cpanel/resellers 2>/dev/null | grep -c .

    Expected: three numbers, for example 42, 118 and 2. The first is cPanel accounts, the second is every domain, subdomain and addon domain, and the third is resellers. If the third number is above zero, note it. Of the free panels here, only CyberPanel has resellers, and in a simpler form than WHM.

  2. Measure the mail and DNS work. Mail and DNS are the parts you rebuild, so size them now:

    find /home/*/mail -mindepth 3 -maxdepth 3 -type d -name cur | wc -l
    du -sch /home/*/mail 2>/dev/null | tail -1
    cat /etc/valiases/* 2>/dev/null | grep -vc '^\*'
    ls /var/named/*.db | wc -l

    Expected: four lines, such as 187, 64G total, 53 and 120. They are the email accounts, the total mail size, the forwarders, and the DNS zone files. A cPanel mailbox lives at /home/<user>/mail/<domain>/<mailbox>/, which is why the search looks three levels down for the cur folder. The default account mail for each cPanel user is not in that count, so add one per account that uses it.

  3. Count the databases and PHP versions. These tell you how much testing each site needs:

    mysql -N -e "SELECT COUNT(*) FROM information_schema.SCHEMATA WHERE SCHEMA_NAME NOT IN ('mysql','information_schema','performance_schema','sys');"
    whmapi1 php_get_installed_versions | grep ' - '
    ls /var/spool/cron | wc -l

    Expected: a database count such as 61, a list like - ea-php81 and - ea-php83, and the number of users with cron jobs. Confirm your candidate panel offers every PHP version in that list.

  4. Build a test VPS on a supported system. On the spare VPS, confirm the release:

    grep -E '^(NAME|VERSION_ID)=' /etc/os-release

    Expected, for a HestiaCP or CloudPanel test: NAME="Debian GNU/Linux" and VERSION_ID="12", or an Ubuntu LTS such as VERSION_ID="24.04". If the release is not on the panel’s current supported list, rebuild the VPS now. An unsupported release is the most common cause of a failed install.

  5. Install the candidate with its official installer. Use one panel per VPS. For HestiaCP, the documented commands are:

    wget https://raw.githubusercontent.com/hestiacp/hestiacp/release/install/hst-install.sh
    bash hst-install.sh

    For CyberPanel, the documented command is:

    sh <(curl https://cyberpanel.net/install.sh || wget -O - https://cyberpanel.net/install.sh)

    For CloudPanel, copy the command from the CloudPanel documentation. Its one-liner includes a checksum that changes with each release, so an old copy will fail on purpose. Each installer asks a few questions and finishes with the admin URL and login. Expected: HestiaCP on port 8083, CyberPanel on port 8090, CloudPanel on port 8443.

  6. Check what the panel really installed. On the test VPS, list the listening services:

    ss -tlnp | grep -E ':(25|53|80|443|993|8083|8090|8443) '

    Expected on HestiaCP or CyberPanel: lines for ports 25 and 993 (mail), 53 (DNS), 80 and 443 (web), and the admin port. Expected on CloudPanel: web ports and 8443, with nothing answering on 53 and no mail service for your domains on 25 or 993. That gap is by design, and it means your mail and DNS plans must live elsewhere.

  7. Move one real site as a trial. Pick a small, typical account. On the cPanel server, package it:

    mkdir -p /root/trial
    /scripts/pkgacct example /root/trial
    scp /root/trial/cpmove-example.tar.gz root@203.0.113.20:/backup/

    Expected: pkgacct ends with pkgacct completed, and the file arrives on the test VPS. Then import it with the candidate’s own tool:

    # HestiaCP
    v-import-cpanel /backup/cpmove-example.tar.gz
    v-list-web-domains example
    # CyberPanel (the path is a folder of cPanel backup files)
    /usr/local/CyberCP/bin/python /usr/local/CyberCP/plogical/cPanelImporter.py --path /backup
    cyberpanel listWebsitesJson

    Expected: the list command shows the account’s domains. On CloudPanel there is no importer. Create the site and database in the panel, copy the files with rsync, and load the database with mysql. Time this trial, because it is your per-account estimate.

  8. Fill in the migration-effort checklist. Multiply your trial time by the account count from step 1, then add the items below.

    ItemHow it movesEffort
    Website filesImporter, or rsyncLow
    DatabasesImporter, or mysqldump and mysqlLow
    Mailboxes and mailImporter where it works, otherwise imapsyncMedium to high
    Mail passwords, forwarders, filtersCheck each one, recreate what is missingMedium
    DNS zonesRecreate records in the new panel or a DNS providerMedium
    Cron jobs, redirects, PHP settingsCheck and recreate by handMedium
    Customer logins and habitsNew URL, new interface, new docsMedium
    ResellersRebuild as separate accounts, or stay on cPanelHigh

Validate it works

Test the trial site on the new server before touching public DNS. --resolve makes curl send the request to the test VPS without any DNS change:

curl -sI --resolve example.com:80:203.0.113.20 http://example.com/ | head -1
dig @203.0.113.20 example.com MX +short
nc -vz 203.0.113.20 993

Expected: HTTP/1.1 200 OK (or a 301 to HTTPS), the domain’s MX host from dig, and a succeeded or open message from nc. On CloudPanel, skip the last two checks, since mail and DNS live elsewhere. Then compare counts: the domains, mailboxes and databases for this account on the new panel should match what you measured in steps 1 to 3. Finally, log in to one mailbox with a mail client and send yourself a message in both directions.

Troubleshooting

  • The installer stops with an operating system error. The release is not on the supported list, or the server is not fresh. Rebuild the VPS with a listed release and run the installer first, before adding anything else.
  • The admin page does not load. Your cloud provider’s firewall is probably blocking 8083, 8090 or 8443. Open that port for your own IP address only, never for everyone.
  • The site loads but pretty URLs return 404. CloudPanel serves sites with NGINX, which ignores .htaccess files, so rewrite rules must move into the site’s NGINX configuration. OpenLiteSpeed reads rewrite rules from .htaccess but needs a graceful restart to pick up changes.
  • Imported mailboxes refuse the old password. Reset the password in the new panel and confirm the login. Check forwarders and filters at the same time, since importers do not always carry them.
  • Outgoing mail never arrives. Many cloud providers block outbound port 25 on new servers. Ask the provider to lift the block, or set up an SMTP relay (an outside service that sends mail on your server’s behalf). HestiaCP has a relay setting for this.

When this is the wrong approach

Stay on cPanel/WHM when any of these is true:

  • You sell hosting through resellers. WHM’s reseller tier, packages and limits have no full equal in these free panels.
  • You host many unrelated customers. Per-user isolation tools such as CloudLinux CageFS, plus the backup and security plugins built for cPanel, are hard to replace.
  • You move accounts often. The Transfer Tool and pkgacct save hours on every move, and a free panel gives that up.
  • Your team or your customers already know cPanel. Retraining and new documentation cost time you will not see on a licence invoice.
  • The labour outweighs the saving. If step 8 shows weeks of careful mail and DNS work, the per-account licence cost is often the smaller number.

A free panel is a good fit when the server is yours alone, carries a handful of sites, and has mail hosted elsewhere or only a few mailboxes. Plan DNS timing before any cutover with the TTL strategy by record type, and see the HestiaCP documentation for its full command reference.

If this is the kind of work you’d rather never own again, it’s the daily job of Managed Cloud Ops — book an infrastructure review.