Managed Hosting Is a Product, Not a Hosting Bill

Managed hosting means someone else owns the day-to-day care of your site’s infrastructure, not just that the files sit on a server.

A plain hosting bill buys space and bandwidth (or a CDN). Managed hosting adds the operational layer: domain and DNS, SSL, deploys, security basics, monitoring, updates, and a person to call when something breaks. That is a different product from a cheap invoice.

A lot of clients confuse the two. They see a £0–£5/month static host, or a £10 shared WordPress plan, and assume the hard part is done. Then the SSL certificate fails to renew, DNS gets pointed at the wrong place, a plugin update takes the site down on a Friday, or nobody knows who owns the registrar login. Managed hosting is the system that keeps the site boring in the best sense: always there, always yours, and not your problem at 11pm.

What a hosting bill actually buys

On a static site, the raw hosting layer is often almost free. Files on a CDN. HTTPS. A deploy from Git. That is wonderful engineering.

It is not a complete product for a business owner.

The bill does not include:

• knowing which registrar holds the domain
• DNS records that survive email provider changes
• certificate renewal when something goes sideways
• a staging URL before a redesign hits production
• uptime checks that page someone who can fix it
• dependency updates that do not break the build
• a clear answer when a client asks “is the site safe?”

WordPress managed hosting sells a thicker stack (PHP, database, caching, WAF) and still leaves ownership gaps: who patches plugins, who tests after auto-updates, who restores from backup when a page builder eats the homepage.

Either way, infrastructure without care is unfinished work.

What managed websites actually cover

When I talk about managed websites on this site, I mean the layer above the host:

• Domain and DNS. Registration, renewals, records for the site, email, and verification tokens. No guessing which GoDaddy account from 2019 still owns .co.uk.
• Hosting that matches the stack. Static hosts for brochure sites. Sensible choices when you need a server. Not the cheapest plan that fails the first traffic spike.
• Security basics. HTTPS, sensible headers, no unnecessary admin surfaces, and a stack that does not invite weekly plugin CVEs for a twelve-page site.
• Monitoring. Knowing the site is up before a customer tells you it is not.
• Updates and support. Small content fixes, dependency bumps, deploy help, someone who can read a failed build log.
• Ownership for you. Repo access, handover notes, and a site you can leave with or keep managed. The product should not trap the client.

That is why a Starter plan at £100/month is not “hosting with a markup.” It is hosting plus domain care plus security basics plus a few hours of support so the site does not become a second job.

When clients should not think about infrastructure

Most founders, agencies, and local businesses do not want to become part-time sysadmins. They want:

1. A domain that resolves
2. A site that loads quickly
3. A way to change copy without breaking layout
4. Someone accountable when something fails

If that is the brief, they should not be choosing CDN plans, wrestling with DNS panels, or reading security advisories about core CMS remote code execution. They should be selling, hiring, or shipping product.

Self-managing makes sense when the team already has engineering capacity, a disciplined Git workflow, and appetite for the edge cases. Plenty of developers prefer that. It is a poor default for a non-technical owner who just needed a brochure site that works.

The failure mode of “we’ll figure hosting out later”

I see the same pattern repeatedly.

Launch on a free tier. Domain bought on a personal card. Deploy keys in one person’s laptop. No monitoring. Content changes by editing production directly or via a CMS nobody reviews. Two years later the original developer is gone, the domain is about to expire, and the business discovers that “the website” was a pile of accounts with no map.

Managed hosting as a product is the antidote: one relationship, clear responsibilities, and a site that survives staff changes.

How this fits a static-first stack

Static sites make management easier, not optional. You still need DNS, deploys, certificates, and a human who can ship a change. You just do not need PHP patching theatre for a marketing site.

That is the model I prefer for most brochure and agency work: Astro (or similar), content in Git, deploy on push, and managed care for clients who want the outcome without the ops. AI-assisted editing can sit on top of that when the team wants Claude as a CMS. The hosting product is still the guarantee that the pipeline stays healthy.

A simple decision rule

• You have a technical team and want maximum control. Buy the host yourself. Keep the repo. Own the pager.
• You need a site that stays online and you do not want to think about DNS. Buy managed websites as a product.
• You only want a hosting invoice. Fine for hobby projects. Risky as a business foundation.

Cheap hosting is a commodity. Reliability, ownership, and someone who answers when the site breaks are not.

If you want a site on a stack that stays cheap to run and a clear managed layer so you can ignore the infra, look at web development or get in touch. Happy to say whether Starter care is enough, or whether you need deeper ongoing ownership.