Operator's Brief
Addon domains vs separate accounts — Shared fate: what an addon domain costs when the site is not yours
Eleven client sites are sitting on one hosting account because it was convenient in 2023, and you are now working out how exposed that actually leaves you.
Straight answer first
Give every client site its own account the moment somebody other than you owns it, because addon domains share one filesystem, one resource allocation and one suspension — and shared fate between sites with different owners is a business risk, not a tidy-up job.
For your own low-stakes properties, addon domains are fine and always have been. The line is ownership. Once a site belongs to a paying client, everything that happens to any neighbouring site happens to theirs, and you will be the one explaining why.
Written by the Hosting Seller staff · Checked 24 August 2026
24/7
Cover behind your desk
1-click
Installs for repeat builds
Free
Certificates on every site
Daily
Backups across client accounts
This starts as a cost decision and becomes a liability decision without anybody noticing the transition. One account holding several sites is cheaper and simpler, right up to the first incident.
Work through the three events that eventually happen to every hosting account — a compromise, a resource ceiling and a client leaving — and the answer becomes obvious. Each of them behaves completely differently depending on whether the sites are separated.
Whose site is it, and what happens when one of them falls over
Addon domains live inside a single account. That means one filesystem, one set of credentials and one suspension: if any site on the account is compromised or breaches a limit, the account is the unit that gets acted upon, and every site on it goes quiet at once.
Picture the conversation. One client's outdated plugin invites malware; ten other clients' sites are offline while it is cleaned. Those ten clients did nothing wrong, are not interested in the explanation, and one of them will tell the others to leave.
Separate accounts turn that into a contained incident. One client site down, cleaned, restored, and nobody else ever knows. Imunify360 watching each client site individually is only useful if the accounts are individual too.
The handover test
Here is the question that settles it: a client leaves tomorrow, amicably, and asks for their site. On separate accounts you take a full cPanel backup, hand it over, release the domain and close the account. It is an afternoon.
On addon domains you are extracting one site's files and one database out of a shared account, untangling shared mail configuration, and hoping nothing else referenced anything you removed. It is a day, it is error-prone, and every hour of it is unbillable.
Handovers are not rare events. Clients get acquired, hire in-house people or simply move on. Being architecturally ready for one is a mark of a professional operation, and being unable to do it cleanly reads to the client as exactly what it is.
Where the resource and billing boundaries actually sit
One account has one allocation. Under addon domains, whichever site is busiest consumes the shared resource, and quiet clients subsidise noisy ones without anybody being able to see it.
Separate accounts let you set the limits per client in WHM — disk, bandwidth, databases, mailboxes — which means the tier a client pays for is the tier they actually receive. That is what makes a price list meaningful rather than aspirational.
Reseller plans are built around exactly this: Reseller 1 carries up to 100 client accounts inside 30 GB of NVMe, Reseller 2 takes 250 inside 60 GB, and Reseller 3 takes 500 inside 100 GB with 1.5 TB of bandwidth, with overselling switched on so small accounts do not reserve headroom they never use.
Splitting them out, and when not to bother
Doing it later is a job but not a crisis. For each site: create the account, copy the files and the database, verify on a temporary address, move the mailboxes, then change the delegation last so nothing is offline. Free migration in means the same work is done for you when the sites are arriving from elsewhere.
Do the busiest and the highest-stakes sites first. The quiet brochure site nobody has touched for two years can wait until you have separated the shop that takes payments.
And keep addon domains where they belong: your own portfolio, your own experiments, the throwaway landing page for a campaign. Sites you own, whose fate you are entitled to share.
Separation is the product
Reseller hosting exists precisely so that client sites are separate objects — a cPanel account each, limits set per package, credentials that belong to the client and a suspension that only ever touches one of them.
Overselling is enabled from the first account, so separation does not mean paying for headroom on every small site, and daily backups run across the whole estate with restores you can perform per account.
- One account per client site
- Limits set per package in WHM
- Suspension that touches one client
- Restores at account level
Why Hosting Seller
On every plan, as standard
Contained incidents
One client's compromise stays one client's problem, instead of taking ten sites offline while it is cleaned.
Clean handovers
A full cPanel backup and an unlocked domain — an afternoon rather than a day of untangling shared files.
Real tier boundaries
Disk, bandwidth, databases and mailboxes set per package, so what a client pays for is what they receive.
Separation without waste
Overselling on from the first account, so a small brochure site is not billed for headroom it will never touch.
Per-site security
Imunify360 watching each client site individually, which only works when the accounts are individual too.
Restores per client
Daily backups across the estate with account-level restores, so recovery does not mean rolling back everybody.
First Steps
From choosing to live
- 1
List every site by owner, not by domain
Anything owned by somebody who pays you belongs in its own account. That single sort tells you exactly how much separation work you have.
- 2
Rank by stakes, not by size
Shops, booking sites and anything handling payments move first. The brochure site nobody has edited since 2023 can wait.
- 3
Move, verify, then change delegation
Copy files, database and mailboxes, check the site on a temporary address, and only change the delivery and delegation records once it is proven.
- 4
Fix the pattern before adding more
Stop creating new addon domains for client work immediately. Separation is much cheaper at creation than at extraction.
In the Box
Packed with every plan
- A cPanel account of its own for every client site
- Package limits set by you for disk, bandwidth, databases and mailboxes
- Overselling enabled so separation does not waste allocation
- Up to 100, 250 or 500 client accounts depending on the tier
- Suspension that acts on one client account rather than an estate
- Imunify360 watching each client site individually
- Daily backups with restores you can run at account level
- Free SSL issued per site, on every account you create
- Private nameservers so a later move needs no client involvement
- Free migration in when you consolidate sites from other hosts
Across the Counter
Things people ask us all the time
Is it ever acceptable to host a paying client as an addon domain?
Only as a deliberate, temporary arrangement you have told them about — a staging build before launch, say. As a permanent structure it means a stranger's plugin can take their site offline, and there is no version of that conversation that goes well when it happens.
What happens to the other sites if one addon domain picks up malware?
They share the account, so they share the outcome: the clean-up, the possible suspension and the downtime all apply to the account rather than to the site. Separate accounts limit the blast radius to the client who actually had the problem, which is the entire point.
How do I split an addon domain into its own account later?
Create the account, copy files and the database, move the mailboxes, verify the site on a temporary address, then change the delegation last so nothing is offline. Do the shops and booking sites first. If the sites are arriving from another host, that work is done for you free of charge.
Is a reseller plan overkill compared with one account holding 25 sites?
They are different products rather than different sizes. A single shared account with room for 25 websites gives you one allocation and one fate. A reseller plan gives you up to 100 separate accounts with limits you set, credentials the client can hold and suspensions that touch one of them. Judge it on isolation and handover, not on the headline count.
Read next
DirectAdmin vs cPanel for Resellers
Panel licence economics for a growing client list, and what changes when you buy wholesale.
Hosting With Imunify360 Security
Malware watching per client site, which only contains anything if the accounts are separate.
Reseller Hosting
WHM, per-client cPanel accounts and package control, built for exactly this separation.
VPS Hosting
KVM servers with root, for the single client whose site has outgrown a shared account.
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.
Separate the fates.
A cPanel account per client, limits you set per package, and overselling on from the first one so separation costs you nothing.
See Reseller Hosting plans