Most people asking who should host my website think they are asking a technical question, and expect an answer involving server locations, load times and a comparison table with ticks in it.
That is not really the question. For a plumbing firm, a law practice, a clinic or an accountancy, the speed difference between one decent host and another is measured in fractions of a second and will not change a single enquiry. What will change your week is who picks up the phone when the site goes dark on a Tuesday morning, and whether you can actually get at your own domain when you decide to move on.
So this guide treats hosting as an accountability question. Who holds the keys, who is on the hook, and what it costs to have someone competent care about the answer. It is written for an owner who does not want to become the IT department and has no interest in learning what a DNS A record is.
The four arrangements service businesses actually end up in
Nearly every small and mid sized service business sits in one of four setups. Each has a different answer to the ownership and accountability question, and the differences matter far more than the brand name on the invoice.
One: self-managed hosting you bought yourself
At some point you signed up to a hosting company directly, probably because the price was low and the offer included a free domain for the first year. The account is in your name, the card on file is yours, and the renewal notices come to your inbox.
Self-managed hosting gives you the clearest ownership and the weakest support. Everything belongs to you, which is excellent, and everything is your problem, which is not. Budget hosts support a very wide range of customers at a very low price, which means the help you get is generic. They will confirm the server is running. They will not diagnose why your contact form stopped sending emails.
The failure mode is quiet neglect. Nobody is watching for software updates, backups are assumed rather than verified, and the renewal card expires eighteen months later when you have changed banks and forgotten the account exists.
Two: an all in one website platform
Squarespace, Wix, Shopify, GoDaddy’s builder and similar platforms fold hosting, security patching, backups and the editing tools into one monthly fee. There is no separate hosting account because hosting is not a separate thing. You are renting a slot on a system somebody else runs entirely.
For a lot of service businesses this is a sensible trade. The platform handles the boring infrastructure work properly and you will almost never see a long server level outage. The trade you have made is portability. Your design, page structure and content formatting live inside their system. You can export text and images. You cannot export the site.
Ownership of the domain is the thing to watch. If you registered it through the same platform, your domain and your website are now tied to one commercial relationship. That is convenient right up until the day it is not.
Three: your web designer or agency hosts it
This is extremely common and gets a worse reputation than it deserves. A designer builds the site, then hosts it on their own account, often a reseller plan carrying dozens of client sites. You pay monthly or annually, and they absorb the technical bits.
Done well, this is the best setup available to a non technical owner. You have one phone number for anything website related. The person answering knows how your site was built because they built it. There is no finger pointing between host and developer because they are the same person.
Done badly, it is the worst. The domain is registered to the designer. The hosting account is in their name. There is no documentation of what runs where. When the relationship ends, whether because you want to move, they change career, or something happens to them personally, you discover you do not own the thing you have been paying for since 2019.
The difference between the good version and the bad version is not the designer’s competence. It is whose name is on the accounts.
Four: you own the accounts, a specialist maintains the site
Here you hold the domain registration and the hosting account in your own name, usually with a decent managed host rather than the cheapest option available. A developer, agency or maintenance provider has access to that account and does the actual work: updates, backups, monitoring, fixing things when they break.
This separates ownership from labour, and it is where most businesses should end up once the site genuinely brings in work. You keep control of the assets. Someone else is responsible for keeping them healthy. If that someone else disappears, you have lost a supplier, not your website.
Who actually owns your domain, and why it decides everything
Your domain name is the only genuinely irreplaceable asset in this conversation. Hosting can be replaced in an afternoon. A website can be rebuilt. Your domain is attached to your email addresses, your Google Business Profile, every backlink anyone has ever given you, the letterhead, the van and the business cards.
Domains are registered to a registrant, and the registrant is the owner. Not whoever pays the bill, not whoever set it up, not whoever has been renewing it. If the registrant details name your web designer’s company, they own the domain, not you.
Even where the registrant correctly names your business, control usually follows the admin email address and the account login. If the admin contact is someone else’s email, transfer approvals and authorisation codes go to them.
Three things are worth confirming today, none of which require technical skill.
Where is the domain registered? You need the name of the registrar, not just "with the website people". Nominet maintains the register for .co.uk and .uk domains and will tell you who the registrant is. For other extensions, a public WHOIS lookup will show at least the registrar, though personal details are often masked for privacy reasons.
Whose name is in the registrant field? It should be your business, with your address. If it is not, fixing it is usually a straightforward change of registrant request, and it is far easier to do while everyone is still on good terms.
Which email address controls the account? Something your business controls permanently, ideally not tied to a single employee who might leave. Renewal warnings, transfer requests and security alerts all go there.
The same questions apply to the hosting account, with slightly lower stakes. If that account is in a supplier’s name, you cannot take a backup, cannot authorise a migration and cannot stop them switching the site off.
When the site goes down or gets hacked, who fixes it?
This is where hosting arrangements get tested, and where the marketing language on hosting websites is most misleading.
Uptime guarantees do not mean what they sound like
A 99.9% uptime guarantee is a billing promise, not a service promise. If the server goes down for an afternoon, the remedy written into the contract is typically a credit against your next invoice, worth a small fraction of a month’s fee. Nobody is obliged to ring you, and nobody is obliged to care that the outage landed during the one hour your radio advert was running.
Worse, uptime guarantees cover the server, not your site. If your homepage is broken because a plugin update went wrong, the server is up, the guarantee is intact, and the host’s answer is that this is not their responsibility.
Most hosting terms make security your problem
Read almost any hosting agreement and you will find security responsibility pushed firmly onto the customer. The host secures the infrastructure. You are responsible for your application, your passwords, your plugins and your content. Where a host offers malware scanning, it frequently scans and alerts rather than cleaning, or cleans at additional cost.
A hacked WordPress site is rarely a server breach. It is usually an out of date plugin, a weak administrator password, or a theme that stopped receiving updates two years ago. All three sit squarely in the customer’s responsibility column. The visible damage is a defaced page or a browser warning screen. The slower, more expensive damage is a domain flagged as unsafe in search results, and email from that domain starting to land in spam folders. Restoring both takes longer than cleaning the site.
The practical consequence: if nobody is being paid specifically to keep your site patched and monitored, nobody is doing it. Not the host. Not the designer who finished the build in 2021.
What good accountability looks like
You do not need a service agreement the length of a mortgage. You need clear answers to four questions, preferably written down.
Who do I contact when the site is down, and through what channel? How quickly will someone respond, and does that cover evenings and weekends? Where are the backups kept, how far back do they go, and has a restore actually been tested? Who applies security updates, and how often?
If the answer to any of those is a shrug, you have no accountability regardless of what you are paying. The shrug is the finding.
What this actually costs
Prices move and vary by provider, so treat these as orders of magnitude rather than quotes. The point is the shape of the difference.
Budget shared hosting sits at the low end, a few pounds a month, often discounted heavily for the first year and renewed at a noticeably higher rate. You are buying disk space and a server that is mostly up. Nothing about your site is being maintained.
All in one platforms charge tens of pounds a month and bundle hosting, security, updates and the editing interface. The price is predictable and the infrastructure is properly looked after. You are paying partly for convenience and partly for the fact that leaving is hard.
Managed WordPress hosting also lands in the tens of pounds a month at the small business end, rising with traffic and site count. The difference from budget hosting is real: staging environments, automated backups you can roll back from, core updates applied for you, and support staff who understand the platform rather than just the server.
Designer or agency hosting is sold as a monthly fee or annual bundle, and the number varies enormously because the scope does. Some of that fee is hosting cost. Most of it should be labour.
Maintenance or care arrangements sit on top of hosting and are priced on scope, from basic updates and monitoring through to content changes and a committed turnaround time.
The useful mental model is that hosting itself is close to a commodity. What you are really buying at every price point above the floor is somebody’s attention. A quote that looks expensive for "just hosting" may be fair for hosting plus a human who will fix things. A cheap quote buys you a server and nothing else.
Signs you are with the wrong host for your business
You do not need an audit to spot most of these.
You cannot name your host or your registrar. If nobody in the business can say where the website lives, nobody can move it, back it up or recover it in a hurry.
The renewal invoice goes to someone who left. Domains expire quietly, and the first sign is usually the email going down.
Your web address shows a security warning, or your dashboard lists a stack of pending updates nobody has touched in months.
You have never seen a backup. Not a promise of backups in a brochure. An actual file, or a restore that someone performed and verified.
You have to go through a third party to make a one line change, and it takes a week. That becomes a business problem the moment your opening hours change or a price goes out of date.
Something broke once and nobody was clearly responsible. The host said it was the developer. The developer said it was the host. You sorted it yourself at eleven at night. That is the clearest sign of all that you are with the wrong host, or at least the wrong arrangement.
What to check before you sign anything
Whether you are appointing a new designer, moving to a managed host or formalising something that has been informal for years, work through this list before you sign.
Insist the domain is registered to your business. Your company name, your address, an email address you will still control in five years. Any supplier worth working with will agree without hesitation.
Get the hosting account in your name too, or get written confirmation of what happens if the relationship ends. The minimum acceptable answer is a full export of the site and database, provided on request within a defined period, at no charge.
Ask who has administrator access and keep your own. You should hold an admin login to your own website even if you never use it.
Establish where backups live and how far back they go. Backups stored on the same server as the site are not backups. Ask for an off site copy, and ask when a restore was last tested.
Agree a response commitment in writing. Not a guarantee of perfection, just a clear statement of how quickly someone will respond to an outage, and during what hours.
Clarify what is included and what is billed separately. Security updates, content edits, plugin fixes and new pages are different things and should be described as such.
Ask what happens if they stop trading. A supplier who has thought about this has a straight answer. One who has not will find the question uncomfortable, which is also an answer.
So who should host your site?
If your website is essentially a brochure, your enquiries come mostly from referrals, and you have no appetite for technical admin, an all in one platform is defensible, provided you register the domain separately in your own name so you can walk away with it.
If your website generates real enquiries and the business would notice it being down for a day, you want the fourth arrangement: hosting accounts in your name with a capable managed host, and a named person or firm paid specifically to maintain and monitor the site.
If you have a web designer you trust and they want to host, let them, once the domain is in your own name and you have written confirmation that you can take an export whenever you ask.
The common thread is that the right answer to who should host my website is rarely about the host. It is about making sure that when something goes wrong there is a specific person whose job it is to fix it, and that when the relationship ends, you leave with everything you paid for.
If you would rather have a website that is maintained, monitored and genuinely yours, without becoming the person reading knowledge base articles at eleven at night, take a look at Nimble Dingo’s AI growth systems and we can go through how your current setup is put together.