The 2026 cPanel price increase, and what to do about it

Every January, cPanel publishes new list prices, and every January the same question goes round the hosting forums: is this the year to move?

Provibr supports cPanel as a live integration. A customer running cPanel and a customer running DirectAdmin pay us exactly the same, so we have nothing to sell you here beyond an accurate answer. This page is the arithmetic, the two numbers we could not stand behind, and the four routes available to you, including staying.

What changed on 1 January 2026

These are the self-managed (non-cloud) list prices.

The cloud tiers moved further. Pro Cloud went from $27.25 to $32.00, roughly 17%, and the per-account overage from $0.30 to $0.35, also roughly 17%.

The increase is not uniform. Premier's base moved least in percentage terms and Pro moved most. The per-account rate above 100 accounts rose faster than the base it attaches to, which is the line that determines what a growing host pays.

What that does to your bill

Take one server on Premier, list price, no volume discount, and vary the number of accounts on it.

That is arithmetic on published list prices, not a quote. Two honest caveats apply to every row of it. cPanel negotiates at volume and a busy host will not be paying list. And these are per-server figures: a fleet of ten servers at 250 accounts each pays ten times the 250-account row, not the 2,500 row.

The number that matters for a hosting business is not the total. It is $0.49 per account per month, or $5.88 per account per year, because that is the figure you compare against what you charge. On a €3/month shared plan, the panel licence is now roughly 15% of revenue before you have paid for hardware, bandwidth, support or your own time.

The surcharge that is not part of this increase

You will see the Extended Lifecycle Support charge mentioned in the same breath as the January prices. It is a real cost and it belongs in your budget, but it is not part of the 2026 increase: cPanel introduced ELS pricing in 2024, for customers still running end-of-life operating systems. Adding it on top of the January percentages double-counts.

It is framed as optional (migrate off the old OS and it goes away), and that framing is fair. It is also not a weekend's work on a dense shared-hosting fleet. If you are still on an older CentOS build, budget for both, and count the OS migration as a project rather than a task.

Two numbers we could not stand behind

This section exists because we went looking for the figures that circulate about cPanel pricing, and two of them did not survive being checked.

"55% more expensive than before 2019": we could not support this. cPanel restructured in 2019 from flat-rate unlimited licensing to account-based pricing. That is not a price change on a comparable product; it is a different product shape. What a specific host pays before and after depends entirely on how many accounts they had, and for a large flat-rate customer the increase was far more than 55% while for a small one it could be nothing at all. There is no single honest percentage, so we are not quoting one.

"Pro went up 17%": that is two different products. Self-managed Pro went from $46.99 to $53.99, which is 14.9%. The ~17% figure is Pro Cloud, $27.25 to $32.00. Both are true; they are not the same tier, and quoting the higher one against the self-managed name overstates the increase for most readers.

What we can support without qualification: a Premier licence covering about 100 accounts sat around $54 to $55 in 2021 and lists at $69.99 in 2026, and increases have been roughly annual since the 2019 restructure.

Four routes, and what each really costs

Absorb it. At 100 accounts this is $48 a year. If the licence is not yet a visible line on your P&L, doing nothing is a legitimate answer, and every hour you do not spend on a migration is an hour spent on something that earns. Revisit next January.

Raise your prices. $0.49 per account is €0.45-ish; a €0.50 increase on a €3 plan covers it with room over. The cost here is not money, it is churn risk and the support conversations that come with a price letter. Most hosts who take this route discover the increase was never the hard part.

Move the price-sensitive accounts only. Your cheapest plans carry the worst licence-to-revenue ratio, and they are usually also the accounts whose customers care least what the panel looks like. Moving the bottom tier to a panel with a flat or absent licence fee, and leaving everything else where it is, gets most of the saving for a fraction of the disruption. The cost is that you now run two panels; see below.

Move everything. The largest saving and the largest project. Worth it when the licence is genuinely one of your top costs, or when the trajectory rather than the level is the problem: if your cPanel bill grows faster than your revenue per account, each January makes the crossing point arrive sooner. It is not worth it as a reaction to a single increase.

Before you decide, check whether your quotas are enforced at all

This is the least-known thing on this page and it can change your maths, so it goes here rather than in a footnote.

A cPanel server only enforces disk quotas when the filesystem the accounts live on carries quota support. Without it, WHM accepts the package, accepts the number, and enforces nothing. We measured this on a running WHM 11.136 server: moving an account onto a package with a 2 GB quota left the account still reporting its limit as unlimited, and the per-account disk figures came back empty. Nothing failed. Nothing was refused. The number in that package simply meant nothing on that machine.

If you sell disk-limited plans, that is the difference between overselling within a known ratio and overselling nothing at all. It also changes what a migration costs you: move that fleet to a panel that does enforce the quota you configured, and every account that had quietly grown past its limit hits it in the same week. That is a support wave, and it is much better to discover it now than halfway through the move.

Provibr's connection test reports this. It reads the accounts on the server and says whether their quotas are actually being enforced, next to the WHM version and the counts. On a server with no accounts there is nothing to measure and it says so rather than guessing. It is also why the platform reads an account's disk limit from the account rather than from the package: what the account reports is what is in force, and the number in the package is what somebody intended.

The real cost of moving is the months in the middle

Nobody moves a hosting fleet in a weekend. You move it in cohorts, over months, and during that stretch you operate two panels: two logins, two ways of counting what you sold, two places to look when a customer calls, and two sets of automation that have to agree about who is suspended. That period is what makes hosts stay on a panel they have already decided to leave, and it is worth pricing honestly before you commit.

Provibr connects both panels to the same account. A cPanel account and a DirectAdmin account appear in the same server list, count towards the same capacity, and land on the same monthly invoice, with the same suspend, resume, repackage and delete actions behind them. The agent dials outward from your own network, so neither server needs an inbound port opened and nothing is installed on either. Accounts you did not create through Provibr are left alone until you import them, which turns "move a panel across" into adopting what is already running.

That does not make the decision for you. It does mean the months in the middle stop being the reason not to make it.

Read next

• cPanel alternatives for hosting providers: the panels we run, on licence cost, migration effort and what your customer notices.
• DirectAdmin vs cPanel: the 2026 numbers: head to head, with the cost curve per account.
• cPanel and WHM setup: the API token, the username rule, and when a disk quota is actually enforced.

cPanel 2026 list prices and their 2025 predecessors are from public reporting of the pricing announcement effective 1 January 2026. The ELS surcharge dates from 2024. Everything described about WHM's API behaviour was measured against a running WHM 11.136 server while building the Provibr integration.