Operations Notes
Reseller hosting vs affiliate programs — One of these is a link; the other is a rota
You are deciding whether to own the customer or hand them over, and nobody has told you what owning them costs in hours once there are forty of them.
The short answer
Measure the workload, not just the margin: a referral link is a one-off payment with no operational tail, while a reseller pool brings capacity planning, backup windows, per-client limits and a support rota that scales with the account count.
Refer where you want a light touch on an existing audience. Resell where you want recurring margin and an asset with resale value of its own — and where you are willing to be the person who answers when a client site is slow. Below: the numbers to track before you commit.
By the HostingFast team · Reviewed 24 August 2026
24/7
Humans reachable
1-click
WordPress provisioning
Free
Certificates, every site
Daily
Backups, everywhere
Referral bounties settle once and stop. A resold account keeps paying for as long as the client renews, so across a multi-year relationship the owned customer returns a multiple of the referral fee.
The support workload is the price of that multiple, and it is the part that never appears in the comparison. It is measurable, though, and measuring it before you commit is what separates a hosting business from an expensive hobby.
What you are actually buying with a reseller pool
Reseller 1 is specified at 30 GB of NVMe with 300 GB of bandwidth and 100 client accounts. Reseller 2 doubles the storage and bandwidth and carries 250 accounts; Reseller 3 runs 100 GB and 1.5 TB across 500. Overselling is enabled from day one on all three.
That last point is the one to think about carefully. Overselling is a planning tool, not free capacity: it lets you allocate beyond the pool on the reasonable assumption that not everybody uses their limit at once. The assumption holds until it does not, which is why per-client resource limits exist and why you should set them.
Each client receives their own panel account with their own allocation, and private nameservers carry your brand rather than ours. Your supplier stays out of view unless you put it there.
The support load, expressed as a number
Track tickets per account per month. It is the single most useful figure in a reseller business and almost nobody records it. Multiply it by your target account count and you have the rota you are signing up for, expressed in hours rather than in optimism.
The distribution matters as much as the average. A handful of clients typically generate most of the volume, and identifying them early lets you price accordingly instead of quietly subsidising them out of the margin on everyone else.
Tooling absorbs a great deal of it. Account provisioning, daily backups across every client account, Imunify360 on every client site and a billing system that suspends overdue accounts by itself all remove work that would otherwise be yours.
Keeping one client from becoming everybody's problem
Set per-client resource limits before you need them. A single site with a runaway plugin or an unindexed query can consume a disproportionate share of a shared pool, and limits turn that from an incident affecting everyone into a conversation with one customer.
Watch the backup window as the pool fills. A full cycle across a hundred accounts takes a great deal longer than a cycle across ten, and if it starts overlapping your clients' traffic they will feel it without ever knowing why.
NVMe under LiteSpeed applies to every client account, which raises the floor considerably. Most of the contention problems that plague reseller pools are storage and cache problems first.
Which one compounds, and what it costs to find out
Referral income converts your audience's trust into equity for somebody else's brand. Reseller income builds a client book you could sell. That is the real asymmetry, and it is worth more than the per-transaction margin difference people usually quote.
Plenty of people run both: resell what you can support properly, refer the products you would rather not touch. The only discipline worth enforcing on yourself is being transparent about which arrangement each customer is in.
Before you commit, note the trial constraint: reseller plans carry a 7-day refund window rather than the 30 days that covers shared, business, WordPress and WooCommerce hosting. Plan your evaluation for that week rather than drifting past it.
The number that predicts the business
Tickets per account per month is the figure that tells you whether reselling suits you. Everything else — margin, capacity, panel choice — is downstream of how much support the book generates.
Daily backups run across every client account, and Imunify360 shields every client site, which removes two of the biggest sources of that ticket volume before it starts.
- Tickets per account, tracked monthly
- Per-client limits set in advance
- Backup window timed as the pool fills
- Seven-day window on reseller plans
Why HostingFast
Standard on every plan
Your brand on every screen
Private nameservers and your own package names, so the supply chain stays invisible to the client.
Per-client resource limits
Define the ceilings yourself, which is how one runaway site stops becoming everybody's incident.
Overselling from day one
Allocate beyond the pool deliberately, with limits in place so the assumption stays safe.
Backups across the whole pool
Daily backups on every client account, so a restore request is a task rather than an apology.
Imunify360 on client sites
Server-level protection across the pool, which removes a large share of the ticket volume before it starts.
Wired for WHMCS billing
Ready to connect to WHMCS, so invoicing and suspension stop being things you do by hand.
Quick Start
From order to online
- 1
Log a month of tickets against accounts
Record every support request and which client generated it. The average tells you the rota you are buying; the distribution tells you which clients you are quietly subsidising.
- 2
Set per-client limits before you need them
Define resource ceilings at provisioning time rather than after an incident. A limit applied in advance is a policy; the same limit applied afterwards is an argument.
- 3
Time one full backup cycle
Run a complete backup across your current accounts and extrapolate to your target count. If the projected window collides with client traffic, move the schedule now while it is still cheap to move.
Built In
Loaded onto every plan
- Your own panel for management, with a separate account for each client
- Private nameservers carrying your brand rather than ours
- Per-client resource limits defined by you at provisioning time
- Overselling enabled from day one across the reseller tiers
- Daily backups across every client account in the pool
- Imunify360 shielding every client site
- NVMe SSD storage behind a LiteSpeed cache on every account
- Free SSL on every site you host, renewed automatically
- Ready to wire straight into WHMCS billing, with no setup fee
- Reseller plans carry a 7-day window; hosting plans carry 30
Frequently Asked
What people ask us most often
How many client accounts fit before a pool starts feeling slow?
The tiers are specified at 100, 250 and 500 accounts, but the number that predicts the experience is how much of the pool is actively used at once. Set per-client resource limits, watch the backup window as it fills, and treat overselling as a planning assumption you keep checking rather than as spare capacity.
What resource limits can I set per client?
You define the ceilings yourself from the reseller controls, which is the mechanism that keeps one busy site from consuming a shared pool. Set them at provisioning time as a matter of policy — retrofitting a limit onto an existing client is a conversation nobody enjoys having.
How do I stop one slow client site affecting the others?
Limits first, then diagnosis. Per-client ceilings contain the blast radius immediately; after that it is the usual work of finding the query or the plugin responsible. NVMe under LiteSpeed raises the floor across every account, which removes a large share of these incidents before they start.
What is the refund window on a reseller plan?
Seven days, against the 30 days that covers shared, business, WordPress and WooCommerce hosting. An account starts earning the moment it is provisioned, which is the reasoning behind the shorter window — so run your evaluation inside that first week rather than leaving it.
Keep reading
WHMCS Hosting
Hosting the billing application itself so the nightly cron actually finishes.
Reseller Hosting for Agencies
Turning delivered client projects into recurring revenue without inheriting a support rota you cannot staff.
Reseller Hosting (Glossary)
What reselling is at the account level, and where the boundary with your supplier sits.
Reseller Hosting
White-label reseller hosting on NVMe, with your brand out front and monthly billing behind it.
OpenCart Hosting
One-click OpenCart on storefront-tuned PHP, with free SSL and staging included.
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.
Price the rota, then start.
Reseller pools on NVMe with per-client limits, daily backups across the book, and private nameservers carrying your name.
View Reseller Hosting plans