Should you host client websites yourself?
Should a one-person AI agency host client websites? The work it adds, when it suits a care plan, when the client should hold the account, and the exit.
A web designer looks after eight small business websites. Early on, hosting them all in one account was the easy choice: one bill, one login, one place to run updates. She adds the cost to each care plan and thinks no more about it.
Then a hair salon decides to move on. The owner is polite and asks for "her website". The site is in the designer's hosting account, the domain is in the designer's registrar account, and the salon's email runs through both. What should have been a friendly goodbye becomes a week of careful unpicking.
Should you host client websites yourself? You can, and for some agencies it works well, as long as you treat hosting as a service you've written down: who pays, what you look after, and what the client gets if they leave. The domain should stay in the client's name either way. For many one-person agencies, the simpler option is for the client to hold the hosting account while you're invited in to manage it.
What does hosting a client's website involve?
Hosting is the paid space where the website lives. Holding it for a client means you become responsible for more than the bill:
- Keeping the site up, and being the first call when it isn't, even on a Saturday.
- Updates and backups, on a schedule, with a backup taken before each update.
- Security certificates, the files behind the padlock in the browser. Let's Encrypt, a free certificate provider, announced in December 2025 that it will cut its certificates from 90 days to 45 days by 2028, alongside the rest of the industry. Automatic renewal handles this on most hosts, but someone has to check it's working.
- Renewals and payments, so an expired card doesn't take eight businesses offline at once.
- Moving a site out when a client leaves.
None of this is hard. All of it is ongoing. The question is whether you want it on your list every month.
It helps to picture a bad week, not a normal one. A host has an outage on the Friday before a bank holiday. Three clients text you at once, one of them a restaurant with a full booking sheet. You can't fix the host's outage, but you are the person they call, and you're the one who has to explain. If that picture sounds manageable, hosting may suit you. If it sounds like the week you'd least want, that's useful to know before you offer it.
What are the pros and cons?
Here's a plain comparison of the two common setups:
| You host the site in your account | The client holds the account, you manage it | |
|---|---|---|
| Setup | Fast; you already have the account | Slower; the client has to sign up and invite you |
| Monthly bill | Yours; you pass it on in the care plan | The client's, paid directly |
| Updates and checks | All sites in one place | One login per client |
| When the site goes down | You're the first call | You're still called, but the client can reach the host too |
| When the client leaves | You copy the site out and help them move | You remove your own access |
| If you're ill or away | Every site depends on you | The client can get help elsewhere |
Neither column is wrong. The first suits a designer who wants to sell hosting as part of a care plan and is happy to carry the responsibility. The second suits a designer who wants the client to be able to carry on without them.
When does hosting it yourself make sense?
It tends to work when most of these are true:
- You look after enough sites that one account genuinely saves time.
- Your care plan already includes updates, backups and checks, so the hosting work is priced in.
- You're ready to answer when a site goes down, and you've said how quickly you'll respond.
- Your clients would rather have one bill from you than an account of their own.
If you choose this, write it into the care plan as its own line. A service recipe is a simple way to set it out: what you host, what you check each month, how quickly you respond, and what's not included.
When should the client hold the account?
When the site is central to the business and the owner would struggle if you disappeared: a dentist's booking page, a café's ordering page, a trades business that gets its jobs through the contact form. Also when the client already has an account with a host they're happy with, or when you'd rather not be the person called at 7am on a bank holiday.
With the account in the client's name, you're invited as a user and can do everything the care plan needs. It's the same idea as being added as a manager on a Google Business Profile instead of owning it: you get the access you need, and the business keeps the account. Owner-held accounts explains the principle in a paragraph you can paste into an offer.
Why should the domain stay in the client's name either way?
Because hosting can be moved and a web address can't be replaced without cost. Customers, printed menus, van signs and years of emails point to it.
Moving a domain also takes time when it's in the wrong hands. ICANN's transfer policy, which sets the rules for moving common domains such as .com between registrars (the companies domains are bought through), lets a registrar refuse a transfer in the first 60 days after a domain is registered or moved, and after a change of owner. A domain registered in your name, discovered on the day a client leaves, can take weeks to sort out. Registering it in the client's name from the start avoids that.
How do you write the exit down?
Before you host anything, agree in writing what happens when either of you ends the arrangement. A web design contract template in plain words should cover:
- What the client gets: a full copy of the site's files and database, in a form another host can use.
- How long you'll keep it running after notice, so they have time to move.
- What help you'll give, and whether it's included or quoted first.
- Who owns the domain and email, and confirmation that both are already in the client's name.
Then keep your own records in a state you could hand over tomorrow. If you ever change the tools you run the agency on, the same thinking applies to you; see how to export client data from a CRM without losing the history.
So, should you host client websites yourself?
Host them if you want to sell hosting as part of a care plan, you've priced in the work, and you've written down the exit. Otherwise, let the client hold the account and ask to be invited in. Either way, keep the domain in the client's name, and decide before the first site goes live, not on the day someone leaves.
Where Volant fits
Volant works on the same rule for your own agency: your phone numbers, bots and accounts stay yours, and so do their bills. The ownership page shows what that means in practice, account by account.