Mail, in full
The reason people cannot leave cPanel — and cannot move to a modern panel.
- Postfix + Dovecot, per-account mailboxes
- Roundcube webmail on webmail.<domain>
- Rspamd antispam, SPF / DKIM / DMARC
RHEL 8/9/10 · AlmaLinux · Rocky
The next-generation
hosting control panel.
Mail, PHP, WordPress, DNS — all of it, on a stack built this decade. Your server, running clean.
No license key. No limits on features. Just documentation-supported.
full mail stack + webmail 0700 isolation native WAF, every edition cPanel import built in
Dashboard
web-01 · AlmaLinux 9
CACHE HIT0%
CPU0%
DISK0%
STACK 5 running
corehttpdhttp/3 · waf · cacherunning
php-fpm8.4 · pool per accountrunning
dovecotimap · postfix · rspamdrunning
mariadb10.11 ltsrunning
pdnsauthoritative dnsrunning
INSTALL
$ curl -fsSL https://get.corepanel.net/install.sh | bash 01
nothing missing
Everything you'd expect.
Still all here.
Most "modern" panels earn the label by dropping things — no mail, no multi-PHP, no DNS, no reseller accounts. CorePanel is next-generation underneath and a complete hosting panel on top. You are not asked to give anything up.
PHP and WordPress
The workload that actually pays the bills, tuned rather than tolerated.
- Multi-PHP 7.4 and 8.1 – 8.4, FPM pool per account
- WordPress Manager — install, harden, wp-cron
- MariaDB 10.11 LTS
The rest of the stack
Every box a hosting account is expected to tick.
- DNS (PowerDNS), FTPS chrooted per account
- Free wildcard SSL — web, mail and FTP
- Kernel-enforced disk quotas, per-account cron
- Scheduled backups
Moving in
The way out of your current panel is part of the product.
- cPanel import — archive or live pull
- Hosting packages for resold plans
- WHMCS integrationBusiness
02
the difference
Native,
not bolted on.
Classic control panels are a web interface over other people's software — Apache, ModSecurity, Varnish, a licensed kernel module. Every layer is someone else's release cycle, and half of them are someone else's invoice. CorePanel ships the stack it manages.
| Capability | Classic control panels | CorePanel |
|---|---|---|
| Web server | Apache or nginx, wrapped in generated config | CoreHttpd — written for this panel |
| Web application firewall | ModSecurity bolted on, rule sets sold separately | pxShield, native — every rule family, every edition |
| Early Hints (HTTP 103) | Not available | Native, on by default |
| WebP conversion | A plugin per site | On-the-fly in the web server |
| Account isolation | Shared group, permissive defaults | 0700 / 0600, PHP-FPM pool per user, SELinux enforcing |
| Applications beyond PHP | SSH and a systemd unit you write yourself | Deploy, env, logs and health from the panel |
| Dynamic page cache | Varnish in front, or a caching plugin | In the web server, with smart invalidation Pro+ |
| Host firewall | A shell script over iptables | Managed in the panel, with automatic blocking Pro+ |
Rows marked Pro+ ship in the paid editions. Everything else is in Personal, free. Compare editions →
03
measured, not claimed
What owning the stack
actually buys you.
Every panel says it is fast. These are numbers from a documented run on a 2-vCPU server, with the method published alongside them — including the cases where the cache does nothing at all.
5,507pages/s
Pro+WordPress with 400 posts, 400 concurrent visitors. Without the cache the same server does 12.1.
1.6ms
Pro+Time to first byte on a cached home page, down from 248 ms. The request never reaches PHP.
0licences
Third-party licences to buy. No ModSecurity rule subscription, no kernel module to rent.
Install it and see.
Personal is free and ships the complete stack — mail, PHP, WordPress, DNS, the full WAF. No licence key, no feature locked behind a trial clock.
Already running cPanel? Transform that server in place — same machine, same IP, 28 seconds offline.