Shared, VPS, managed, or static: choosing hosting without overpaying
Hosting decisions get made backwards. Someone picks a plan from an ad, then discovers their site needs something the plan cannot do, or pays for a server nobody administers. Start from what the site does, and the category picks itself.
The four categories
| Type | You manage | Fits | Main risk |
|---|---|---|---|
| Static / CDN hosting | Files only | Blogs, brochure sites, docs, landing pages | Cannot run a traditional CMS or database |
| Shared hosting | Your app and content | WordPress sites, small stores | Noisy neighbours, dated software versions |
| Managed platform | Your code | Framework apps, teams shipping often | Cost scales quickly; plan terms restrict commercial use on free tiers |
| VPS / cloud server | Everything, including security patches | Custom apps, specific software needs | You are now the sysadmin, forever |
Static hosting is underrated for content sites
If your site is articles and pages, static hosting on a CDN is faster, cheaper, and less breakable than anything else. There is no database to corrupt, no plugin to exploit, and no PHP version to upgrade at midnight. Free tiers are often genuinely sufficient for a publication, and forms or newsletter signups can run through a single small serverless function.
The tradeoff is real: no plugin ecosystem, no clicking around a familiar admin panel, and content usually lives in files or a headless CMS. If a non-technical person must publish daily without help, weigh that seriously.
Shared hosting: what the cheap plan actually means
Shared hosting is a real machine with many customers on it. That is not automatically bad, and the price is honest about what you are getting. What matters is the fine print rather than the headline rate:
- Renewal price versus first-term price. The advertised figure is usually a multi-year introductory rate. Check what year two costs.
- “Unlimited” storage and bandwidth. Bounded in practice by inode limits, CPU throttling, and a fair-use clause. Find those limits before you rely on them.
- Backups. Are they included, how far back, and can you restore one yourself without a support ticket?
- Software versions. A host stuck on old runtimes will eventually block a security update you need.
- Migration help. Free migration is worth more than a free domain.
When a VPS is the right answer, and when it is a trap
A VPS makes sense when you need specific software, persistent processes, or control that shared hosting will not give you, and somebody on your side will keep it patched. That last clause is the whole decision. An unmaintained VPS is a security incident on a delay.
Be honest about the true cost: the monthly server fee plus backups plus monitoring plus the hours someone spends on updates, TLS certificates, and the occasional 3 a.m. disk-full alert. Compared honestly, managed hosting is often cheaper.
Read the commercial-use terms before you deploy
Several excellent platforms restrict their free tiers to non-commercial personal projects. A site with ads, affiliate links, sponsors, or checkout is commercial. Nobody wants to discover this after building an audience. Check the current plan documentation for the platform you are considering, and budget for the eligible paid tier if that is what your use case requires.
Decision shortcuts
| Situation | Start with |
|---|---|
| Content site, technical owner | Static hosting on a CDN |
| WordPress, non-technical publisher | Reputable shared or managed WordPress hosting |
| Small store | Hosted commerce platform, or managed hosting with real backups |
| Framework app, frequent releases | Managed platform on an eligible paid plan |
| Specific software or compliance constraint | VPS, with a named person responsible for patching |
| Traffic is spiky and unpredictable | Anything that scales without you resizing a server |
Things worth paying for
- Backups you have personally tested by restoring one.
- A CDN in front of the site, which fixes latency for distant visitors more cheaply than a bigger server.
- TLS certificates that renew automatically, so nobody has to remember.
- Support that answers in hours when the site is down.
Things not worth paying for early
- More CPU and RAM than your traffic uses. Measure first.
- Bundled SEO or marketing add-ons sold with hosting.
- Long multi-year commitments to a provider you have not run in production for a month.
- A dedicated server because a plan page implied you needed one.
Own the parts that are hard to replace
Register the domain somewhere you control, independently of the host. Keep content in files you can copy. Keep the subscriber list exportable. Hosting is a commodity you should be able to change in a weekend; your domain, content, and audience are the actual assets.
No company paid for placement in this article. Verify current prices and terms with each provider before buying.