Partner Hosting Explained: Reseller, Affiliate, White Label, and Who Answers the Phone

Partner hosting is any arrangement where you sell someone else’s infrastructure to your own clients. The three common shapes are affiliate, where you refer and get a commission; reseller, where you buy capacity wholesale and bill your clients directly; and white label, where the provider is invisible and everything carries your brand. The models differ mostly in one thing: who your client calls when the site is down.

Agencies get pitched these programmes constantly, usually framed as recurring revenue with no extra work. The recurring revenue is real. The no extra work part is where the pitch quietly stops describing reality, and the difference between the three models is exactly the difference in how much extra work arrives.

Table of contents

• The three models, precisely
• Who answers the phone at two in the morning
• Margin arithmetic, and where it goes wrong
• Oversubscription and the resource question
• The exit question nobody asks first
• Choosing between the models
• How this fits the rest of the stack
• FAQ

The three models, precisely

The names are used loosely in marketing material, so it is worth being exact about what each one actually commits you to.

• Affiliate. You send a referral link. The client signs up with the provider, pays the provider, and is the provider’s customer. You get a one-off or recurring commission. You have no support obligation and no control.
• Reseller. You buy an allocation of resources at wholesale and divide it among client accounts. You set the retail price and you bill the client. The client is your customer. The provider supports you, and you support the client.
• White label. Reselling plus brand removal. The control panel, the notification emails and sometimes the nameservers carry your name. The client may not know the underlying provider exists.

There is a fourth arrangement that is increasingly common and does not have a marketing name: you deploy each client on their own account with a mainstream platform, they pay the platform directly, and you charge for management. It has none of the margin of reselling and none of the liability, and for a lot of agencies it is the correct answer.

Who answers the phone at two in the morning

This is the question that decides whether a partner programme is a good idea for your business, and it is rarely on the comparison page.

Under an affiliate arrangement, the provider does. You are not in the loop, which is comfortable until a client asks you to chase something and you have no standing to do so.

Under a reseller or white label arrangement, you do. Your client’s contract is with you. When their site is down, they call you, and you open a ticket with the provider and wait, while remaining the only person your client can shout at. You have taken on the full support obligation and kept only partial control over the resolution.

That asymmetry is the central risk of reselling, and it is why the model works well for agencies with a support function and badly for solo developers who wanted a passive income stream. The revenue is recurring. So is the pager.

Two questions worth asking any provider before signing:

• What is the guaranteed response time on a partner ticket, and does it differ by severity?
• Can I see the underlying incident history, or do I find out about outages from my own clients?

Margin arithmetic, and where it goes wrong

The pitch is straightforward: buy wholesale, sell retail, keep the difference, multiply by the client count. The arithmetic is correct and incomplete.

What the model leaves out is that the cost of a hosting client is not the hosting. It is the support minutes. A client on a small plan generating one support conversation a month can consume more of your margin than the plan is worth, and the clients most likely to generate those conversations are exactly the ones on the smallest plans.

The way this usually goes wrong, in order:

1. You sign twenty small clients because the margin per client looks fine.
2. Support volume scales with client count, not with revenue.
3. You are now running an unstaffed hosting company as a side effect of running a design agency.
4. The margin is consumed by the support, and you cannot raise prices without a renegotiation with every client at once.

The version that works is the opposite shape: fewer clients, larger engagements, hosting bundled into a maintenance retainer that is priced for the support rather than for the server. The hosting becomes a component of a service you were charging for anyway, rather than a product line with its own economics.

Oversubscription and the resource question

Wholesale allocations are usually sold as a pool: an amount of storage, an amount of bandwidth, and a number of accounts. The pool is shared, which means one client’s traffic spike is drawn from the same bucket as everyone else’s steady state.

Ask directly what happens at the limit. The answers vary and they matter:

• Hard cap with a suspension. Predictable, and brutal if it lands on a client’s launch day.
• Overage billing. Predictable in behaviour, unpredictable in amount, and the bill lands on you rather than on the client who caused it.
• Soft throttle. Everything gets slower and nobody gets an alert, which is the hardest failure to diagnose from the outside.

Also ask about isolation. If accounts share a machine, one client running a badly written import script can degrade every other site in your pool, and you will spend the afternoon explaining that to people who did not cause it.

The exit question nobody asks first

Partner arrangements are easy to enter and structurally difficult to leave, because leaving means migrating every client at once.

Before signing, get concrete answers to these:

• Can I export full site and database backups on demand, in a standard format, without asking support?
• Who owns the client relationship contractually if the arrangement ends?
• If I stop being a partner, do the client accounts transfer to direct accounts with the provider, or do they terminate?
• Are the nameservers mine or the provider’s? If they are the provider’s, a migration is a DNS change on every domain simultaneously.

A provider that answers these clearly is a reasonable partner. A provider that treats them as hypotheticals is telling you something useful.

Choosing between the models

The decision comes down to what you want to be responsible for.

Take the affiliate route if you want a referral income and no operational surface. It pays less. It also cannot wake you up.

Take the reseller or white label route if you already run a support function, have more than a handful of clients, and can price hosting inside a retainer rather than as a standalone line item. The brand control is genuinely valuable when hosting is part of a larger managed service.

Take the fourth route, separate accounts plus a management fee, if you are small, if your clients vary a lot in their needs, or if you would rather sell your expertise than someone else’s servers. The margin is lower and the liability is much lower, and for most agencies that trade is the right one.

How this fits the rest of the stack

Whichever model an agency lands on, the calculation that decides it is the per-client monthly cost against what the client is billed, and that is only honest when every component is listed rather than bundled. The RunxBuild hosting calculator breaks a project into its parts so a per-client figure can be built from real line items: the service, the database, the storage and the bandwidth. For agencies taking the separate-accounts route, RunxBuild has teams, so several people can hold access to a project without sharing one login, and managed WordPress starts at three dollars a month with a file manager and a database browser in the dashboard rather than behind SFTP.

Useful related references:

• What Is a Static Website? Benefits, Examples, Hosting
• WordPress Self-Hosting: LAMP, Docker, or Managed RunxBuild
• Webspace Hosting: An Old Word for a Constraint That Moved
• Services on RunxBuild

FAQ

What is the difference between reseller hosting and partner hosting?

Partner hosting is the umbrella term for any arrangement where you sell a provider’s infrastructure. Reseller hosting is one specific form of it, where you buy capacity wholesale and bill clients directly. Affiliate and white label programmes are also partner arrangements with different obligations.

Is reseller hosting profitable?

It can be, but the margin is consumed by support rather than by infrastructure. Profit depends on client count relative to support capacity, not on the wholesale discount. Agencies that bundle hosting into a maintenance retainer do better than those that sell it as a standalone product.

Do I need technical skills to resell hosting?

Yes, more than the marketing suggests. You become the first line of support, which means diagnosing DNS problems, certificate errors, PHP version mismatches and email delivery issues before you can even escalate meaningfully to the provider.

What is white label hosting?

Reselling with the provider’s branding removed. The control panel, notification emails and sometimes the nameservers carry your name instead. It is useful when hosting is presented as part of your own managed service, and it makes migrating away harder because the client has no relationship with the underlying provider.

Can I just put clients on their own accounts instead?

Yes, and for many agencies that is the better arrangement. The client pays the platform directly and you charge a management fee. You give up the reselling margin and you also give up the billing liability, the support obligation and the migration problem if you ever change providers.