Short answer: “white label hosting” describes three different arrangements that get sold under one name, and they have very little in common. One is reselling, where you own the account and become the support desk. One is cosmetic branding, where the panel carries your logo but the client still owns their account. One is simply not mentioning who hosts the site, which requires nothing from the host at all and is what most agencies are actually doing. Work out which one you are buying before you compare prices, because the operational cost of the first is enormous and the third is free.
The three things "white label" means#
Vendors use the term loosely, and the marketing page rarely separates them. These are the arrangements underneath it.
| Reselling under your brand | Cosmetic rebranding | Unbranded pass-through | |
|---|---|---|---|
| Who owns the hosting account | You | The client | The client |
| Who the client pays | You | The host | The host |
| Who answers “my site is down” | You | The host | The host |
| Does the client see the host’s name | No | Only in small print | Only if they look |
| What it costs you to run | A second business | Usually a plan upgrade | Nothing |
| Client can leave without you | No | Yes | Yes |
| What you are really selling | Infrastructure | Your own branding | Your expertise |
Reselling under your brand#
You buy capacity wholesale, put client sites inside your account, bill the clients yourself at your own price, and the client never learns who the underlying host is. This is the version with real margin and it is the version people mean when they say white label hosting is a revenue stream.
It is also a business rather than a revenue stream, and the costs are laid out in detail in how agencies make money on client hosting. The short version is that you inherit the support queue, the billing operations, the cashflow float, and a lock-in problem that surfaces the day a client decides to leave.
Cosmetic rebranding#
The client has their own account and pays the host directly, but the control panel, the login screen and the notification emails carry your logo and your domain instead of the host’s. Some hosts offer this as a plan feature, often on higher tiers.
This is the version most agencies imagine when they picture white labelling, and it is much cheaper than reselling because you are not taking on the account. What it buys you is presentation. What it does not buy you is margin, since the client is still paying the host directly and can see the invoice.
Unbranded pass-through#
You recommend a host, the client signs up and pays them, and you simply do not make a feature of who it is. There is no rebranding, no reseller agreement, no arrangement of any kind. The client could find out with one click in their own account, and in practice most never think about it.
This costs nothing, requires nothing from the host, and is what the majority of agencies are doing whether or not they call it white labelling.
What you are actually buying#
Strip the branding question away and there are only two decisions underneath it.
Do you want the hosting margin? If yes, you need reselling, and you need to accept the operational load that comes with it. There is no arrangement that gives you the margin without the support queue, because the margin is payment for the support queue.
Do you want the client to believe the infrastructure is yours? This is a positioning choice, not a technical one, and it is worth thinking about harder than most agencies do.
The case for hiding the host is that it makes your offering feel complete and makes you harder to disintermediate. The case against is that it makes you responsible for something you do not control. When the platform has a bad day, you have no infrastructure story to tell, because you claimed it was yours. You cannot say “the host is on it” when you have spent two years implying there is no host.
There is also a slower cost. Clients who believe you built the infrastructure will ask you to change it. Requests that a host would answer with a documented feature become custom work you have to either do or refuse, and refusing is awkward when you are supposed to own the stack.
The argument for naming your host#
The opposite approach is worth considering seriously, because it is what experienced agencies tend to drift towards.
Put hosting on the proposal as a named third-party cost the client pays directly, priced, in the same place you list a premium plugin licence or a font subscription. Clients are entirely used to that. What they object to is a vague “hosting and infrastructure” line at a number they cannot verify, which is exactly what reselling produces and exactly the line that gets challenged at renewal.
Naming the host does three useful things. It removes the renewal argument. It makes your own fee legible as the part that requires a person. And it lets you recommend something because it is good rather than because you have margin on it, which is a stronger position to argue from and one you can say out loud.
It also makes your exit clean. When a client leaves, they keep their site and their account, nobody performs a migration that somebody has to pay for, and the relationship survives intact. Agencies underrate this until the first time it goes badly.
When white labelling genuinely is right#
There are real cases, and they share a shape.
You already run a helpdesk. If you have defined support hours, a ticketing system, and somebody whose job includes billing, the marginal cost of absorbing hosting support is much lower than it would be for a three-person studio. The margin is real and the overhead is already paid for.
Hosting is genuinely one component of a managed service. If you sell an outcome that includes the site, the maintenance, the content and the infrastructure as one number, then itemising a hosting line undermines the offer. An MSP selling a managed package is in a different business from an agency selling website builds.
The client is contractually forbidden from managing infrastructure. This comes up in regulated work and in large organisations with procurement rules. Sometimes the client genuinely cannot hold the account, and somebody has to.
Outside those, the honest answer for most agencies is that the branding is worth less than it appears and the operational load is worth more than it appears.
What to check before signing a reseller agreement#
If you have decided reselling is right for you, these are the terms that matter and they are rarely on the pricing page.
What happens to client sites if your account lapses. You are a single point of failure for every client in the account. Ask what the grace period is and whether clients can be extracted individually.
Whether you can split a client out. When one client leaves, can that site be moved to their own account cleanly, or does somebody have to perform a full migration? The answer decides whether every departure costs you a day.
Who the abuse contact is. If one client site is compromised and starts sending spam, the complaint arrives at the account holder, which is you. Understand what the host’s response is: a warning, a suspension of that site, or a suspension of everything in your account. The last one is not unusual and it is catastrophic.
Isolation between sites in your account. If everything under your reseller account shares one underlying system account, a compromise on one client site can reach the others. That risk concentrates on you specifically, because you are the common factor across twenty clients. This is one of several reasons per-site isolation is worth more to an agency than to anyone else.
What support you actually get. Reseller support is frequently a different and slower queue than end-customer support, on the theory that you are technical. Find out before you promise a client a response time you cannot meet.
What reselling quietly makes you#
The part that surprises agencies is not operational, it is contractual. When you bill the client for hosting, you stop being an intermediary and become the supplier. Several things follow from that, and none of them appear on a reseller pricing page.
You are the merchant of record. The client’s card is charged by you. That means failed payments are your dunning process, refunds are your decision, and chargebacks land on your payment processor and your dispute rate. A client who disputes a hosting charge is disputing it with you, and you will be the one assembling evidence for it.
Sales tax becomes your problem. Digital services are taxed differently depending on where the buyer is, and thresholds vary. Reselling hosting across clients in several states or countries can create registration obligations you did not have when you were only invoicing for design work. This is worth ten minutes with an accountant before it is worth any amount of margin.
You need your own terms. If you are supplying hosting, you need an acceptable use policy, a service description, and something that says what happens during downtime. Passing through the host’s terms does not work, because the client has no contract with the host. In practice most agencies skip this entirely and discover the gap during the first serious dispute.
You may become the data controller. Depending on jurisdiction and what the sites process, holding the hosting account can change your role under data protection law from processor to controller, with the documentation obligations that carry. Agencies working with healthcare, finance or EU customers should check this rather than assume.
Uptime promises are yours to make and yours to break. If your contract mentions availability, you are promising something you do not control. Your host’s outage becomes your breach. Either omit the promise, or make sure whatever you commit to is comfortably looser than what your host commits to you.
None of this makes reselling wrong. Firms do it profitably every day. But the honest accounting is that the margin is not payment for reselling, it is payment for absorbing a support desk, a billing operation, a tax position, and a contractual liability. Compared against that list, a fifteen dollar monthly markup on twenty sites is not obviously a good trade, and it is the trade most agencies make without ever writing the list down.
Where Hostney sits#
We do not offer a reseller tier or panel rebranding, and it is worth saying why rather than pretending it is coming.
Reselling puts client sites inside your account, which creates the lock-in and the abuse-contact problem above, and it hands you a support desk. We would rather the client owned their account. They pay us directly, they can leave whenever they like, and if they part ways with you they keep a working site without anybody performing a migration.
You work inside the account through delegate access, which the client grants and can revoke, and which gives you your own login rather than their password. Your actions appear in the account’s activity log as yours rather than as theirs. One limitation worth knowing: delegate access is all-or-nothing per hosting account today, so scoped or read-only access for a junior team member is not something we can offer yet.
On the commercial side there is a partner programme instead of a reseller discount. The client pays us, you take a commission on their invoices, and your own invoice covers your work. Current rates are on the partner page rather than here, because that is the sort of number that changes and an article is a bad place to keep it.
If you want to test the platform on something real before recommending it, the trial is there, and free migration is performed by a person for sites you already have elsewhere.
Summary#
“White label hosting” is three arrangements wearing one name. Decide which you are actually buying before comparing anything.
Reselling is the only one with margin, and the margin is payment for becoming a support desk, a billing operation and a single point of failure for every client in your account. It suits firms that already run a helpdesk and punishes everyone else.
Cosmetic rebranding buys presentation without margin. Unbranded pass-through costs nothing and is what most agencies are already doing.
The branding question is a positioning choice, and the less obvious answer is often the better one: name your host, price it as a third-party cost the client pays directly, and charge properly for your own work. You lose a margin that was never large and gain an honest recommendation, a clean exit, and a maintenance plan that is worth considerably more than the hosting ever was.