Back to Blog
4 min read

What Are You Actually Paying For When You Pay for Hosting?

There's a line item with the word "hosting" on it, and most owners couldn't say what it buys or whether they can reach it. Here it is in plain terms, including the one part that's actually worth your attention.

Listening · What Are You Actually Paying For When You Pay for Hosting?

Your website is a pile of files, and those files have to sit on a computer that never turns off. Renting space on that computer is hosting. That is the entire concept.

Everything confusing about it comes from the fact that you never see the computer, never meet the company that runs it, and the bill just quietly renews. The thing your whole online presence physically sits on stays completely abstract, right up until the month the payment fails or the site slows to a crawl and it becomes very real.

A server is a computer that never sleeps

Your files, the pages and images and code, have to be somewhere switched on and connected every second, because a visitor can turn up at 3am and the site still has to answer. Your laptop can't do that. So the files live on a server instead: a computer built to stay on, sitting in a data centre, doing nothing but handing your site to people who ask for it.

When someone visits, their browser asks that server for your pages and the server sends them back, and that happens for every visitor, all day long. Hosting is what keeps your files on that always-on machine and keeps it answering. Stop paying and the files eventually come down and the site goes dark, the same as any rented space.

Why one site costs eight dollars and another costs two hundred

The range is wide enough that people suspect they're either overpaying or getting away with something. Usually it's neither. You're renting different amounts of room and different amounts of help, and it's worth knowing roughly what the tiers are.

At the bottom is shared hosting, often five to fifteen dollars a month. Your site sits on one machine alongside hundreds of others, all splitting its power. Fine for a small site with ordinary traffic, the way a hot desk in a shared office is fine for one person.

In the middle sits a VPS, usually twenty to eighty a month. It's still a shared machine, but you get a walled-off slice that's reliably yours, so a busy neighbour can't drag you down with them. A lot of real business sites live here.

At the top is a dedicated machine or fully managed hosting, from around a hundred dollars up. Now you're paying for room and for people: someone keeping the machine patched, watched, and fixed when it breaks. A store that can't eat an hour of downtime pays for that, and usually should.

The price itself isn't the thing to fixate on. What it's telling you is how much room your site needs and how much of the upkeep someone else is carrying.

"Managed" is the word that actually matters

Underneath the tiers is one distinction that touches your life more than the dollar figure, and that's whether your hosting is managed.

Unmanaged is renting an empty computer. It's cheap, it's yours, and everything that keeps it alive, the updates, the security, the fixing at 2am, is on you or on whoever you hire. Managed hosting costs more because the company does that upkeep for you. For almost every business owner, managed is worth it, because the alternative is that "maintain a server" quietly became your job the day you asked for a website, and it was never a job you wanted.

You usually don't pick this yourself, your developer does, and that's fine. It's just useful to know which one you're paying for, because it tells you who's on the hook when the machine needs attention. Unmanaged, with nobody hired to mind it, is a gap sitting there waiting to become an outage.

The one part worth checking

You don't need to understand any of this. You need to be able to get to your hosting, and that comes down to whose account it's in.

If the account is yours or your company's, you can move hosts, hand a new developer access, or fix a failed payment before it takes the site down. If it lives only inside a developer's account, your site is sitting on space you can't reach, and the day you need to reach it tends to be the worst possible day to find out you can't.

So the whole job is one small question to whoever runs your site: what company hosts us, and is the account in my name? You'll probably never log in, and probably never need to. Being able to is the point.

Share this article

Want to Work Together?

Let's discuss how I can help with your project.

Get in Touch