CloudPanel: self-hosted WordPress without a heavyweight panel

Legacy control panels — cPanel, Plesk — were long the default route into shared hosting. On dedicated VPS instances serving a few dozen sites, a lighter generation of tools has taken over. CloudPanel is its most visible representative. Here is what you gain, and what you agree to give up.

#What a heavyweight panel really costs

The bill for a legacy panel arrives through three channels. The first is licensing: both cPanel and Plesk work on a monthly subscription whose price grows with the number of hosted accounts. The second is memory: these suites bundle an Apache, mod_php and ancillary services stack that commonly holds 1.5 to 2 GB of RAM before serving a single page. The third, less visible, is a comprehension debt — when an incident occurs, the operator debugs the panel’s abstraction before debugging the server.

On a VPS you administer yourself, the abstraction layer you are paying for becomes the main obstacle to diagnosis.

#CloudPanel: technical scope

CloudPanel is a free, performance-oriented control panel built on Nginx (1.18 and above) with PHP-FPM, MySQL or MariaDB, and Redis. Version 2.5.4, released on 1 July 2026, adds support for Node.js 24, MariaDB 12.3 and Ubuntu 26.04. Everything is described in the official documentation.

The features that matter in day-to-day operation:

• Per-site PHP version: a PrestaShop on PHP 8.1 and a WordPress Bedrock install on PHP 8.3 coexist on the same machine with no manual configuration.
• Built-in Let’s Encrypt, with automatic renewal and no scheduled task to write.
• Redis and FastCGI cache available natively, with a measurable effect on WordPress installs.
• Live monitoring of CPU, memory and disk, plus service restarts from the interface.

#cPanel, Plesk, CloudPanel compared

#Installation

On a clean Debian 12 VPS, installation takes two commands, with the database engine chosen explicitly:

curl -sS https://installer.cloudpanel.io/ce/v2/install.sh -o install.sh
sudo DB_ENGINE=MARIADB_11.4 bash install.sh

The interface then answers on port 8443. The point worth noting for a technical profile: the panel generates a readable, overridable Nginx virtual host. A typical WordPress cache block can be added directly:

location ~* .(jpg|jpeg|png|webp|css|js|woff2)$ {
    expires 30d;
    add_header Cache-Control "public, no-transform";
    access_log off;
}

set $skip_cache 0;
if ($request_method = POST) { set $skip_cache 1; }
if ($http_cookie ~* "wordpress_logged_in") { set $skip_cache 1; }

#Observed migration procedure

On a fleet of WordPress Bedrock installs hosted at OVH, the migration sequence settles into four steps:

1. Provision a fresh VPS and install CloudPanel.
2. Create the site, point the domain, let Let’s Encrypt issue the certificate.
3. Restore code and database, enable Redis, wire the FastCGI cache.
4. Switch DNS, then apply the WordPress hardening baseline.

The gain shows on three axes: response time at equal configuration, hosting cost, and the ability to drive the machine from the command line as well as the interface — which matters for teams attached to their command-line tools. Pricing context reinforces the argument: OVH rates rose by up to 45% in 2026, which makes memory consumed by a panel more expensive than it used to be.

#Product limitations

• One server per installation: no native multi-node orchestration.
• No built-in mailbox management. Projects that delegate email to a dedicated service lose nothing; those looking for a turnkey webmail will need to look elsewhere.
• A smaller community than cPanel’s: fewer ready-made tutorials, more reliance on documentation and the terminal.

These are deliberate scope decisions, not hidden defects.

#What to take away

Moving to a lightweight panel means trading abstraction comfort for control and machine resources. The trade-off is favourable for anyone administering their own VPS and able to read an Nginx configuration. It is considerably less favourable for an organisation expecting a self-driving tool with no in-house systems skills.

#Also on Mail Studio

• WordPress hardening: the minimal security baseline
• Command-line tools for web development