cPanel pricing changed in 2019. Since then, reseller margins have been squeezed year after year. Here's how Enhance compares — from a host that actually operates both.
Let's start with what happened in 2019, because it explains why this comparison matters.
Before October 2019, cPanel licensing for resellers was priced on a per-server or tier basis. If you were an agency running a VPS with 30 client accounts, your licensing cost was relatively predictable and modest. Then cPanel changed their pricing model to charge per account — specifically, per cPanel account installed on the server, regardless of whether those accounts were active or generating revenue.
The new pricing structure meant a reseller with 100 accounts was suddenly paying significantly more for the same server. Resellers who had been running comfortable margins found themselves passing cost increases to clients, absorbing them, or looking at alternatives for the first time.
It forced a question many in the industry had avoided asking: is cPanel actually the best tool for the job, or is it just the one everyone learned?
We run both. Here is an honest account of what we've found.
cPanel's current pricing is account-tiered. As of 2024, you're looking at roughly $15/month for up to 5 accounts on a VPS, stepping up through tiers to $45/month for up to 30 accounts, $65/month for up to 50, and higher from there. If you're running a dedicated server for resellers, the DEDI licences are priced differently again.
A realistic scenario: you're an agency managing 50 client hosting accounts. On cPanel reseller hosting, you're paying — at current rates — somewhere in the $65/month range for the licence alone, plus your server or reseller plan costs. That's before you've added any margin.
Enhance uses a different model. The platform charges per server rather than per account. Hosting providers pass on a per-server cost, and the per-account economics improve as you add more accounts. FXRM's reseller plans using Enhance are priced based on the resources allocated to your reseller package — disk, RAM, CPU — not on how many accounts you create within it. You add a new client, spin up their account, and the account creation itself doesn't trigger a new per-account licensing charge.
For an agency with 50 accounts today and an expectation of growing to 80 over two years, the trajectory of costs under the two models is meaningfully different.
cPanel has been around since 1996. There is a generation of web developers, sysadmins, and support staff for whom cPanel is simply what hosting looks like. The WHM interface for resellers is dense — sometimes bewilderingly so — but it's familiar. When something goes wrong at 11pm, you know where to look. That familiarity has real value.
Enhance's interface is modern. It's cleaner, built with a contemporary design sensibility, and considerably easier to navigate for someone encountering it for the first time. The information architecture makes more sense — creating a website, setting up a domain, configuring PHP, managing databases — these flows are logical.
But if you've spent years in cPanel, Enhance will feel unfamiliar. Not bad. Not wrong. Just unfamiliar. You will click in the wrong places. You will look for features where they aren't. You will, for the first month or so, be slightly slower at routine tasks. That's a real cost in a business context, and it's worth acknowledging honestly.
In our experience, experienced developers adapt to Enhance relatively quickly — the underlying concepts are the same, only the location of the controls changes. The initial friction is genuine but it passes.
What doesn't pass: cPanel has a vast ecosystem of documentation, tutorials, YouTube walkthroughs, and community forum posts. "How do I do X in cPanel" returns useful answers from Stack Overflow, WHM documentation, and thousands of hosting provider knowledge bases. Enhance is newer, and while its own documentation is good, the breadth of third-party resources isn't there yet.
This is probably the most significant technical difference between the two platforms, and it matters most for agencies who automate anything.
cPanel's API is functional. It works. But it was built incrementally over 25+ years, layered onto a system that predates modern API design principles. There are multiple API versions (API1, API2, UAPI) with inconsistent conventions. Authentication has evolved in ways that left legacy approaches in place. The documentation is extensive but dense, and the response structures are not always consistent between endpoints.
If you've tried to build cPanel automation — provisioning accounts, configuring domains, setting up email through the API — you know what I mean. It can be done, but it requires working through idiosyncrasies that wouldn't exist in a purpose-built API.
Enhance was built API-first. The entire platform is driven by its own REST API, and the web interface is a consumer of that API rather than a parallel implementation. This means the API surface is complete, consistent, and well-documented. Everything you can do in the UI, you can do through the API. The authentication model is modern. The response structures are predictable JSON.
For an agency that wants to build a client portal, automate account provisioning, or integrate hosting management with their own tools, this difference is significant. The lift required to build against Enhance's API versus cPanel's is materially lower.
Standard cPanel shared hosting runs on a model where server resources — CPU, RAM, I/O — are shared between all accounts. Resource isolation exists but requires additional tooling: CloudLinux is the standard solution, and it works well, but it's an additional layer and an additional cost on top of cPanel licensing.
Enhance is built with container-based isolation as a native architectural choice rather than a bolt-on. Each website runs in its own isolated environment. CPU and RAM limits are set per account and enforced at the container level. One client's traffic spike, runaway PHP process, or poorly optimised query is less likely to affect their neighbours.
This matters most in reseller scenarios with varied client workloads. If you're managing 50 client accounts with different traffic patterns and different application quality, the isolation model affects how much one client's behaviour can damage another's experience.
Both platforms support standard email configuration: IMAP/POP3, SMTP, SPF, DKIM, DMARC, spam filtering. cPanel's email stack is mature — Exim as the MTA, Dovecot for IMAP, SpamAssassin for filtering. It's been in production use for decades.
The practical difference shows up in configuration workflow. Setting up DKIM in cPanel involves multiple steps across different sections of WHM and cPanel, and for resellers managing accounts for multiple clients, it requires doing this per account. Enhance provides more centralised control with a clearer workflow.
One area where shared infrastructure on either platform is a constraint: if you're on shared hosting, you share the sending IP. IP reputation affects all accounts on that IP. For clients where email deliverability is business-critical, dedicated sending infrastructure matters regardless of which control panel you're running.
I want to be direct here because this is a comparison of two platforms we operate, not a sales pitch for one of them.
cPanel's ecosystem advantage is real and should not be understated. Thousands of hosts, millions of installations, decades of community knowledge. WHM certification exists. Staff who have worked at any hosting company for more than three years can almost certainly work in WHM without training.
cPanel's integrations are extensive. Softaculous for one-click application installs, Jetbackup, Imunify360, KernelCare — there is a mature third-party ecosystem built specifically for cPanel. Some of these have Enhance equivalents, some don't yet.
cPanel is also the safer choice for migrations. Moving a client from another cPanel host to a cPanel server is a supported, documented process. Migrating from cPanel to Enhance requires more manual work — there is no automated account migration tool that handles the full transfer including email, databases, and configuration. If you're considering switching, factor in migration time. For a small number of accounts, the overhead is manageable. For a large reseller with complex client setups, it's a material project.
Enhance makes the most sense for agencies and freelancers who:
cPanel remains the right choice for teams where:
cPanel changed its pricing in 2019 and the industry has been adapting ever since. Enhance isn't perfect — the ecosystem is younger, migration tooling is less mature, and you will spend a few weeks recalibrating where things live in the interface. Those are real costs.
But for agencies growing their client base, for developers who want to automate provisioning through a clean API, and for anyone evaluating the long-term cost trajectory of managing 50, 80, or 100+ client accounts, the economics and architecture of Enhance are worth understanding.
We run both because our clients have different needs. But for new reseller accounts where you're starting from scratch and planning for growth, we consistently recommend looking at Enhance-based reseller hosting.
If you're at the point where per-account cPanel costs are eating into your margins, or you're rebuilding your agency's hosting infrastructure and want to do it on a platform with a cleaner long-term cost model, FXRM's reseller hosting plans run on Enhance. We're happy to talk through whether the migration overhead makes sense for your situation before you commit to anything.
Founded by Jon Morby, whose team has been running UK servers since 1992. Hosting built by engineers who care about deliverability and uptime.
Get in touch →cPanel's 2019 per-account pricing change quietly restructured the economics of web agency hosting. Five years on, the cumulative effect is reshaping which platforms agencies actually choose.