BETANot production ready yet. Testers wanted: apply · report a bug
KarnakPanel
Compare panels / For resellers

cPanel alternative for resellers: price it per server, not per client.

If you sell hosting, per-account licensing turns every new customer into a small tax. This page is the arithmetic first, then what a self-hosted panel has to do to genuinely replace WHM — packages, white-label nameservers, billing and all — and the parts where cPanel is still the better answer.

The bill

What per-account pricing does to a reseller.

cPanel's list prices from 16 December 2026, before any host markup. The tier price is not the whole bill: accounts above Premier's included 100 are charged individually, and that per-account rate rises from $0.49 to $0.55 on the same date.

TierList price, from 16 Dec 2026What it changes for you
Solo$32.99 / monthOne account. Fine as a personal box, useless as a reseller model.
Admin$38.99 / monthA handful of accounts. Where most small hosts start, and where the ladder begins.
Pro$58.99 / monthThe tier most reseller servers sit on, until they outgrow it.
Premier$76.99 / monthIncludes 100 accounts, then $0.55 each. This is the tier that scales with your customer count.

A 500-account server goes from $265.99 to $296.99 a month on this round alone. WHMCS is separate and also rising: the entry tier is $34.95 in 2026, with 11–20% added from January 2027. The full pricing page has the history and the worked examples.

What the alternative actually costs. KarnakPanel is $0 per server — no per-account fee, no licence server, every module included. Your real costs are the VPS and your own time: support, backups and anti-spam are yours either way, but there is no invoice that grows because a customer grew.
The comparison

What replaces WHM, item by item.

Written as a checklist rather than a feature list, because most of these are the reason a reseller cannot simply install a panel and start selling.

In WHMHereThe difference that matters
Packages with account limitsAdmin, reseller and user roles; packages with enforced disk, bandwidth, mail and site limitsLimits are enforced by the panel, not by policy. Over-bandwidth auto-suspends.
Create, suspend, terminate clientsThe same, plus one-click plan changesPlan changes are allocation-capped and downgrade-guarded, so a reseller cannot hand out more than they were given.
Reseller brandingPanel name, logo, accent colour, support link and emailApplies to the reseller's panel and to their clients' view of it.
Private nameserversEach reseller gets their own ns1/ns2 names for their clients' zonesTheir domains do not have to point at your brand.
Login as clientLogin-as, fully loggedSupport without asking for a password, and an entry in the log for every use.
Billing automationWHMCS module with a five-minute setup guide; REST and provisioning APIs with scoped, expiring, IP-pinned tokens; HostBMS module in early developmentAccount creation is an API call, so the same billing system you use now can keep doing it.
Client isolationSeparate system user per account, PHP 8.3–8.5 per account, per-account cron and mailOne customer's runaway script does not take the box with it.
MigrationImport from cPanel by backup, API token or root SSH; Account Transfer between two KarnakPanel serversOne account or a whole book, without cPanel's per-account tooling.
Honestly

Where cPanel is still the right answer.

This page argues for a different panel, so the case against it belongs here rather than in the footer.

  • Your customers' contracts name cPanel. If a client bought "cPanel hosting", moving them is a commercial conversation, not a technical one. The licence you stop paying is the feature they think they bought.
  • You need the plugin ecosystem. cPanel has fifteen years of third-party add-ons — spam filtering, backup targets, security scanners, billing modules — with companies behind them. A young panel has the core and not the long tail.
  • Your staff were trained on it. cPanel University, the documentation and the muscle memory in this industry are real. Retraining a support team is a cost that does not appear on any licence invoice.
  • You sell cPanel licences yourself. Reselling licences is a revenue line for some hosts; that is a different business, and this panel cannot give it to you.
  • You need a support contract. There is no phone number here. Support is the bug tracker, the docs and the person who wrote it.
The honest middle. Most hosts who leave run both for a while: new customers on the cheap server, legacy customers where their contract says cPanel. Nothing here forces an all-or-nothing switch, and the import runs one account at a time precisely so you can stop halfway without a mess.
The move

Bringing a book of clients across.

The order that keeps the invoices going out while the sites move.

A reseller is not a list of accounts, it is a branch: one owner, their packages, their nameservers, their clients and their support address. Import the branch as a unit or you will spend the week reconciling which client belongs to whom. Decide up front whether the reseller keeps their own billing system or moves onto yours; both work, but the answer changes the order of the steps below, and changing it halfway is how a customer ends up suspended for an invoice nobody raised.

  • Map packages before accounts. cPanel packages rarely translate one-to-one. Decide what each one becomes here — disk, bandwidth, mail and site counts — then import into that, not into the default.
  • Move one reseller, not one account. Pick a reseller with a handful of clients and move the whole branch. You will learn more from their support tickets than from ten test imports that all went well.
  • Keep the billing system pointed at the old API until the last account lands. The WHMCS module can be configured while the old server still provisions; switch it after the final import, not during.
  • Take the nameservers seriously. Reseller-branded ns1/ns2 means registrar changes at their end, not yours. Tell them what to set before the day, or their clients will be the ones who notice.
  • Leave the old server running. A month of overlap costs less than one botched weekend, and the import never deletes anything from the source.
Limits

What this is not.

Stated before you build a business on it.

Not production-ready yet. It is in public beta. Import a reseller's test branch before you import a customer who pays you.
No licence resale. There is nothing to resell. That is the point, and it is also a revenue line you lose.
One server at a time. No clustering, no central console for a fleet. A big book means several boxes and your own bookkeeping.
Ubuntu 24.04 and Debian 13 only. If your fleet is on older releases, that is a rebuild, not an import.
The long tail is missing. Core hosting, mail, DNS, backup and billing are here; the hundred niche add-ons are not.
Beta support. The bug tracker and the documentation are the support contract.
Questions

What resellers ask first.

Short answers.

Can my resellers bill their own clients?

The panel provisions accounts; it does not invoice anyone. Your resellers bring a billing system, or use yours. The WHMCS module and the provisioning API are how that connection is made, and the HostBMS module is in early development.

How many accounts fit on one server?

There is no licence ceiling, so the limit is memory, disk and PHP workers. A 2 GB box is the documented minimum for the panel itself; a reseller server is a capacity decision, not a licensing one.

Do my clients see KarnakPanel branding?

Your resellers can set the panel name, logo, accent colour and support links, and their clients' zones can sit on the reseller's own nameservers. The panel is not white-label at the code level — the branding is configuration, not a rebrand you can resell as your own product.