An agency that hosts 20 client sites under one reseller or managed-hosting account carries 20 sets of uptime, backup, and security obligations through a single login, and the decision that sets the risk is made before the first site is built: whether the hosting account belongs to the agency or to the client. The cost of getting it wrong shows up at offboarding, when a client leaves and every site, email box, and DNS record has to be separated from an account that was never designed to be split.
The Short Answer
Use a client-owned account (the client is the account holder and the agency has delegated access) when the client is a business that will outlast the engagement, has its own payment method, and expects to keep the site if the contract ends. Use an agency-owned account (the agency is the account holder and bills the client for hosting) when the agency is selling a managed service with a monthly fee and the agency controls updates, backups, and incident response. Most agencies need both models, assigned by client type, and the failure comes from mixing them without a written rule.
This article compares account-ownership models, not specific hosts or plans, so it quotes no prices. For plan and price comparisons, see the agency white-label hosting guide, which carries as-of dates for each plan.
The Two Ownership Models
Agency-owned: the agency is the vendor
The agency holds the contract with the host (a reseller account, a managed-WordPress agency tier, or a cloud server it administers), places each client's site inside it, and bills the client a monthly fee that includes hosting. The agency is responsible for the uptime the client experiences, whatever the host's own service-level terms say. Because the host's agreement is with the agency, the host's support will usually speak only to the agency, not to the client's staff.
Strengths: one invoice per client, one place to patch, standardized backups, and a margin on the hosting line. Weaknesses: the agency holds the liability, every client's resource use draws on the same account limits, and a payment failure on the agency's card affects every client at once.
Client-owned: the agency is a delegated user
The client opens the hosting account, pays the host directly, and invites the agency as a collaborator or technical contact. Most managed WordPress hosts and cloud platforms support some form of team access, so the agency can deploy and maintain without owning the billing relationship. If the engagement ends, the client removes the agency's access and keeps the site.
Strengths: clean offboarding, no hosting liability for the agency, and no margin mix-up between design fees and hosting. Weaknesses: the agency gives up the recurring hosting line, depends on the client to keep the card current, and cannot standardize the stack across clients.
Comparison Table
| Factor | Agency-owned account | Client-owned account | Verdict |
|---|---|---|---|
| Who the host's agreement is with | Agency | Client | Client-owned keeps liability with the party that benefits |
| Billing | Agency bills client; pays host | Client pays host directly | Agency-owned only if hosting is a priced service line |
| Outage during a payment failure | Hits every client on the account | Hits one client | Client-owned isolates failures |
| Offboarding a client | Migration project, agency-run | Remove agency access | Client-owned is faster by a wide margin |
| Standardized patching and backups | Easy, one stack | Depends on each client's host | Agency-owned for managed-service clients |
| Host support access | Agency only | Client can contact host directly | Client-owned for clients with IT staff |
| Hosting margin | Yes, if priced | None | Agency-owned if margin matters to the model |
A Worked Offboarding Cost Example
The figures below are planning assumptions, not measurements. Replace them with your own.
- Assumption: 20 client sites on an agency-owned account; 3 clients leave in a year.
- Assumption: each agency-run migration takes 4 hours of staff time, at an internal cost of $100 per hour.
- Result: 3 migrations x 4 hours x $100 = $1,200 per year in offboarding labor, before any email migration, DNS work, or client communication.
- Client-owned alternative: removing access takes under an hour per client; the same three exits cost roughly $300 of staff time.
The difference of about $900 per year is small next to the hosting margin on 20 sites. That is the point: offboarding cost alone rarely decides the model. The decisive factors are liability and failure isolation, which a labor estimate does not capture.
What Goes Wrong in Practice
- Mixed models with no written rule: some clients on the agency account, some on their own, and no document saying which. The first time a client asks for a copy of its site, nobody knows who has the credentials.
- A single payment method for the whole account: an expired card on an agency-owned account can suspend every client site at once. Put the renewal date in a shared calendar with a named owner.
- Resource limits treated as unlimited: shared and reseller plans are never truly unlimited. One client running a heavy WooCommerce import can slow the others. Check the host's published limits for CPU, memory, and entry processes before adding a client with spikes.
- Backups stored only at the host: if the host's backup lives on the same account, losing the account loses the backup. Keep an off-host copy.
- No exit clause in the client contract: an agency-owned arrangement needs a stated notice period and a stated export format, or the migration becomes a dispute.
How to Choose Per Client
- Ask who will own the site in three years. If the answer is the client, default to a client-owned account.
- Check whether hosting is a priced line in the proposal. If the agency sells care plans with updates, backups, and monitoring, agency-owned is consistent. If hosting is incidental, do not hold the liability for it.
- Look at the client's technical staff. A client with an IT contact can manage its own account; a solo owner usually wants someone else to.
- Size the blast radius. If more than 5 or 10 sites would go down together on one account, split them across accounts by risk profile.
- Write the rule into the contract. State who owns the account, who pays the host, what happens at termination, and who holds the backups.
Questions to Put to a Host Before Choosing a Model
Host feature pages describe account structure in marketing terms. The answers that matter come from the support team or the terms of service, and they are worth getting in writing before the first client site goes live.
- Can account ownership be transferred? Some hosts allow a site or an environment to be moved to another account, and some require a fresh migration. This one answer decides how painful an agency-owned exit is.
- Does the plan support team members with limited permissions? A client-owned model depends on being able to invite the agency without sharing the owner login.
- Who may contact support about a site? On agency-owned accounts, some hosts talk only to the account holder, which means the client cannot escalate an outage on their own.
- What are the published resource limits per account and per site? Look for CPU, memory, concurrent processes, and monthly visits. A limit that is shared across all sites on an account is the one most likely to be hit by a single noisy client.
- Where do backups live and how long are they kept? Confirm the retention period, the restore method, and whether restores are included or billed.
Where Specific Hosts Fit
The ownership model narrows the field before price enters. Agency-owned accounts point toward reseller or agency-tier plans with a client-management panel, and client-owned accounts point toward managed hosts that support team invitations. The WordPress hosting for digital agencies guide and the hosting for multiple WordPress sites guide cover plans with dated pricing; the shared hosting vs managed WordPress comparison explains the underlying product difference. For moving a client between accounts, the migration and cancellation sequence lists the order of operations.
The Verdict
For one-off website projects, choose client-owned: it removes liability, isolates failures, and makes offboarding a one-hour task. For recurring care plans where the agency controls updates, backups, and incident response, choose agency-owned and price the hosting line to cover the risk. Document the choice for every client in the contract, and keep one backup outside the host.
Compare agency hosting options on HostingDive, with intro and renewal pricing, resource limits, and client-management features for each plan.
Frequently Asked Questions
- Should an agency host client sites on its own reseller account?
- Only when hosting is a priced, managed service. A reseller account makes the agency liable for every site's uptime, so a flat hosting fee that ignores that liability underprices the risk.
- Can a client-owned account still be maintained by the agency?
- Yes. Most managed WordPress hosts and cloud platforms support team access or collaborator invitations, so the agency can deploy updates without holding the billing relationship.
- How many sites should share one hosting account?
- There is no universal number. Split accounts when the loss of one account would be unacceptable to the whole client base; as a working rule, avoid putting more than 5-10 high-value client sites in a single failure domain.
- Where should backups live?
- At least one copy outside the hosting account that serves the site, so account suspension or deletion does not remove the backup.