Plenty of organisations are well served by hosting that sits in their agency’s or provider’s account. Managed hosting is a legitimate service. The question is not ‘who hosts?’ but ‘on what terms?’ If you cannot answer three things about your current setup (where the site physically lives, what happens if you leave, and who holds the credentials), you have a problem worth fixing now, while the relationship is still good.
Hosting you own vs hosting you rent through someone else
When you buy hosting directly from a provider (a managed WordPress host like WP Engine, Kinsta, or Cloudways), you hold the account credentials, the billing sits with you, and you can grant or revoke access to anyone who works on your site. If the agency relationship ends, your site stays where it is.
When your agency or developer hosts your site on their infrastructure (their server, their reseller account, their Cloudflare setup), you are a tenant. That can work well for years. Agencies that specialise in hosting often deliver better uptime, faster patching, and more coherent server configuration than a client would manage alone. The arrangement only becomes a problem when it is opaque.
‘Opaque’ means any of the following:
- You don’t know which hosting provider sits underneath your agency’s setup.
- You have no direct server access, no cPanel or dashboard login, not even read-only.
- Your contract or retainer doesn’t specify what happens to the site if you terminate the agreement.
- You’re paying for ‘hosting’ as a line item in an invoice, with no detail on what that covers.
None of those is unusual. All of them are fixable.
What a good managed hosting arrangement looks like
Agencies and hosting-first providers who do this properly share a few traits. The specifics vary, but the pattern is consistent.
You know what you’re paying for. The hosting line in your invoice or retainer separates out from other services. You can see whether you’re paying £30 / $40 a month for a shared environment or £150 / $200 a month for a dedicated VPS with managed backups. If hosting is bundled into a larger retainer with no breakdown, you have no way to evaluate whether the cost is reasonable, and no way to compare if you ever want to move.
You have access, even if you don’t use it. At minimum, you should have credentials for the hosting control panel (cPanel, Plesk, a proprietary dashboard) or a staging/production login. Many clients will never log in. That isn’t the point. The point is that access exists and you hold it. Some providers grant full root access; others offer a read-only monitoring dashboard. Either is reasonable. No access at all is not.
Migration is addressed in writing. The contract or service agreement states what happens if you leave. Does the provider give you a full site backup? Do they assist with migration to a new host, and if so, is there a fee? Is there a notice period, and does the site stay live during it? These are not hostile questions. Any provider confident in their service will have clear answers. The ones who get defensive are telling you something.
Backups are your safety net, and you should be able to verify they exist. Ask where backups are stored, how frequently they run, and how long they’re retained. Can you download a backup independently? If the only person who can restore your site is the same person you might be parting ways with, that is a single point of failure.
The questions to ask your current provider
If your hosting sits with an agency or third party, these five questions will tell you whether the arrangement is sound. None of them should produce an awkward pause.
- Where is the site physically hosted, and with which provider?
- Do I have login credentials for the hosting account or control panel?
- What does my hosting cost cover, separately from any design, development, or maintenance fees?
- If I terminate our agreement, what is the process for migrating my site elsewhere?
- Can I download a full backup of my site and database independently?
If the answer to questions two or five is no, fix that first. Everything else is a negotiation; those two are baseline.
When you should insist on owning the account directly
Some situations make direct ownership the better call, even if managed hosting would otherwise be simpler.
You have internal technical capability. If your team includes a developer or sysadmin who can manage a server, there’s little reason to pay someone else to sit between you and the provider. Buy the hosting, grant the agency deployment access, revoke it when the project ends.
Your agency relationship is project-based, not ongoing. An agency building your site and then handing it over should not also be the long-term gatekeeper of your hosting. That creates a dependency the project scope didn’t account for. If there’s no retainer, there should be no hosting lock-in.
You’ve been burned before. If you’ve already lived through a difficult separation where hosting access was used as a bargaining chip, you’ll want direct ownership going forward. That’s a rational response, not an overreaction. It happens often enough that nobody should be surprised by the request.
What to check right now
Run through this in five minutes. You need a browser and your latest invoice.
Check your invoice or retainer agreement. Is hosting listed as a separate line item with a clear cost? If it’s bundled, ask for a breakdown.
Try logging into your hosting. If you don’t have credentials, ask for them. If your provider says you don’t need them, that’s worth questioning. What happens if the relationship breaks down or the agency disappears?
Look for a migration or termination clause. If your agreement doesn’t address what happens when you leave, raise it now. It is much easier to add a clause while you’re on good terms than to negotiate one during a dispute.
Confirm your backups. Ask for a test restore or a downloadable copy. If you can’t verify backups exist independently, they may as well not.
As with domain ownership, do this while the relationship is good. The worst time to discover your hosting arrangement is inadequate is the day you need to leave it.