Panel & Tooling
WHM: the tier where account limits are decided
You are choosing numbers for a package template, and those numbers become somebody else's page load times.
The short answer
WHM is the server-level panel above cPanel: it creates and suspends accounts, defines package templates, sets per-account resource limits, manages nameservers and applies policy across the whole machine. cPanel administers one account; WHM administers all of them.
The screen that matters most is the package editor. Disk, bandwidth, addon domains and databases are the numbers clients read, while entry processes, concurrent connections and memory are the numbers that decide whether their sites feel quick under load.
You meet WHM when you buy reseller hosting or a server of your own; a standard hosting plan gives you cPanel and nothing above it.
By the HostingFast team · Reviewed 12 August 2026
100+
Terms defined here
2 min
Typical read time
Plain
English, no hand-waving
24/7
Engineers on shift
Think of it as the boundary control for the machine. Each account gets its own filesystem, its own database user, its own quota and its own ceilings, and WHM is where those ceilings are written. Nothing inside a cPanel account can cross into another, and the isolation is enforced below the panel rather than by it.
Server-wide settings live here too: nameserver configuration, the PHP releases available to accounts, the default PHP version for new sites, feature lists that decide which cPanel icons a client can see, and account suspension. Most of a reseller's operational life is four screens in this panel.
The package editor, field by field
Disk quota and bandwidth are self-explanatory and rarely the constraint. Addon domains and databases decide how many sites and applications an account can carry. The interesting fields are the resource limits: entry processes, concurrent connections and memory, which together decide what happens when a client's site meets real traffic.
Set those too tight and clients get intermittent errors under perfectly ordinary load, which arrive at your inbox as complaints about the host. Set them with headroom and monitor consumption instead — a limit you can raise after measuring beats a limit you guessed at.
Defaults are the only settings that scale
Set the default PHP release for new accounts to a current 8.x branch, enable the server cache in the package, and leave image optimisation on. Anything you plan to configure per account after creation will end up configured on some of them and forgotten on the rest.
Feature lists are worth ten minutes as well. Hiding the panel tools a client will never use makes their cPanel less intimidating and cuts the number of tickets that begin with the words I clicked something.
Where WHM ends and WHMCS begins
WHM creates and controls accounts. WHMCS handles the commerce around them: orders, invoices, payment, automatic suspension and termination. WHMCS instructs WHM over an API, which is how an order placed at midnight becomes a live account before breakfast without anyone being awake.
Keep the boundary clear in your own head when something breaks. An account that exists but is not billed is a WHMCS problem; an account that is billed but never provisioned is usually an API credential or a package name that does not match.
WHM on our reseller tiers
Every reseller plan gives you WHM with a private cPanel for each client, private nameservers on your own domain, overselling enabled from day one, per-client limits you define, packages you name yourself, Softaculous in each account, free SSL on every site and daily backups across the estate. Reseller 1 is the entry tier, priced as a plan fee plus a charge per active user.
Underneath, every client account sits on NVMe behind a LiteSpeed cache with Imunify360 in front. Read Reseller Hosting, cPanel and WHMCS next.
The package editor is the important screen
Most WHM guides walk through every menu. This one concentrates on the handful of fields that change how client sites behave, and on the defaults that decide what happens on the accounts you forget to revisit.
Accounts are ready to wire straight into WHMCS billing, so provisioning can run without you being at the keyboard.
- Resource limits, explained by symptom
- Defaults over per-account fiddling
- Feature lists to cut tickets
- The WHM and WHMCS boundary
Why HostingFast
Standard on every plan
WHM on every reseller tier
Full account administration with a separate, isolated cPanel for each client you create.
Limits you set yourself
Disk, bandwidth, databases, processes and memory per package, revisable once you have measured real consumption.
Private nameservers
Delegation on your own domain, so the platform underneath your accounts stays out of the client's view.
Overselling from day one
Enabled by default, with the resource visibility you need to keep the assumption behind it honest.
Imunify360 across the estate
Server-level scanning and shielding on every client account rather than a plugin per site.
Daily backups for every account
The whole estate is backed up daily, so a client mistake is a restore rather than an incident.
Quick Start
From order to online
- 1
Write the package before the first client
Two templates, one light and one heavy, with process and memory limits set from measured use rather than instinct.
- 2
Fix the defaults for new accounts
Current PHP 8.x, server cache enabled, image optimisation on. Defaults apply everywhere; intentions apply to some.
- 3
Wire provisioning to billing
Connect WHMCS over the API and place a test order end to end, so the first real one at midnight is not the first attempt.
Built In
Loaded onto every plan
- WHM for you, an isolated cPanel for each client
- Package templates you define and name yourself
- Per-account entry process, memory and connection limits
- Private nameservers carrying your own brand
- Overselling enabled from day one
- Feature lists controlling what each client sees
- Softaculous inside every account you create
- Free SSL on every site you host
- Daily backups across every client account
- NVMe storage behind a LiteSpeed cache throughout
Frequently Asked
What people ask us most often
Which package limit causes the most confusing failures?
Entry processes. Disk and bandwidth failures announce themselves in plain language, but a process ceiling produces a site that works all day and stalls during a modest burst. If clients report intermittent errors that you cannot reproduce, that limit is the first place to look.
Will a normal hosting customer ever see WHM?
No. A standard plan provides cPanel and nothing above it. WHM appears when you buy reseller hosting or a server, which is the step from living in one account to administering many of them.
How do WHM and WHMCS actually divide the work?
WHM owns the accounts: creation, suspension, limits, nameservers. WHMCS owns the commerce: orders, invoices, payment, dunning and termination, and it instructs WHM over an API. When provisioning fails, the cause is nearly always an API credential or a package name mismatch between the two.
Can I change a package after clients are on it?
Yes, and you should once you have a fortnight of real consumption data. Editing the package applies the new limits to the accounts using it, which is exactly why guessing generously at the start and tightening later is safer than the reverse.
Keep reading
cPanel
The per-account panel your clients see, and the screens they will open in their first week.
Reseller Hosting
Buying capacity wholesale and selling it on, from the resource-limit side rather than the sales pitch.
How to Upload Files With File Manager
Uploading files with the panel's file manager, step by step, including the snags.
Domain Names
Find, register or transfer names, with the first year included on an annual hosting plan.
VPS Hosting
KVM virtual servers with full root, DDoS filtering and a flat monthly price.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Set the limits, keep the clients quick.
WHM with private nameservers, per-client limits you define, and NVMe behind LiteSpeed on every client account.
View Domain Names plans