Servoke

Servoke vs CloudPanel

CloudPanel is a tidy, site first panel for nginx and PHP. Servoke covers the same sites and adds mail, DNS, resellers and hosting accounts for customers, so a hosting company can run its whole server from one console.

Free, with a strong focus on simplicity
A fast NGINX, PHP-FPM and Redis stack
Images and installers for the common clouds

Servoke and CloudPanel, area by area

Pricing. Servoke: $4.99 a server a month. $3.99 each from 100 servers. A quote from 500 servers. CloudPanel: Free. A separate managed service on your own AWS account is 29, 49 or 99 EUR a month.
Accounts per licence. Servoke: Unlimited on every server. No fee per account, ever. CloudPanel: Sites, with Admin, Site Manager and User roles. A user can be limited to assigned sites.
Licence. Servoke: Commercial licence per server, checked on the server from a signed document. CloudPanel: A free proprietary licence, activated per server. Reselling it or hosting it for others needs written permission.
Websites, PHP and certificates. Servoke: nginx with PHP-FPM, Apache and OpenLiteSpeed engines, certificates issued and renewed for you. CloudPanel: NGINX with PHP-FPM, plus Node.js, Python, Varnish and free certificates.
Email hosting. Servoke: Postfix, Dovecot and Rspamd, with SPF, DKIM and DMARC written for you, and webmail. CloudPanel: Not included. The docs recommend an outside provider or Mailcow.
DNS hosting. Servoke: PowerDNS zones created with each domain. CloudPanel: No DNS server is included.
Databases. Servoke: MariaDB and PostgreSQL. CloudPanel: MySQL 8.4 or 8.0, or MariaDB.
Resellers. Servoke: Reseller accounts with their own packages and limits. CloudPanel: No reseller role. Users are Admin, Site Manager or User.
Per-account resource limits. Servoke: CPU, memory and IO limits per account on cgroup v2, with no add-on. CloudPanel: No per-site CPU or memory limits are documented.
Firewall and brute force guard. Servoke: Firewall, brute force guard, web application firewall and a security advisor. Every change in the audit log. CloudPanel: A UFW firewall, IP and bot blocking, Basic Auth and two factor sign in, with no brute force guard listed.
AI that reads the server. Servoke: Michael reads the real server and proposes each step for you to approve. Paid with JagAI credits. CloudPanel: No AI features are listed in the docs or changelog.
API, CLI and MCP. Servoke: Every console action is an /api/v1 call in OpenAPI. The CLI mirrors it, and an MCP server is built in. CloudPanel: The clpctl command line tool for root and site users. No HTTP API is documented.
Updates. Servoke: Checks hourly, verifies the signature, saves its state and puts the last build back if a new one is unhealthy. CloudPanel: Updated by running clp-update as root, and the docs advise taking a snapshot first.
Moving from cPanel. Servoke: Installs beside cPanel and imports its accounts. Take over stops cPanel and WHM in one click while every site, mailbox and zone keeps running, and Bring cPanel back is one click. CloudPanel: No cPanel importer. The docs give a manual guide for moving a PHP site.
Core runtime. Servoke: One Rust daemon with the consoles built in. Privileged changes are typed operations, never shell strings. CloudPanel: A PHP application shipped as a Debian package.

When CloudPanel is the better fit

If you only host your own PHP sites on a cloud image and keep mail and DNS elsewhere, CloudPanel is lean and focused.

From CloudPanel to Servoke

Install Servoke on a fresh server: Keep the old server running while you move.
Move sites and databases: Copy files with SFTP and load databases with the database tools.
Add mail and DNS: Servoke can host them on the same server, or you can keep your current providers.

Related comparisons

Compare Toolbox Terms of Service EULA Privacy Policy