for hosting providers
Don't migrate anything. The next server you turn on — the one you were going to buy anyway — turn it on with CorePanel: $24.99 a month, flat, per server. The WAF, the cache, the firewall, the per-account limits and the off-server backups are already in that number. Nothing you sell today gets touched.
One command on a spare server, then 14 days of Business free. No card, no sales call, nobody following up.
the second invoice
Price the next server, not the fleet. Every line below is a separate licence on a conventional build. Every one of them is already inside the $24.99.
$148.95 a month back on this server — $1,787.40 a year.
Every figure above is editable — put in the numbers on your own invoice. The ones we filled in are typical list prices, not quotes, and yours will differ. What doesn't differ: above 100 accounts that panel line grows by $0.49 per account, every month, forever. Ours doesn't grow at all.
That last sentence is the whole thing. Per-account pricing means your panel takes a commission on your growth. Every account you sell past 100 costs you before it has served a single byte. A flat licence is the same number on the day you have 40 accounts and the day you have 400.
And it has gone up every year since 2019. Not because the product changed — from your chair it looked much the same in December as it did in January — but because your margin is the easiest thing in this industry to tax.
the real problem
Suppose the panel were free tomorrow. You'd still be selling the same thing as the nine other results on the page: some storage, some PHP, a mailbox, a weekly backup. Same feature list, same screenshots, same promises.
When the offer is identical, the only lever left is price. And that race is won by whoever can afford to lose money longest — which, if you're honest, is not going to be you, and shouldn't have to be.
So the question isn't what does the panel cost.
It's what does the panel let me sell that I can't sell today.
a plan you can actually charge for
Same server. Same site. Same WordPress. The only thing that changed is that CorePanel's page cache is on. Every number below links to the run that produced it, method written out, re-runnable.
Time to first byte, WordPress home page
155× faster on a 2-vCPU box. And not a plugin cache: a plugin still boots PHP just to tell you it has a copy. Here nothing runs — the page is answered before PHP is involved. This is the number your customer sees in GTmetrix, and the one they screenshot to their boss.
Pages per second under concurrent load
With the cache off, 20 concurrent visitors already pinned the box at 100% CPU. Adding 380 more produced a queue, not a page: median response went to 26.5 s. That is the Monday morning ticket, the refund request and the one-star review. It stops happening.
p95 latency at 20 concurrent visitors
Half of that 51 ms is the network itself. The day one of your customers finally gets written about is the day this line decides whether you get a thank-you or a chargeback.
Server CPU per page view
PHP-FPM, MariaDB and the web server summed. At about a millisecond of CPU per cached view, the sites on that box stop fighting each other for the same two cores.
Measured on one server with the cache off and on — not against another panel. The method, the fixture and the two mistakes we made first are all written up in WordPress served without PHP.
Add that up and you're not selling "hosting, but cheaper". You're selling a managed WordPress plan with a single-digit-millisecond first byte, on a server whose licence costs you the same whether it holds 40 accounts or 400. That's a product with a price tag, not a line item in a race to the bottom.
read this before you say yes
You'll find this out in the first afternoon anyway. Better here, while it's still a cheap decision.
File access is FTPS. The protocol that would give us one is designed, not shipped.
Accounts are nologin by design. SSH administers the server; it is not something you resell.
There is no multi-server manager. Each box runs its own.
AlmaLinux, Rocky and RHEL 8/9/10. No Debian, no Ubuntu.
CorePanel is new. Instead of testimonials, every performance figure on this page links to the run that produced it, with the method written out so you can re-run it on your own hardware and check.
None of this touches the servers you already run. That's the entire argument for starting on a new one.
what it actually takes
One command on a fresh AlmaLinux, Rocky or RHEL box. Web server, mail, DNS,
MariaDB, multi-PHP, WAF and SSL come up configured. And nothing phones home to
change your server afterwards — dnf update is the entire update
mechanism.
A native module, plus compatibility with the WHM protocol your existing cPanel products already speak. You add a product. You don't reconfigure the ones you sell today.
Price it as what it is. The server underneath costs you $24.99 no matter how many accounts land on it, so every account after the first is margin, not a licence fee.
And if a customer does decide to move across later, the importer pulls accounts from cPanel — files, mail with its messages, databases, DNS, cron and SSL — preserving the original passwords. Your customer never learns their site moved. It reads the source server; it never writes to it.
what operators ask us
Which is why we are not asking you to move anything. Start Personal — free forever, the complete core stack, not a demo — on one spare box. If we vanish, you are out an afternoon. And there is no lock-in on the way out either: standard Postfix, Dovecot, MariaDB and Maildir underneath, so anything that reads a normal Linux server can read ours.
One server, one afternoon, one tech. If it does not click, you have spent an afternoon. The things that actually consume a sysadmin’s day — creating accounts, DNS, SSL, mail, a restore — are one screen each, and there is a CLI for every one of them.
Nothing. Every licence failure degrades the panel to Personal. It never degrades a site to offline. Your customers’ sites do not depend on our billing being reachable — that is a design rule, not a promise.
The free panels are Apache or Nginx with a UI bolted on top. CorePanel’s web server is ours: the cache, the WAF, WebP and Early Hints run inside the server, which is why the numbers above exist at all and why none of them need a plugin to be true.
No. The price is per server and the accounts are unlimited. We would rather have your twelfth server than a percentage of your growth; charging you more as you succeed is the exact business model this page is arguing against.
Install it, then start 14 days of Business from the panel itself — no card, nothing to cancel. The client area, hosting packages, WHMCS and the cache are all open from minute one, so you can build the plan and price it before you decide anything.
$ curl -fsSL https://get.corepanel.net/install.sh | bash And if you let the trial run out, nothing goes dark: the panel falls back to Personal — free forever, and the sites, mail and DNS on that server keep serving. A licence lapse degrades the panel, never a customer's site. When you do want to keep it, Business is $24.99 a month per server, bought in the panel in about a minute. No quote, no call, no minimum term.