What website hosting actually is, and who's supposed to pay for it

Hosting, in plain terms

The email says the site is suspended, and the first question that comes up is what that even means. Hosting is a rented space on a server — a computer, owned and run by a hosting company, that stores your site's files and serves them to anyone who types in your domain.

No hosting account, no live site. It doesn't matter how good the design is, or how much the build cost. Without a paid, active hosting account behind it, a website is just files sitting somewhere with nowhere to be shown to anyone.

Think of it like renting a shop unit. The unit doesn't care what's inside it or how nicely it's decorated. If the rent stops, the doors close, regardless of how good the shop itself is.

Files are stored differently for different kinds of sites, too. A simple brochure site might just be a handful of pages. A site with a store or a booking system also needs a database, sitting on that same server, holding everything from product listings to customer orders.

That's the whole concept. Everything else about hosting is really about who pays for that rented space and who controls the account it lives in.

Was hosting part of your build price, or a separate bill

Some web builds bundle a period of hosting into the upfront price. You pay once, and hosting is covered for a stretch before it becomes its own bill. Others treat hosting as entirely separate from day one, billed directly to you by a hosting company with no involvement from whoever built the site.

Both arrangements are normal. Neither one is automatically better. What matters is knowing which one you actually have, and what happens to the site once any bundled period runs out and the billing switches over to you directly.

Ask specifically what happens at that switchover point. Does a new bill just start arriving, or does someone walk you through setting up your own account before the free period ends?

Get the exact date in writing, too, not a rough estimate. A vague "sometime after launch" answer is how a switchover ends up getting missed entirely.

Whether hosting shows up inside a quote or gets billed separately is a question worth asking before you sign anything, not after the first renewal notice lands in your inbox.

Who actually holds the login to that account

This is a detail that turns into a real problem later if it's skipped now. If a designer set up hosting under their own account, in their own name, you don't control it. You're effectively a guest on someone else's infrastructure, even though the site itself is entirely yours.

If the account is in your name, with your own login, you control it. That's true regardless of who actually manages it day to day on your behalf.

There's a simple way to check: try logging in yourself, right now, with your own email address. If you can't, or if you don't even know which host the site is on, that's the answer.

This isn't about distrust. It's a basic piece of infrastructure your business depends on, and depending on it without access to it is a risk worth closing, regardless of how the working relationship is going.

Who owns the hosting account specifically, separate from who owns the design or the domain, is worth confirming directly rather than assuming it works out the way you'd expect.

What happens when a hosting bill lapses

A missed hosting payment doesn't take a site down instantly in most cases. Hosts commonly send a warning first, and a grace period follows it. There's usually a window before anything actually goes offline for good.

But if nobody's watching the inbox that warning lands in, or nobody knows the card on file expired months ago, the grace period runs out anyway. The site goes dark with no one noticing until a customer says something is wrong.

This is exactly why knowing who holds the account matters so much. A bill that lands in an old employee's inbox, or a designer's account you've since lost touch with, is a bill nobody's actually watching, month after month.

A calendar reminder ahead of the renewal date is a small thing that closes this gap. It costs nothing and takes a minute to set up once you know the date.

Shared hosting versus managed hosting

Shared hosting means your site sits on a server alongside many other sites, splitting the resources between them. It's inexpensive. It's also fine for most small-business traffic that isn't seeing huge spikes in visitors.

Managed hosting means a company actively monitors that server, applies security patches, and handles backups on your behalf, for a higher price. You're paying for someone else to be watching, continuously, instead of hoping nothing goes wrong.

Neither is wrong. They're different levels of hands-on support for different needs, different budgets, and different tolerances for risk.

Moving to a different host later

Nothing locks a site to one host permanently. Moving means copying the site's files and database to a new server and pointing the domain there instead. It's a task with real steps to get right, but it isn't a rebuild.

A move usually goes smoothly with a bit of planning. It goes badly when it's rushed under pressure, like right after an account gets suspended and there's no time left to do it carefully.

Where hosting fits into the wider set of tasks a site needs after it launches covers the bigger picture. And the domain itself carries its own separate renewal to track — the domain and SSL renewals that nobody remembers until they lapse is worth reading alongside this one.

More from the blog

All posts