Own the Pipes, Not the Keys: Who Should Own What Between an Agency and Its Client

Every agency has the “who owns what?” conversation eventually. It’s far easier to have it on day one than when offboarding. This article is for WordPress agencies, and it comes down to one idea: pipes and keys.

The pipes are replaceable infrastructure: hosting, staging, caching, and the systems that keep a website running.

The keys are the assets that carry business identity, access, or history: domain registration, advertising accounts, analytics, and the email address used to register services.

You can own the pipes without holding the keys. Clients need control of their business assets. Agencies need enough operational control to do their jobs efficiently. Those goals only conflict if you treat every account as the same kind of asset.

Agencies genuinely disagree on where to draw the line, so we have included the strongest arguments on both sides, followed by our own take. Let the debate begin!

Who Should Own What?

Ask one question about each asset: If your agency disappears tomorrow, could the client recover it and keep their business running?

A website can usually be migrated if there’s a working backup, access to the necessary files, and a clear handover plan. A domain, advertising account or analytics property may carry years of identity, data and history that can’t simply be recreated.

That gives you a practical starting point:

	Default owner	Agency’s role
Domain registration	Client	Manage DNS and technical settings
Business email used for registrations	Client	Help configure it
Advertising accounts, pixels and audiences	Client	Work through delegated or partner access
Analytics and Search Console	Client	Receive user access
Website CMS accounts	Client keeps an admin account	Use named accounts with appropriate permissions
Hosting and staging	Agency or client, according to the agreement	Operate and maintain when the agency owns the account; work through delegated access when the client does
Backups	Both should have access to a usable copy	Maintain and test recovery

Paying for an account doesn’t necessarily mean owning it, administering it or being responsible for everything that happens there. An agency might pay for and operate hosting while the client owns the domain and remains responsible for their business decisions and data.

Put these roles in the contract. Don’t rely on assumptions about what “the client account” or “agency-managed” means.

Hosting: When Agency Ownership Makes Sense

Hosting is often the strongest case for agency ownership. A consistent environment makes it easier to manage PHP versions, caching, updates, security settings, and troubleshooting across multiple WordPress sites.

It also cuts coordination time. If a site goes down, you may need server logs, emergency access, or help from the hosting provider. When the client controls the hosting account, even a straightforward fix can involve another person, another support queue, and another set of permissions.

The Cost of Owning Hosting 

Agency-owned hosting comes with obligations. Clients will usually call you when the website fails, even if the hosting platform is at fault. Selling hosting means selling a support expectation, not just server space. It also means the client’s site and backups live in your account, so spell out exit terms: how fast you’ll hand over a full backup, who pays for migration, and how long the site stays live during the move.

Choose a Model and Set the Rules 

A useful policy is to offer agency-managed hosting as part of a clearly defined maintenance plan. Let clients keep their own hosting when they have in-house IT, an established provider, or compliance requirements you can’t meet. If you support websites on outside hosts, explain the limits and charge for the extra coordination where appropriate.

The key is consistency. Decide which model you offer, what support it includes, and how a client can leave. If every client has a different arrangement, your team has more exceptions to remember and more things that can go wrong.

“Good web hosting is at the heart of any successful website. Regardless of platform, you need safe, fast, and dependable web space to make your site accessible.” Rocket.net

The debate: who should own the hosting account?

	Agency owns it	Client owns it
Upside	One consistent environment, faster fixes, and hosting you can bundle into a care plan	Full portability, a clean exit, and a fit for clients with in-house IT or compliance rules
Downside	Clients expect you to fix every outage, and some feel locked in	More coordination, extra support queues and slower emergency fixes

Our take: Hosting is the one asset where agency ownership is reasonable, provided exit terms and backup access are in writing.

Does the Hosting Plan Actually Make Money?

Hosting revenue is not the same as profit. Setup, support tickets, troubleshooting, and renewals all take time. The right question is how much support time the remaining revenue can pay for.

Use this calculation:

Break-even hours = (Monthly plan price − Hosting cost) ÷ Hourly labor cost

Say a care plan costs $75 per month, hosting costs $8 per site, and your loaded labor cost is 60 an hour. That gives (75 − $8) ÷ $60 = 1.12 hours, or about 1 hour and 7 minutes of labor per site each month before labor consumes the revenue left after hosting.

Now compare it with a more reliable setup that costs $30 per site but cuts support to 15 minutes a month:

	Host A	Host B
Care plan price	$75	$75
Hosting cost per site	$8	$30
Support time per month	60 minutes	15 minutes
Labor cost at $60/hour	$60	$15
Left per site, before other overheads	$7	$30
Across 50 sites	$350	$1,500

The pricier host breaks even at 45 minutes of support per site, so 15 minutes leaves plenty of room. These are illustrative figures, not industry benchmarks. The point is that the cheapest host isn’t necessarily the most profitable one. Price your care plan around the work it creates, not just the provider’s monthly fee.

“Offering website maintenance care plans is one of the best ways to stabilize and grow your revenue.” Rocket.net

Domains and Advertising Accounts: Keep the Keys with the Client

Domains: Check Who the Registrant Is

The client should normally be the domain’s registrant, the person or organization recorded as holding the registration. You can manage DNS and technical settings without owning the domain.

Registering a client’s domain under your agency’s details can create problems when the relationship ends. A contract may say the client owns the domain, but the registration record and account access still need to support that ownership.

Before changing registrant details or transferring a domain, check the current rules with the registrar. Some changes can trigger transfer restrictions or waiting periods. A domain transfer also doesn’t automatically move DNS hosting, so plan the change to avoid disrupting email or the website.

Use an email address controlled by the client for important registrations and recovery. If every service is tied to an agency employee’s mailbox, the client may lose access when that person leaves, or the contract ends.

The debate: who should be the registrant?

	Agency registers it	Client registers it
Upside	One dashboard, no missed renewals and less to explain to clients	The registration record matches the contract, and leaving is a non-event
Downside	Disputes and transfer delays when the relationship ends, plus messy recovery if an employee leaves	The client may miss a renewal or lose the login, and you wait on them for changes

Our take: The client should be the registrant. Keep DNS access, renewal reminders, and a recovery email the client controls as part of your care plan, so you get the convenience without holding the registration.

Advertising Accounts: Use Partner Access

The client should own its advertising accounts, payment methods, pixels, and related business assets. You should be granted the access you need to manage campaigns.

For a new Meta setup, have the client create its own business portfolio and own the relevant Pages, ad account, and datasets. You can then request partner access. On Google Ads, link the client’s account to your manager account.

The client should use its own payment method for ad spend. You shouldn’t need to carry the client’s advertising costs on your own card.

This arrangement also makes the end of the relationship simpler: the client can revoke access without trying to recover an account created inside your agency’s business structure.

At handover, check both partner permissions and individual users. Revoking one kind of access doesn’t necessarily remove every person who may have been granted access separately.

The debate: who should own the ad accounts?

	Agency owns them	Client owns them (partner access)
Upside	Full control over account structure and billing, with a quick start	The client keeps its history, pixels, and audiences, and can revoke access cleanly
Downside	You carry spend and payment risk, a suspension lands on your business, and the client loses its history on exit	More setup up front, and you depend on the client to approve access and keep billing current

Our take: The client owns the account, and the agency works through partner access. Agency-owned ad accounts put your business on the hook for someone else’s spend and policy compliance.

Contracts, Data Protection and Responsibility

The contract should settle practical questions before work begins:

• Ownership: Who owns each domain, account, dataset, and website asset?
• Access: Who can administer each service, and how is access revoked?
• Support: What does the agency fix, and what belongs to the hosting provider?
• Response times: What counts as an emergency, when is support available, and what does out-of-hours work cost?
• Exit: What will be handed over, by when, and who pays for migration?

For EU clients, data protection needs separate attention. If you process personal data on the client’s behalf, you may be acting as a processor under the GDPR. An appropriate data processing agreement should be in place, and you must account for relevant subprocessors, including your hosting provider.

The agreement documents each party’s obligations. It doesn’t automatically transfer all legal responsibility from one party to another, because the actual roles depend on what each party does. Have your contract and data-processing arrangements reviewed by a qualified professional where necessary.

Hosting ownership alone doesn’t decide who is responsible for personal data, just as owning a domain doesn’t make someone responsible for every technical task performed on it.

Make the Handover Part of the Project

A clean exit shouldn’t require a crisis meeting. Agree on the process at the start and keep the information current throughout the relationship. Use this short checklist when you set up a project and again when a client leaves.

Before Work Begins

• Record the owner, administrator, billing contact, and renewal date for each service.
• Make sure the client controls the domain registration and recovery email.
• Confirm the client owns its advertising accounts and analytics properties.
• Agree on hosting responsibilities, backups, support, and migration costs.
• Document the technology stack and the important configuration choices.

When the Contract Ends

• Confirm domain registration, DNS, and transfer requirements.
• Transfer the website or provide a usable backup and migration instructions.
• Check advertising (partner permissions and individual users), analytics, Search Console, and CMS access.
• Return or delete personal data as required by the agreement.
• Confirm the new site works before shutting down the old environment.
• Settle billing, document the handover, and confirm the client can access its assets.

Don’t withhold a client-owned asset to resolve a payment dispute. Handle unpaid invoices through the agreed contractual process, not by making the client’s domain or business accounts inaccessible.

“A clean offboarding isn’t a chore – it’s not even a service – it is a competitive advantage. Most of your competitors aren’t doing it. That’s your edge.” Rocket.net

The Bottom Line

Let your agency manage hosting and infrastructure when that makes the work more efficient. Keep domains, advertising accounts and business data under the client’s control. Make ownership, support, costs and handover responsibilities explicit before the project starts.

Hosting is a real judgment call, and agency ownership works when exit terms are clear. For domains and ad accounts, the case for client ownership is much stronger, because the client carries the history and the risk.

Get your agency the access you need to do the work. Let the client keep control of its business assets. And agree on how to separate before anyone needs to.

Fast & Secure Hosting? Yes, Please!

Grow your business with lightning-fast, secure and optimized websites that are easy to set up and manage. Top-tier agencies and online businesses choose Rocket.net as their trusted managed WordPress hosting provider. Why shouldn’t you?

Choose your plan today!