Best cPanel Alternatives for Linux VPS Na Which?
Compare free cPanel alternatives for VPS: Virtualmin, ISPConfig, CyberPanel, HestiaCP, CloudPanel and Froxlor, plus install commands and migration traps.
Which cPanel alternatives you fit install for VPS today
The free cPanel alternatives wey you fit install for Linux VPS today na Virtualmin, ISPConfig, CyberPanel, HestiaCP, CloudPanel and Froxlor. Each one dey install for fresh server, and each one leave out something wey cPanel get. The real choice na which missing part you fit manage without, and how many hours you go spend to move.
cPanel na two programs. WHM na the server side. cPanel na the per-account side. Together, dem dey manage Apache virtual hosts (vhosts), PHP versions, MySQL users and grants, DNS zones, Exim and Dovecot mail, FTP accounts, cron jobs, certificates, and per-account backups. Panel dey write and manage the configuration files for your server, instead of just sitting on top as web interface. Na why every project below tell you to start with fresh operating system.
Wetin cPanel cost, and where the real cost dey hide
Di data wey dey behind dis chart
[
{
"plan": "Solo",
"usd_per_month": 29.99,
"accounts_max": 1
},
{
"plan": "Admin",
"usd_per_month": 35.99,
"accounts_max": 5
},
{
"plan": "Pro",
"usd_per_month": 53.99,
"accounts_max": 30
},
{
"plan": "Premier",
"usd_per_month": 69.99,
"accounts_max": 100
}
]Na the published monthly prices per server be these, as we read am from cPanel pricing page for October 2026. Solo licence cover one account at 29.99 USD every month. Premier cover 100 accounts at 69.99 every month, and dem bill extra accounts separately. If you pay yearly, the price go reduce small.
Na the licence be the number wey everybody dey quote. But na the hours dey decide the real cost, and dem price those hours further down this page.
How much RAM one control panel need?
Two different numbers dey important here, and if you mix dem up, na why pipo go put full panel for 1 GB VPS come dey wonder why the box dey swap.
Di data wey dey behind dis chart
[
{
"label": "Virtualmin, mini install",
"min_ram_gb": 1
},
{
"label": "HestiaCP, no mail filtering",
"min_ram_gb": 1
},
{
"label": "CyberPanel",
"min_ram_gb": 1
},
{
"label": "CloudPanel",
"min_ram_gb": 2
},
{
"label": "Coolify",
"min_ram_gb": 2
},
{
"label": "Virtualmin, full stack",
"min_ram_gb": 4
}
]Dem numbers na the minimum wey each project write for dia own documentation, e no be measurement wey dem take from box wey no dey do anything. CyberPanel installation documentation ask for 1024 MB of RAM and 10 GB of disk. ISPConfig and Froxlor no publish any figure, so dem no dey for the chart instead of make we guess. Read the first row and the last row join: the same software ask for 1 GB if mail no dey and 4 GB if mail dey.
The second number na wetin the services wey dey under the panel dey consume, and e pass the panel itself. Virtualmin low memory page show the price of the parts; ClamAV Docker documentation give the antivirus allocation wey dey below.
Di data wey dey behind dis chart
[
{
"label": "ClamAV virus scanning, Docker preferred",
"typical_ram_mb": 4295
},
{
"label": "SpamAssassin",
"typical_ram_mb": 1024
},
{
"label": "MySQL or MariaDB",
"typical_ram_mb": 400
},
{
"label": "Apache",
"typical_ram_mb": 250
},
{
"label": "PHP",
"typical_ram_mb": 100
},
{
"label": "The panel itself",
"typical_ram_mb": 30
}
]ClamAV Docker documentation talk say minimum na 3 GiB and e prefer make you give am 4 GiB, wey be about 4295 MB, because 2 GB fit no reach. Dem estimate SpamAssassin for 1024 MB, while the panel process dey near 30 MB. The panel na the cheapest thing for the server. Mail filtering na the expensive one, so panel wey no get mail server go run well for 2 GB; Virtualmin document say about 4 GiB na minimum for full-stack, but if you give ClamAV the 4 GiB wey e prefer, you go need extra RAM for the other services. If you give am small, e go dey fight your PHP workers for memory all day.
Virtualmin: cPanel and WHM wey e resemble pass
Virtualmin dey run on top Webmin and e get the same structure wey cPanel get: server view for admin, per-domain view for site owner, and resellers above dem. E get documented importer for cPanel account archives. Na one of three free panels for here wey fit do am, together with CyberPanel and HestiaCP.
sudo sh -c "$(curl -fsSL https://download.virtualmin.com/virtualmin-install)" -- --bundle LAMPUse --bundle LEMP instead of Nginx. Add --type mini for the light install. This one skip local mail, spam and virus filtering, local DNS, FTP, and Jailkit, but e still keep the complete web stack. The installer fully support Red Hat Enterprise Linux, AlmaLinux and Rocky Linux 8, 9 and 10, Debian 12 and 13, and Ubuntu 24.04 and 26.04 LTS (long term support). Ubuntu 22.04 no dey the list again. Another set of systems, including Fedora Server, CentOS Stream and Ubuntu interim releases, go install only when you add the --os-grade B flag. Anything wey no dey for either list no dey within wetin the automated script cover.
Import cPanel account archive from command line.
virtualmin migrate-domain --source /root/backup/example.com.tgz --type cpanel --domain example.com --user exampleuserThe command suppose report the new virtual server, and e go then show for the domain list. When e fail, na usually the archive cause am: partial cPanel backup, or backup wey newer cPanel write pass wetin the importer sabi, no dey restore cleanly. The same tool fit take Plesk and DirectAdmin archives with --type plesk or --type directadmin.
Wetin e no do well: the interface na Webmin own, so one page fit get forty form fields without clear default value. If you don already work with Webmin for Ubuntu 24.04, you sabi how e feel. Virtualmin also dey come as free GPL edition and paid Pro edition. The free interface dey advertise Pro features for the same place, and some people find this irritating.
ISPConfig: one panel, plenty servers
ISPConfig na the answer when web, mail and DNS dey for different machines. One control panel dey manage all of dem; Coolify too dey offer free multi-server management, with unlimited connected servers for its self-hosted edition. Its README get a piped installer. Download am first so you fit read am and list its flags.
curl -fsSL https://get.ispconfig.org -o ispconfig-install.sh
less ispconfig-install.sh
sudo sh ispconfig-install.sh --help
sudo sh ispconfig-install.shISPConfig own documentation, wey dem read on 4 November 2026, list the autoinstaller for Debian 11 through 13 and Ubuntu 22.04 through 26.04, with ARM support, so arm64 VPS na valid target. Autoinstaller explicitly cover Ubuntu 26.04. The installer dey reconfigure the whole server, so e belong for fresh operating system and nothing else.
The thing wey e no do well: no free cPanel importer dey. The vendor paid Migration Toolkit add-on, wey dem list at 79 euros excluding VAT for October 2026, name cPanel as source and carry web files, mail and databases across, but dem mark its cPanel support as beta. So migrate one test account before you plan the whole move around am. The interface plain and dense, and e assume say you already know wetin vhost, jailed shell user and DNS zone mean.
CyberPanel: OpenLiteSpeed, and one security record wey worth reading
CyberPanel dey built around OpenLiteSpeed, and na the quickest among these panels to make cached WordPress site run. Install am as root.
sudo su -
sh <(curl https://cyberpanel.net/install.sh || wget -O - https://cyberpanel.net/install.sh)Run that line from bash. The <(...) form na process substitution, wey be bash feature, so plain sh or dash shell go reject the line with syntax error before anything download. The current stable installer accept Ubuntu 22.04, 24.04 and 26.04, AlmaLinux 8, 9 and 10, Rocky Linux, RHEL, CloudLinux and CentOS. E architecture check accept both x86_64 and aarch64 (ARM64). The project still list Ubuntu 20.04 too, but its standard support end on 31 May 2025; extended support still dey available through Ubuntu Pro, so no build new server on am.
E get cPanel importer. Put the account archives inside one directory, then point the importer to that directory.
/usr/local/CyberCP/bin/python /usr/local/CyberCP/plogical/cPanelImporter.py --path /home/backupThe importer first prints the path to its log file. If site no appear for the panel afterwards, that log go show the account and the step wey fail.
The serious problem no be interface preference. For October 2024, unauthenticated remote code execution flaw for CyberPanel 2.3.6 and 2.3.7, tracked as CVE-2024-51378, attackers exploit am widely. Attackers run commands as root over the network and encrypt the servers with PSAUX ransomware. The flaw enter CISA catalogue of known exploited vulnerabilities. The lesson apply to every panel here: control panel na root shell with login form in front. No leave its port open to the whole internet. Restrict am to your own address with a ufw rule for the VPS, or reach am through a WireGuard tunnel wey you host yourself, and patch am during the week wey release land. OpenLiteSpeed also treat .htaccess differently from Apache. E apply rewrite changes when server restart, instead of on every request. So application wey rewrite that file at runtime go behave differently from how e behave on cPanel. CyberPanel also offer paid .htaccess module for Apache-style directives, separate from its free custom OpenLiteSpeed binary.
HestiaCP: di easiest full stack
HestiaCP na fork wey dem dey maintain from VestaCP, and e be di shortest way to get web, mail, and DNS server wey get clean interface. Run di installer as root for fresh system.
sudo -i
wget https://raw.githubusercontent.com/hestiacp/hestiacp/release/install/hst-install.sh
bash hst-install.shDi script go ask you question one by one, show you di panel URL and admin login for di end, and ask if you wan reboot. HestiaCP support Debian 12 and 13, plus Ubuntu 22.04, 24.04, and 26.04, for both x86_64 and arm64. Release 1.10.5 don remove Debian 11. Di minimum requirement na 1 core, 1 GB of RAM, and 10 GB of disk space, provided you no install SpamAssassin and ClamAV. Dat arm64 support dey important if your VPS na ARM instance. Hestia still dey, just like ISPConfig, Virtualmin, CloudPanel, and CyberPanel, wey dia current stable installer sef dey accept arm64.
E also get cPanel importer inside im command line tools. Copy your cPanel backup go di server and run am as root, e go restore di archive enter new Hestia user.
v-import-cpanel /backup/backup.tar.gzOne matching v-import-directadmin dey for DirectAdmin backups. Both of dem come from community import scripts wey dem write for VestaCP, so make sure you check every site and mailbox wey you restore before you move your DNS. Di cPanel importer list certificate import failure and missing DKIM update as things wey fit happen, so make sure you reissue certificates and check your DKIM after you finish restore.
Wetin e no dey do well: e dey manage one server, e no fit manage plenty server at once. Di default setup put Nginx for front of Apache, wey dey okay until you try debug redirect loop and you come dey wonder which one of di two cause di wahala.
CloudPanel: fast, and e no dey do mail
CloudPanel na Nginx only, with short interface and sensible PHP defaults. Check the licence before you commit. E free to use, but na proprietary freeware, no be source available or open source, and one company dey develop am. The licence treat the source code as confidential, and the public repository get README and supporting assets instead of the panel source code. This na real difference between am and the others for this page.
curl -sS https://installer.cloudpanel.io/ce/v2/install.sh -o install.sh
echo "8146dbe0a488e7088b04071b0c34d59aa0ab1fe9dcec382d395fd155c9e6c476 install.sh" | sha256sum -c
sudo DB_ENGINE=MYSQL_8.4 bash install.shThe checksum line must print install.sh: OK before you run anything. That hash dey change with every installer release, so copy the current one from CloudPanel own installation page on the day you install, no be from any article, including this one. Use DB_ENGINE=MARIADB_11.8 on Ubuntu 26.04 or Debian 13, or DB_ENGINE=MARIADB_11.4 on Ubuntu 22.04, Ubuntu 24.04 or Debian 12, if you prefer MariaDB. Supported systems na Ubuntu 22.04, 24.04 and 26.04 and Debian 12 and 13, for x86 and ARM64, with stated minimum of 1 core, 2 GB of RAM and 10 GB of disk.
Wetin e no do well: no mail server and no DNS server. If you dey leave cPanel and your users get mailboxes for there, CloudPanel no replace wetin you get before. Mail go then become separate service, such as self-hosted Mailcow mail server, and DNS go move to your registrar or DNS provider.
Froxlor: e light, and e expect say you sabi your stack
Froxlor na the smallest among all of dem. E dey manage customers, domains, PHP-FPM pools, and quotas, and e dey write configuration for services wey you don install and tune by yourself. Install am from the project apt repository.
sudo apt -y install apt-transport-https lsb-release ca-certificates curl gnupg
sudo curl -sSLo /usr/share/keyrings/deb.froxlor.org-froxlor.gpg https://deb.froxlor.org/froxlor.gpg
sudo sh -c 'echo "deb [signed-by=/usr/share/keyrings/deb.froxlor.org-froxlor.gpg] https://deb.froxlor.org/debian $(lsb_release -sc) main" > /etc/apt/sources.list.d/froxlor.list'
sudo apt update && sudo apt install froxlorFor Ubuntu, change deb.froxlor.org/debian to deb.froxlor.org/ubuntu for that source line. Froxlor get documentation for Debian 11, 12 and 13 and Ubuntu 22.04 and 24.04, wey support PHP 7.4 go reach 8.5 and MySQL 8.4 or MariaDB 11.7 for im current documentation. After the package finish install, you go complete the setup for browser, then point Froxlor go Apache or Nginx.
Wetin e no dey do well: e no dey give you plenty things. No cPanel account importer dey, but im separate quick installer now dey install and configure Postfix and Dovecot join the web stack. If you sabi build a LAMP stack on Ubuntu 24.04 by hand, Froxlor na layer wey customers fit use on top of that work. If you no sabi, e go be like say the work never finish.
Di two honest answers wey no be panel
The first one na reverse proxy plus compose files. Each application go run as container, one file for each app, and proxy for front go terminate TLS (transport layer security) and route traffic based on hostname. Na Traefik for front of several Docker Compose apps, wey dey build on Compose basics for VPS. E suit one operator wey dey run their own applications. E no suit customers wey need log in and change their own PHP version.
The second one na platform as a service (PaaS) style panel. Coolify dey deploy from git repository, build the image, and manage the proxy for you.
curl -fsSL https://cdn.coollabs.io/coolify/install.sh | sudo bashCoolify dey ask for 2 cores, 2 GB of RAM and 10 GB free disk space, plus extra space for Docker images, volumes and backups, and its own interface dey listen on port 8000 after the script finish. Na deployment tool e be, so e no get per-customer hosting accounts for the cPanel meaning; e document how to deploy Stalwart as separate mail service, with mailboxes wey you manage inside Stalwart. Comparison of Cloudron, CasaOS and Coolify explain where each one dey fit.
If the reason wey you get cPanel na because other people dey log in and manage their own site and mailbox, none of these two answers fit, and your list na Virtualmin, ISPConfig or HestiaCP.
Questions wey go decide whether real migration go happen
E dey import cPanel backups? Virtualmin, CyberPanel and HestiaCP get documentation for free importers. ISPConfig dey sell one as part of im paid Migration Toolkit add-on, but cPanel support still dey marked beta. CloudPanel and Froxlor no get importer, so you go move files, databases and mailboxes by hand. After import, check document roots, databases, mail accounts, PHP handler settings, custom Apache directives and anything wey you tune for WHM.
E dey handle mail? Virtualmin for im full install, ISPConfig, HestiaCP, CyberPanel and Froxlor all fit manage mailboxes. CloudPanel no fit; Coolify dey deploy separate mail service like Stalwart instead of managing mailboxes by itself. Mail na the expensive part of any migration. Mailbox passwords dey stored as hashes, and HestiaCP's cPanel importer dey copy those hashes, so migration no automatically mean say every user must reset password. For manual mail migration, copy messages with an IMAP (internet message access protocol) sync tool like imapsync. Mail authentication records, SPF, DKIM and DMARC, must correct for the new server before cutover. If not, your mail fit land for spam folders from day one.
E dey handle DNS? Virtualmin, ISPConfig, HestiaCP and CyberPanel dey run authoritative nameserver for you. CloudPanel and Coolify no dey. Plenty people wey dey run small number of sites keep DNS for their registrar or DNS provider. This remove the question and one more listening service from the server.
Wetin go happen to your existing vhosts? Dem dey at risk. Na why every installer for here dey tell you make you use fresh operating system. These scripts dey write inside web server, database and mail configuration directories, then restart those services. So, if you run one for server wey already hosts sites, e fit overwrite the configuration wey those sites depend on. Build on second VPS, move the sites, test with hosts file entry, then move DNS. Reduce the time to live (TTL) for your records to 300 seconds one day before cutover, and keep the old server running for one week after the cutover.
How certificates go be? Every panel for here dey automate Let's Encrypt issuance and renewal. If you remove the panel, na you go handle that work. That means Certbot with Nginx on Ubuntu 24.04 and renewal timer wey you check once every quarter.
Cost wey nobody dey write down
Licence na the small number. The move na the big one. For one WordPress site, the work fit be one evening: copy files, dump and import the database, reissue the certificate, then change DNS. For twenty customer accounts with mailboxes, na one week of evenings, and the work wey remain after the move go last pass the move itself. You go handle the support questions wey cPanel interface used to absorb. You go answer “where my email password dey” for everybody wey their mail client stop connecting. From that time, na you own the panel security updates, and CVE-2024-51378 show wetin that ownership fit look like for one bad week.
Two habits fit make the remaining work shorter. Give every site its own system user instead of running everything under one account. Na the practice for least privilege users for VPS, and every panel here dey do am by default. Also restore one site from your new backups before you switch DNS, no be after.
None of this mean say cPanel na bad software. E mean say the licence buy support contract and twenty years of hosting industry defaults. If na your own sites you dey run for your own server, na that support desk you don already dey act as.
FAQ
Which free cPanel alternative fit import cPanel backup?
Virtualmin, CyberPanel, and HestiaCP na the three free panels wey get documented importers. For Virtualmin, you go run virtualmin migrate-domain --source /root/backup/example.com.tgz --type cpanel --domain example.com, and the same tool fit accept Plesk and DirectAdmin archives. For CyberPanel, you go put the archives for one directory and run the bundled importer for /usr/local/CyberCP/plogical/cPanelImporter.py with the --path flag. For HestiaCP, you go run v-import-cpanel with the path to the backup, and e go create new user from am. ISPConfig sef get one, but na only inside their paid Migration Toolkit add-on, wey mark cPanel support as beta. Make sure you check PHP handler settings, custom Apache directives, and WHM tuning by hand after any import.
How much RAM a control panel need for VPS?
The panel process small, e dey near 30 MB according to Virtualmin own estimate. Wetin dey cost memory na the stack wey dey under am, and mail filtering dey take the most: ClamAV Docker documentation talk say 3 GiB na minimum and dem prefer 4 GiB, while Virtualmin estimate say SpamAssassin dey take around 1 GB. Panel wey no get mail server, like CloudPanel, fit run for 2 GB VPS. Virtualmin document say 4 GiB na the minimum for full hosting stack, but to give ClamAV the 4 GiB wey e prefer go need extra RAM for the other services. For 1 GB, you fit run mini install with mail turned off, or you add swap and accept say the machine go dey use am.
I even need control panel for VPS at all?
No. If na only you dey login, panel mostly dey add attack surface, because e be privileged web application wey dey listen for one port. Reverse proxy wey get one Compose file per application dey do the same work with less software exposed. Panel dey useful when other pipo need manage their own sites, mailboxes, and databases without shell access, because to build that interface by yourself dey take more work pass just to run one.
I fit install panel for server wey already get sites?
Treat am as unsupported. Virtualmin, ISPConfig, CyberPanel, and HestiaCP all dey tell you make you start from fresh operating system, because their installers dey write web server, database, and mail configuration and dem dey restart those services. To install for live box fit overwrite the configuration wey your sites depend on, and no way to undo am. Build the panel for new VPS, migrate site by site, then move DNS once the new server dey serve the same pages.
Which cPanel alternatives dey handle email?
Virtualmin for im full install, ISPConfig, HestiaCP, CyberPanel, and Froxlor all dey manage mailboxes and the DNS records wey follow dem. CloudPanel no dey manage mailboxes; Coolify document say you fit deploy Stalwart, wey get im own mailbox administration. Decide this question first if na mailboxes make you dey use cPanel, because Coolify need separate mail service and CloudPanel need external mail setup, and mail na the part of migration wey dey take longest time.