Account Structure
Hosting for multiple websites — The structural decision that decides everything else
Twelve sites inside one hosting account is either a sensible economy or a professional liability, and the only thing that decides which is who owns them.
Straight answer first
Put your own projects wherever you like — the Pro shelf at $4.66/mo carries 25 sites on one account — but give every client site its own cPanel account, because shared accounts fail together, bill together and cannot be handed over separately.
This page is the structural argument rather than a plan comparison: what actually happens when a shared account is compromised or suspended, what separate accounts cost you, how the billing follows the structure, and the exit that only one of these two arrangements survives.
Written by the Hosting Seller staff · Checked 24 August 2026
99.9%
Target across every account
24/7
Cover for the whole book
Free
SSL on every site you host
NVMe
Disks under all of them
Multi-site economics favour the quiet many. A typical collection is one busy site and nine dozing ones, and a shared allocation absorbs that shape without breaking sweat — which is exactly why piling sites into one account is so tempting and so cheap.
The temptation is correct for your own work and wrong for anybody else's. Launch carries 1 website at $2.42/mo, Pro carries 25 at $4.66/mo and Elite carries 100 at $7.08/mo; Business Standard at $19.99/mo allows 100 addon domains. Reseller plans start at $14.99/mo plus $0.40 per active user and give each client an account of their own. The price difference is small. The structural difference is not.
What happens the day one site is compromised
Inside a single cPanel account, every site shares a filesystem and a user. A vulnerable plugin on the least important site gives an attacker read and write access to the document roots of every other site in the account, including the one belonging to your best client. There is no boundary to cross because there was never a boundary.
Separate accounts change that completely. Each client has their own account, their own limits and their own backups, so one customer's mess stays that customer's own. Imunify360 stands on guard on every client site and ImunifyAV+ watches for malware, but the isolation is the part that decides how bad a bad day gets.
The same applies to suspension. If an account is suspended — non-payment, abuse, a resource incident — everything inside it goes down together. On a shared account that means every client you have parked there is offline simultaneously, for a reason that has nothing to do with any of them. That is the scenario that ends agencies.
What separate accounts actually cost you
Very little. On Reseller 1 at $14.99/mo, the marginal cost of one more client account is $0.40 per active user. Twenty clients is $22.99 a month all in, which is less than the difference between two shelves of shared hosting and buys you a structure that survives contact with reality.
The real cost is administrative, and it is front-loaded: building packages in WHM, setting up private nameservers, writing a welcome email, deciding the feature list. Do that once and every subsequent account is a two-minute operation. Improvise it per client and it is a fifteen-minute operation forty times over.
The resource question that people worry about is not really a question. Sites sit idle for most of the day, so the allocation follows total traffic rather than headcount, and overselling is enabled from the start precisely because of that. Twenty separate accounts do not consume twenty times what one does.
How the billing follows the structure
One account with twelve sites in it produces one invoice from your supplier and no natural way to attribute cost to a client. That sounds like a bookkeeping detail until you try to work out which clients are profitable, or until one of them asks what exactly they are paying for.
Separate accounts give you a per-client cost line whether or not you use billing software, and they make the eventual move to automated billing straightforward — the reseller plans are ready to wire into WHMCS, and a licence is resold here at $6.99/mo when manual invoicing stops scaling. Somewhere past ten accounts, the cost of manual billing shows up as missed renewals rather than as time.
It also settles the awkward question of what happens when a client stops paying. With their own account, you suspend theirs and nobody else notices. Inside a shared account, you have no mechanism at all short of deleting files, which is not a business process anybody wants to be running.
The exit only one structure survives
Every client relationship ends. With a separate cPanel account, ending it is a full backup handed over, which restores onto any cPanel host anywhere, and a domain that was registered in the client's name transferring away once the registry's usual 60-day lock has passed. The whole thing is an email and twenty minutes.
With a shared account, extracting one site means picking files out of a document root, exporting one database from among a dozen, untangling mailboxes and hoping nothing was shared between sites. It is a manual job, it takes hours, and you will be doing it in a week where the relationship has already soured. Some agencies simply refuse, which is the reputational disaster this whole page exists to prevent.
Doing this well is not charity. A tidy exit in a small industry is the most reliable source of referrals a hosting reseller has, and the structure that makes it tidy costs forty cents a month per client.
Your own projects are a different question
For sites you own outright, one account with an allowance is genuinely the sensible economy — Pro carries 25 sites at $4.66/mo and Elite carries 100 at $7.08/mo, and a broken experiment of yours is only ever your own problem.
The rule is simply ownership. As soon as a site belongs to somebody who pays you, it belongs in an account of its own.
- One account per client, without exception
- Your own projects can share a shelf
- Per-account limits, backups and certificates
- $0.40 per active user for the separation
Why Hosting Seller
On every plan, as standard
One compromise stays one compromise
Separate accounts mean a vulnerable plugin on the smallest site cannot reach your best client's document root.
Suspension without collateral
A non-paying client can be suspended from WHM without any other site on your book noticing.
A per-client cost line
Forty cents per active user, attributable, which is what makes profitability per client a question you can actually answer.
Backups that mean something
Each account has its own backup, so restoring one client's mistake never touches anybody else's site.
A handover that takes twenty minutes
A standard full backup restores onto any cPanel host, which turns the end of a relationship into an email.
Room for your own work too
Pro at $4.66/mo carries 25 sites and Elite at $7.08/mo carries 100 for the projects you own outright.
Price Tags Compared
How we compare with the household names
Typical sign-up and renewal prices across the market, set next to ours — the second number most comparison charts leave off.
| Line item | Hosting SellerBest seller | Typical big-brand host | Typical budget host | Typical loss-leader |
|---|---|---|---|---|
| Entry price / mo* | $2.42/mo | $4–$6 | $2–$4 | $1–$3 |
| Price at renewal / mo | $2.42/mo | $10–$15 | $8–$12 | $4–$6 |
| Renewal price on the entry plan is unchanged | ||||
| SSL on every plan | ||||
| Site migration included | ||||
| The entry plan uses NVMe storage | ||||
| Entry plan gets a backup daily | ||||
| Live human support, 24/7 |
*The number in our column is the cheapest plan on our shelf, priced on an annual term and pulled live from the very catalogue that feeds the pricing page, so it cannot drift out of date. Other columns show the ranges shared hosting tends to advertise inside each bracket: introductory rates that normally ask for a one-to-four-year commitment, then climb once that term expires. Naming individual competitors and printing their prices is something we have stopped doing. A figure we cannot re-check on the day you read it has no business sitting in front of you. So compare us with whoever you are genuinely weighing up, and read the renewal line first. That line tells you more than the headline ever will.
First Steps
From choosing to live
- 1
Apply the ownership test to every site
If somebody else pays for it, it gets its own account. If you own it outright, it can share a shelf with your other projects.
- 2
Build the packages before the migration
Disk, mailboxes, databases and feature list decided once in WHM, so creating each new account is two minutes rather than fifteen.
- 3
Untangle any existing shared account now
Doing it calmly this quarter is a job; doing it during a dispute or an incident is a crisis with an audience.
- 4
Test one full handover end to end
Back up a test account, restore it somewhere else, and confirm the procedure works before a real client asks for it.
In the Box
Packed with every plan
- Every client site in its own cPanel account
- Your own projects consolidated on a shelf with an allowance
- Per-account disk, mailbox and database limits set
- Separate backups verified per client account
- Client domains registered in the client's own name
- A suspension procedure that affects only one account
- Per-client cost attributable from your supplier invoice
- Imunify360 active on every client account
- A tested full-account backup and restore procedure
- Any legacy shared account scheduled for untangling
Across the Counter
Things people ask us all the time
Is it ever acceptable to put two clients in one account?
No, and the reasons are structural rather than technical. They fail together when one is compromised, they go down together when the account is suspended, they cannot be billed separately with any accuracy, and neither can be handed over without extracting them by hand. At $0.40 per active user the separation is close to free, and it is the single decision that most distinguishes a professional reseller from a hobbyist.
What about a client with several sites of their own?
One account per client, with an allowance inside it, is usually right — their marketing site, their landing pages and their staging copy can share a filesystem because they share an owner. If two of those sites have genuinely different risk profiles, a trading shop and a brochure site say, splitting them is defensible. The test remains ownership, applied one level down.
How do I untangle a shared account I have already built?
One site at a time, in a quiet week. Create the new account, copy the files and export the database, check it on a temporary URL, move the mailboxes, then change DNS. Free migration is available if you would rather hand the job over. What matters is doing it before you need to rather than during a dispute, because the version done under pressure is the one that goes wrong.
Do separate accounts use more of my allotment?
Marginally, and less than people fear. Sites are idle most of the time, so the allocation follows traffic rather than headcount, and overselling is enabled from the start on that basis. What separate accounts do consume is a small fixed overhead each — a mail configuration, a certificate, a backup — which is a fair price for the isolation and is why the per-user charge exists at all.
Where does my own portfolio site belong?
On its own account, treated exactly like a client's. It is the site that sells your business, it has different uptime consequences from anything else you host, and putting it inside a client account or an experimental one is the version of this mistake that agencies make most often. Give it the same separation you sell.
Read next
Email Hosting for Small Business
The mailbox side of a reseller's book, and why it produces more tickets than every website you carry combined.
Hosting With 24/7 Human Support
What round-the-clock cover behind your own desk actually lets you promise a client in writing.
Web Hosting
cPanel accounts on NVMe with SSL, migration and year-one domain — the shelf most client packages are modelled on.
Website Builder
Drag, drop and publish on quick hosting, for the client who would rather assemble it than commission it.
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.
One account each, from the start.
Reseller plans from $14.99/mo plus $0.40 per active user, with per-account limits, backups and certificates for every client.
See Web Hosting plans