There's a moment in almost every web-design conversation where the question of hosting comes up, and the prospect's eyes glaze. They picked a host once. It was the cheapest one. Now it's a recurring charge that arrives in their inbox each month, the way insurance does. The trouble with treating hosting as a line item is that bad hosting compounds, and you don't notice the compounding until the year someone redesigns the site and you find out what's actually been happening.
What cheap hosting actually costs
The $4/mo shared host is a real product. It is also why we get a steady stream of inherited sites with the following list of problems:
- TLS that didn't auto-renew. The certificate expired three days ago and the site has been showing a browser warning to every visitor. Nobody noticed. The form submissions stopped, but the owner thought it was a slow month.
- No CDN. Every visitor outside the host's region waits 800 ms for the first byte. Lighthouse drops accordingly. Mobile rank slides.
- Backup hygiene that doesn't exist. The host backs up nightly. Restores take 72 hours and a support ticket that goes unanswered for two days.
- No security headers. No HSTS. No Content Security Policy. No Referrer Policy. Defaults that were “fine” in 2014 are now active liabilities.
- Noisy neighbors. You share a server with 400 other sites, one of which got compromised. Yours just got blacklisted by half the spam filters in the world.
- Cron jobs that don't run. The lead-routing script your developer wrote? It hasn't fired in six weeks. You're losing leads silently.
The bill for the cheap host is $48 a year. The bill for the consequences is uncountable.
What good hosting actually includes
When we say a site is on Catalyst hosting, here's what that means in practice:
- Edge-cached, global CDN. First-byte times under 100 ms from any major continent.
- Automatic TLS renewals. Certificates rotate before they expire. You don't think about it.
- Aggressive security headers. HSTS, strict CSP, frame-options, referrer policy — the whole list. Penetration tests pass on day one.
- Atomic deploys with instant rollback. A broken update doesn't leave the site half-broken. Worst case is a rollback that takes one click.
- Monitoring with paging. If the site goes down, we know. If a deploy fails, we know. If response times spike, we know.
- Backups that are tested. Backups that aren't restored from regularly are theatrical. Ours are tested.
Hosting as a product surface
The framing we want owners to absorb is that hosting isn't infrastructure; it's a feature of the site. Page speed is a feature. Uptime is a feature. Security headers are a feature. Backups are a feature. All of these are paid for, one way or another — either with the host's monthly fee, or with developer time, or with the cost of an outage.
You pay for hosting once, in cash, on a schedule you control. Or you pay for it forever, in incidents, on a schedule the universe controls.
Why $99 keeps coming up
Catalyst hosting and support is $99/mo. That number isn't arbitrary. It's what it costs us to run a real edge-cached, monitored, backed-up, security-headered, certificate-rotating environment for a small-business site, with an hour of support included every month. We don't make a margin on the hosting itself; we charge the same as it costs to deliver good. The bet is that if your site doesn't disappear, you'll send referrals.
When DIY hosting makes sense
Two cases:
- You have someone in-house who genuinely runs infrastructure. If you're a 50-person company with a dedicated ops person who likes managing hosting, by all means.
- The site truly doesn't matter. If you're a B2B operation whose customers never look at the marketing site, and lead-gen happens entirely on referrals, you can probably get away with anything.
Outside those two cases, hosting is a feature, and treating it like one starts paying back the day you flip the switch.
