The Reseller Stack
WHM — Where You Actually Run the Hosting Company
Everything that makes forty client accounts manageable happens on one screen your clients will never open.
Straight answer first
WHM is the administrative deck above cPanel: where you create client accounts, define the packages they receive, set quotas, suspend for non-payment and hold platform-wide settings such as nameservers. It is the difference between having clients and running a hosting operation.
The work that pays off is done once. Build two or three packages properly and every new client becomes thirty seconds of typing, with the limits, the isolation and the branding applied automatically rather than remembered by hand each time.
Written by the Hosting Seller staff · Checked 24 August 2026
100+
Terms an admin needs
2 min
Between client calls
Plain
Speaking on both sides
24/7
Cover while you sleep
A cPanel account runs one customer's world. WHM runs the accounts themselves: creating them, suspending them, setting quotas, building packages, and holding the settings that apply across everything you sell.
That split is the reseller business model expressed in software. WHM for you, a separate cPanel for each of your customers, and a clean line between the two that nobody can cross by accident.
Packages: build once, sell for years
A package is a saved set of limits with a name on it: disk, bandwidth, mailboxes, databases, addon domains. Build a Starter package once at 10 GB and five mailboxes, then drop each new client into it in about thirty seconds, with the limits and the isolation applied automatically.
Two or three packages is the right number. One is too blunt to price against, and six becomes a table nobody can remember alongside a support answer that starts with you checking which plan somebody is actually on.
Quotas, suspensions and the awkward month
Suspension is a commercial tool, so decide the policy before you need it. How many days after an invoice, what the suspended page says, and whether mail keeps flowing while the site does not. Writing that down turns an uncomfortable decision into a procedure you can follow calmly.
Because accounts are separate, suspending one client touches nothing else. That is the single strongest operational reason to keep one client per account, and the reason the alternative goes badly the first time somebody stops paying you.
The settings that apply to everything
Nameservers, branding, the default package, backup behaviour and the resource ceilings your packages draw from all live at this level. Get them right before client one, because changing a nameserver after fifty accounts means a DNS edit on fifty separate domains.
Your clients never open this screen. A standard hosting account gives them cPanel and nothing above it, which is exactly the boundary you want: full control on your side of the line, and no visibility at all on theirs.
What to automate next
WHM creates and controls the accounts; billing software gives it instructions over an API. Once orders, invoices and suspensions run themselves, adding a client stops adding admin to your evening, and that is the point where the business scales rather than merely grows.
Reseller plans here are ready to wire into WHMCS billing whenever you are. Until then WHM alone is perfectly workable, because it is the manual version of the same loop and worth understanding properly before you automate it.
The deck your clients never see
Everything in this file is written from the administrator's side of the line: what you configure once, what you repeat per client, and what should never be visible from a cPanel login.
A 99.9% uptime target sits behind every account you create, watched by monitoring day and night.
- Package design, done once and reused
- Suspension policy written in advance
- Platform settings that must precede client one
- The automation step that follows
Why Hosting Seller
On every plan, as standard
Thirty seconds per client
A saved package applies quotas, isolation and branding automatically, so onboarding stops being a checklist you work through.
A suspension policy, not a decision
Days, wording and what happens to mail, agreed calmly before the first invoice goes unpaid.
Isolation that means something
Separate accounts mean suspending one client is completely invisible to the other thirty-nine.
Settings in the right order
Nameservers and branding before client one, because retrofitting either is a change on every domain you have sold.
Invisible to the client
A standard account sees cPanel and nothing above it, which keeps the administrative layer entirely yours.
Ready to automate
The same loop can be driven by billing software over an API when the manual version stops being worth your evenings.
First Steps
From choosing to live
- 1
Design two or three packages, then stop
Enough to price against, few enough to remember. Name them for what a client receives rather than for the internal quota.
- 2
Write the suspension procedure down
Days after the invoice, the wording on the page, and whether mail keeps flowing. Decide it calmly now and apply it consistently later.
- 3
Fix the platform settings before client one
Nameservers, branding and defaults. These are the settings whose cost multiplies by every account you have already sold.
In the Box
Packed with every plan
- WHM for you, and a cPanel of their own for every client
- Packages you build, name and price yourself
- You set the limits every client account receives
- Overselling switched on from the start
- Private nameservers running under your own brand
- Suspend or restore one account without touching the rest
- A backup of every client account, taken daily
- Imunify360 on guard on every client site
- Ready to wire into WHMCS billing whenever you are
- Real people to escalate to, for you and for them
Across the Counter
Things people ask us all the time
How many packages should I build in WHM?
Two or three. One is too blunt to price against and six produces a table nobody remembers, yourself included. Name them for what the client receives rather than for the internal quota, and resist building a bespoke package for the client who asked nicely, because that is how a price list turns into archaeology.
Do my clients ever see WHM?
No. A standard hosting account gives them cPanel and nothing above it. WHM appears once somebody buys reseller hosting or a server of their own, which is the difference between renting a unit and managing the whole parade of shops.
What should my suspension policy look like?
Written, and decided before you need it. A number of days after the invoice, an explicit page the visitor sees, and a decision about whether mail keeps flowing while the site does not. Because accounts are separate, suspending one client is invisible to everybody else, which is what makes the policy enforceable at all.
When should billing software take over from WHM?
Around the point where invoicing and provisioning by hand pass an hour or two a month. WHM creates and controls the accounts, while billing software instructs it over an API and handles orders, invoices and overdue suspensions. Reseller plans here are ready to wire into WHMCS whenever that admin stops being worth your evenings.
Read next
Domain Names
Client domains registered and renewed alongside the accounts they point at.
VPS Hosting
Root access for the client whose requirements have outgrown anything a package can express.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Run it from one screen.
WHM, packages you name yourself, overselling from the start, and private nameservers under your own brand.
See Domain Names plans