cPanel is a web interface that turns Linux server administration into forms: it creates system users, writes web server virtual hosts, provisions MySQL databases, requests certificates and configures mail, all without you touching a config file.
That is a genuinely valuable thing for a specific audience, and a layer of complexity you may not need for a different one. Which of those you are depends almost entirely on whether you administer websites for other people.
This is a tour of what is actually in there, what it costs now that licensing has changed, and an honest view of when the answer is not to use a control panel at all.
Table of contents
- What the sections actually do
- cPanel and WHM are not the same thing
- The licensing change that reshaped the market
- Where control panels genuinely earn their keep
- Where it is the wrong abstraction
- How this fits the rest of the stack
- FAQ
What the sections actually do
The interface is a grid of icons and it is not obvious which ones matter. Roughly in order of how often they are used:
- Files. A file manager, disk usage, FTP accounts and backups. The file manager is genuinely useful for a quick edit; the backup section is worth understanding properly before you need it.
- Databases. Creates MySQL databases and users, and grants privileges. Note that creating a database and creating a user are separate steps, and the third step of assigning the user to the database is the one people forget.
- Domains. Addon domains, subdomains, redirects, and the DNS zone editor. The zone editor is where A, CNAME, MX and TXT records live.
- Email. Accounts, forwarders, autoresponders, spam filtering. Frequently the reason a business is on cPanel at all.
- Security. SSL/TLS status, hotlink protection, IP blocking, and ModSecurity toggles.
- Software. PHP version selection, Node.js application setup, and a one-click installer for common applications.
- Metrics. Visitor statistics, bandwidth, error logs. The error log link is the most useful item on the page and the least used.
The single most important habit: when something breaks, go to Metrics and read the error log before changing anything. The answer is usually sitting there in plain text.
cPanel and WHM are not the same thing
This confuses nearly everyone at first, and the distinction is straightforward once stated.
WHM is the administrator interface. It runs at the server level, creates and suspends accounts, sets package limits, manages services and installs system-level software. If you have root on the box, you are in WHM.
cPanel is the end-user interface. It runs at the account level and manages one website’s files, databases, email and domains. Its user cannot see or affect other accounts on the same server.
Shared hosting customers get cPanel only. Buy a VPS or dedicated server with a licence and you get both: WHM to create the accounts, cPanel inside each one. Resellers live in WHM full time, because their product is creating cPanel accounts for their own customers.
The practical consequence is that half the tutorials you find do not apply to you. If a guide says to open WHM and you only have cPanel, your host controls that setting and you need to ask them.
The licensing change that reshaped the market
cPanel was historically licensed per server at a flat rate. In 2019 it moved to per-account tiered pricing, and the increase for anyone running many small sites on one machine was substantial.
Two consequences that still shape decisions today:
- Density stopped being free. Packing two hundred small sites onto one server used to cost one licence; now the licence scales with the accounts, which changes the arithmetic for small hosting businesses considerably.
- Alternatives got serious. Several competing panels, including free ones, gained real adoption in the years afterwards, and the assumption that a hosting server means cPanel is much weaker than it was.
If you are pricing a self-managed hosting setup, get a current quote for the account tier you actually need rather than relying on a figure from an old article. It is a recurring cost that sits alongside the server, not inside it, and for a small number of sites it can exceed the server itself.
Where control panels genuinely earn their keep
There is a real case for this software and it is worth stating clearly rather than dismissing.
A control panel is the right tool when you administer sites for other people. If you build websites for clients, need to hand each client a login that cannot break the others, and want email, backups and certificates handled without writing configuration, this is exactly the product for that.
It is also the right tool for a business whose website is WordPress, whose staff are not developers, and where the ability to add a mailbox or restore a file without a support ticket is worth the licence.
And it has genuine value as a common language. Any freelancer you hire knows this interface, which is a real reduction in onboarding cost compared to a bespoke setup only you understand.
Where it is the wrong abstraction
The case against is equally specific. A control panel assumes a particular shape: long-lived servers, sites configured by hand, state living on the machine.
That assumption breaks for an application team, and it breaks in ways that matter:
- Configuration is not in version control. Settings live in a database on the server. You cannot review a change, cannot diff two environments, cannot recreate the machine from a repository.
- Deployment is a file copy. No build step, no atomic switch, no rollback to the previous version. The classic failure is a partially uploaded deploy serving broken pages.
- Staging is a manual clone that drifts from production immediately.
- The panel owns the server. It writes the web server configuration, so hand-editing files gets overwritten on the next update.
- It is a large privileged surface. A control panel runs as root and exposes a login to the internet, which is a meaningful thing to keep patched.
For a team shipping application code from a repository, the useful abstraction is a deploy pipeline rather than a file manager. On RunxBuild that means pushing to GitHub, getting a build log, a live route, environment variables, runtime logs and a rollback to the previous deploy, with the GitHub deployment docs covering the connection. Different product, different problem.
The WordPress case sits between the two. RunxBuild’s managed WordPress keeps the two things people actually use a panel for, a file manager and a database browser in the dashboard, without the rest of the server administration surface.
How this fits the rest of the stack
The honest way to decide is to add up what you are paying for, because the control panel licence, the server, the backups and the bandwidth are four separate lines and the panel is the one most often left out of the estimate. The RunxBuild hosting calculator prices the managed shape, which is the right comparison when you are working out whether you need a panel at all or just needed the things it was doing for you.
Useful related references:
- Plesk Software: What a Control Panel Actually Buys You
- Cloud Governance: The Framework That Keeps the Cloud Under Control
- Python next Function: Consume Iterators Without Losing Control
- Services on RunxBuild
FAQ
What is the difference between cPanel and WHM?
WHM is the server administrator interface: it creates accounts, sets limits and manages services across the whole machine. cPanel is the per-account interface for managing one website’s files, databases, email and domains. Shared hosting customers get cPanel only; a server owner gets both.
Is cPanel free?
No. It is commercially licensed, and since 2019 pricing has been tiered by the number of accounts rather than flat per server. Shared hosting bundles the cost into your plan. On your own VPS it is a separate recurring charge that can approach or exceed the cost of the server for a small number of sites.
Do I need a control panel to run a website?
No. A control panel is a convenience layer over standard Linux services, and everything it does can be done directly or handled by a managed platform. It is most valuable when you administer sites for other people who need their own login, and least valuable for a single application deployed from a repository.
Why can I not find a setting a tutorial mentions?
Most likely because the setting is in WHM rather than cPanel, and your host controls WHM. Hosts can also hide individual cPanel features from the account package. If a feature is genuinely missing rather than hidden, ask your host, because it may be a plan limitation.
Can I move my site away from cPanel?
Yes, though the export is manual. Files come out over FTP or the file manager, databases through phpMyAdmin or a mysqldump, and email needs a mailbox-by-mailbox migration. The full-account backup archive is portable to another cPanel server but not to a platform that does not run cPanel.