Skip to content

CyberPanel vs cPanel: which control panel fits your WordPress servers

Compare CyberPanel and cPanel & WHM for hosting WordPress sites, and learn how to test your own sites against each before you commit. You will weigh license cost against operator time, check your .htaccess rules for Apache-only settings, and decide with evidence from a staging server.

This guide compares CyberPanel and cPanel & WHM for people who run WordPress sites and are deciding which control panel to put on their next server. Most people ask this question the week a cPanel license renewal lands, because CyberPanel is free and cPanel charges per account. The short answer is that CyberPanel fits a small number of sites you run yourself, on a server you are willing to patch closely. cPanel fits when you host many accounts, sell to resellers, or rely on tools like JetBackup and CloudLinux. By the end, you will have an inventory of your sites and a staging test that tells you which side of that line you are on.

What you’ll accomplish

  • Understand how each panel is built, from the admin screen down to the web server, PHP and cache.
  • Count your accounts, resellers, PHP versions and mailboxes, so the decision rests on your real numbers.
  • Find every .htaccess setting that depends on Apache and would behave differently on OpenLiteSpeed.
  • Run one real site on a CyberPanel staging server and confirm its redirects, uploads and cache work.
  • Walk away with a clear choice and a list of the work that choice brings with it.

Prerequisites

  • Root SSH access to your current cPanel server, so you can read account and .htaccess data.
  • A spare virtual machine for staging, sized like a small production server. Check the current supported OS list on cyberpanel.net before you pick an image, since it changes with each release. It has covered Ubuntu LTS and AlmaLinux families.
  • One representative WordPress site you can copy, ideally the one with the most custom rules.
  • About half a day. The inventory takes an hour. The staging test takes the rest.

How it works

Both panels are management layers. They sit on top of a web server, a PHP runtime and a cache, and they write the configuration for those pieces when you click through the admin screens. The real differences sit one layer down.

Side-by-side stack comparison. cPanel and WHM run on Apache built with EasyApache 4, or LiteSpeed Enterprise as a paid add-on, with PHP-FPM or LSAPI and caching mostly handled by WordPress plugins. CyberPanel runs on OpenLiteSpeed, or LiteSpeed Enterprise as a paid option, with LSAPI PHP and the LSCache module built into the server.

cPanel & WHM is commercial software. WHM (Web Host Manager) is the server-wide admin side, and cPanel is the per-account side that each customer or site owner sees. It is licensed per account, so the bill grows as you add sites. The default web server is Apache, built and updated through EasyApache 4, cPanel’s tool for choosing Apache modules and PHP versions. You can swap Apache for LiteSpeed Enterprise, a paid web server that reads Apache configuration unchanged. Around it sits a large ecosystem. That includes the WHM Transfer Tool for moving accounts between servers, JetBackup for backups, and CloudLinux for limiting how much CPU and memory each account can use.

CyberPanel is an open-source, free control panel built around LiteSpeed’s web servers. The free setup runs OpenLiteSpeed, the open-source edition of LiteSpeed. You can switch to LiteSpeed Enterprise with a paid license. CyberPanel includes WordPress installation with LSCache, the LiteSpeed cache that serves saved copies of pages without running PHP. It also bundles email, DNS, FTP and backups. Its extras, such as Docker management and one-click apps, change between versions, so check the current feature list rather than assuming.

PHP runs the same way on both LiteSpeed editions. LSAPI (LiteSpeed Server API) keeps lsphp worker processes alive between requests, which is fast. On a well-tuned cPanel server with Apache, PHP runs through PHP-FPM (FastCGI Process Manager), which is also fast. So raw PHP speed rarely decides this comparison.

The .htaccess file is where the two worlds differ most. Apache reads each directory’s .htaccess on every request, so an edit takes effect at once. OpenLiteSpeed reads rewrite rules from .htaccess, but a change needs a server restart before it applies. It also does not support every Apache directive, so settings like php_value or Header may be ignored. Our LiteSpeed Enterprise vs OpenLiteSpeed guide covers this edition difference in detail.

Security is a process, and the panel is part of your attack surface. Any control panel exposed to the internet needs prompt patching. CyberPanel had a publicly reported, actively exploited pre-authentication vulnerability in October 2024, patched afterward. Pre-authentication means an attacker did not need to log in first. cPanel has had security fixes too, published through its regular release process. The point is simple: whoever runs the server must watch advisories and apply updates within days, whichever panel you pick.

The decision tree below sums up these differences in four questions. Answer them in order, and stop at the first answer that sends you to the right.

Decision tree with four questions. Resellers or many client accounts, .htaccess files that go beyond rewrite rules, or a dependence on JetBackup, CloudLinux or WHM tools each lead to cPanel and WHM. With nobody to patch the panel every week, stay on cPanel for now. Otherwise CyberPanel is a good fit.

If you are also weighing Plesk, DirectAdmin or Enhance, read our comparison of cPanel, Plesk, DirectAdmin and Enhance alongside this one.

Step-by-step

Run steps 1 to 4 as root on your current cPanel server. Run steps 5 to 7 on the staging VM.

  1. Count accounts and resellers. This is the number that drives your cPanel bill, and the number that decides whether CyberPanel’s model fits.

    ls /var/cpanel/users | wc -l
    cut -d: -f1 /var/cpanel/resellers 2>/dev/null | grep -c .
    14
    0

    The first line is your cPanel account count. The second is resellers, meaning accounts that can create and sell their own sub-accounts. Any reseller count above 0 points strongly to cPanel. CyberPanel has reseller features, but they are much thinner than WHM’s, and your resellers’ customers would lose the cPanel screens they know.

  2. List the PHP versions your sites use. CyberPanel installs its own lsphp builds, so every version you depend on must exist there.

    whmapi1 php_get_vhost_versions | grep -oE 'ea-php[0-9]+' | sort | uniq -c
          3 ea-php74
         11 ea-php82

    Here, three sites still use PHP 7.4. Write down each version. In step 6 you will confirm the matching lsphp build exists on staging. An old version that CyberPanel no longer offers means those sites need a PHP upgrade before any move.

  3. Find .htaccess settings outside the rewrite family. This is the check that most often changes the answer. It lists every directive name used across all sites, except the Rewrite lines that OpenLiteSpeed handles.

    find /home/*/public_html -name .htaccess -type f \
      -exec grep -hoE '^[[:space:]]*<?[A-Za-z_]+' {} + \
      | tr -d ' \t<' | grep -v '^Rewrite' | sort | uniq -c | sort -rn
         14 IfModule
          6 Header
          4 php_value
          2 Options
          1 AuthType

    IfModule is the wrapper around WordPress’s standard block, and you can set it aside. Treat everything else as unsupported on OpenLiteSpeed until you test it on staging. To see which sites use them, list the files:

    find /home/*/public_html -name .htaccess -type f \
      -exec grep -lE '^[[:space:]]*(php_value|php_flag|Header|Auth[A-Za-z]+|Options|SetEnvIf)' {} +
    /home/shopone/public_html/.htaccess
    /home/clientb/public_html/.htaccess

    An empty result means your sites use only rewrite rules, which is the easy case. Each file listed is one site where the move needs manual work.

  4. Check what else the server depends on. These are the cPanel-side tools you would need to replace.

    grep '^NAME=' /etc/os-release
    command -v jetbackup5api
    find /home/*/mail -mindepth 3 -maxdepth 3 -type d -name cur | wc -l
    NAME="CloudLinux"
    /usr/bin/jetbackup5api
    37

    CloudLinux means you use per-account resource limits today. A path for jetbackup5api means JetBackup handles your backups. The last number is how many mailboxes exist. Each of these needs a named replacement on CyberPanel, or it is a reason to stay.

  5. Install CyberPanel on the staging VM. Use the install command from the official documentation at cyberpanel.net, because it changes between releases. Choose OpenLiteSpeed during setup to test the free edition. When the installer finishes, confirm the services are listening:

    ss -ltn | grep -E ':(80|443|7080|8090)[[:space:]]'
    LISTEN 0  4096   0.0.0.0:80     0.0.0.0:*
    LISTEN 0  4096   0.0.0.0:443    0.0.0.0:*
    LISTEN 0  4096   0.0.0.0:7080   0.0.0.0:*
    LISTEN 0  4096   0.0.0.0:8090   0.0.0.0:*

    Port 8090 is the CyberPanel admin screen and 7080 is the OpenLiteSpeed admin console. If 8090 is missing, read the installer log before going further. Firewall these two ports so only your own IP address can reach them.

  6. Confirm the edition and PHP builds. Check you are testing what you think you are testing.

    /usr/local/lsws/bin/openlitespeed -v
    ls -d /usr/local/lsws/lsphp*
    LiteSpeed/1.8.3 Open
    /usr/local/lsws/lsphp74  /usr/local/lsws/lsphp82

    Open confirms OpenLiteSpeed. Every PHP version from step 2 should have a matching lsphp directory. A missing one is a blocker for those sites.

  7. Copy your hardest site and test its rules. Create the site in CyberPanel and copy in the files and database of a site from step 3. Then point your laptop’s hosts file at the staging IP. Then check one redirect and one header from its .htaccess:

    curl -sI https://example.com/old-page/ | grep -iE '^(HTTP|location)'
    curl -sI https://example.com/ | grep -i '^x-frame-options'
    HTTP/2 301
    location: https://example.com/new-page/

    The redirect works, but the second command printed nothing, so the Header line was ignored. That is the typical result. If a rule does not apply, restart and retest before you conclude anything, because OpenLiteSpeed only picks up .htaccess changes on restart:

    /usr/local/lsws/bin/lswsctrl restart
    [OK] Send SIGUSR1 to 80124

    Rules that still fail after a restart need to move into the virtual host configuration, or be dropped.

Validate it works

Your evaluation is complete when you can answer each line below with a yes or a no, backed by output from the steps above.

  • The staging site loads over HTTPS, and you can log in to wp-admin and upload an image.

  • Every redirect you tested returns the same location as on the cPanel server.

  • Pages come back with a cache hit on the second request:

    curl -sI https://example.com/ | grep -i '^x-litespeed-cache'
    x-litespeed-cache: hit

    A miss on the first request is normal. A missing header after two requests means the LiteSpeed Cache plugin is not active on that site.

  • You have written down who will apply CyberPanel updates, and how often. A weekly check is a sensible floor for a panel that faces the internet.

Troubleshooting

A rule works on cPanel but not on staging. Restart OpenLiteSpeed first, as in step 7. If it still fails, the directive is likely unsupported. Rewrite it as a rewrite rule, or move it into the virtual host settings in the OpenLiteSpeed console.

Upload limits reset to defaults. A php_value upload_max_filesize line in .htaccess is not applied on OpenLiteSpeed. Set the value in the PHP settings for that lsphp version inside CyberPanel instead.

The cPanel backup import fails or misses data. CyberPanel documents a cPanel backup import, but results vary with account size and features. Check the site files, database and mailboxes one account at a time. Moving the other way, from CyberPanel back to cPanel, is a manual copy per site, so plan it before you need it.

The admin panel is reachable from anywhere. Restrict ports 8090 and 7080 to your own IP addresses with the server firewall. Leaving admin screens open to the world is how most panel compromises start.

When this is the wrong approach

Stay on cPanel if you run reseller accounts, host clients who edit their own .htaccess, or depend on JetBackup, CloudLinux or the WHM Transfer Tool. The license cost is real, but so is the time you would spend rebuilding those pieces and supporting clients through a new interface. Compare the yearly license against the hours of operator time the move and upkeep would take.

If you like LiteSpeed’s speed but not the move, keep cPanel and add LiteSpeed Enterprise. You get LSCache and LSAPI without changing panels. CyberPanel is the right pick when you run a handful of your own WordPress sites, your .htaccess files hold only rewrite rules, and someone owns patching.

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.