If you’re stuck between “shared hosting,” “VPS,” “managed WordPress,” “static hosting,” or “serverless,” you’re not alone. Most advice is either too vague (“it depends”) or too deep (“learn Kubernetes”). This is a one-page if/then cheat sheet to get you to a defensible choice.

Decision signpost pointing to hosting options icons

Pick the simplest thing that you can run confidently for the next 6–12 months.

The 60-second decision tree (start here)

Follow the first “if” that matches your project.

  • If it’s mostly pages (marketing site, docs, portfolio) → choose static hosting + CDN.
  • If it’s WordPress → choose managed WordPress (unless you truly need custom server control).
  • If it’s a small web app with a database → choose managed app platform (or PaaS) first; consider VPS only if you’re comfortable owning ops.
  • If traffic is spiky/unpredictable and you want pay-per-use → choose serverless functions + managed database.
  • If you need unusual system dependencies or long-running background jobs → choose VPS (or containers on a managed platform).
  • If you must meet strict compliance/audit requirements → start with managed offerings plus a documented setup; avoid “pet server” VPS unless you have operational support.

Option map: what each choice is “best at”

Abstract tiles representing different web hosting categories

  • Static hosting + CDN: fastest path to reliable, cheap, secure pages. Limited server-side behavior.
  • Managed WordPress: WordPress done for you (updates, caching patterns, backups). You trade some flexibility for fewer fires.
  • Shared hosting: cheapest “traditional hosting.” Can be fine for simple sites, but noisy-neighbor performance and outdated setups are common.
  • Managed app platform (PaaS): deploy an app, get routing, SSL, logs, basic scaling. Great middle ground.
  • VPS: maximum control. Also maximum responsibility (patching, hardening, backups, monitoring).
  • Serverless: functions and managed services. Great for event-driven and bursty workloads; can get complex if you force-fit everything.

A useful mental model: you’re not only buying compute. You’re buying (or declining) ongoing maintenance.

If/then by constraints (the questions that actually decide it)

These are the decision “levers” that usually matter more than raw traffic numbers.

  • If you don’t want to do security patching, then avoid VPS and lean static hosting, managed WordPress, or PaaS.
  • If uptime matters and you’re solo, then prefer managed options with built-in backups and easy rollback.
  • If you need a database, then decide whether you can use a managed database (usually yes). If you can’t, a VPS or specialized managed host may be necessary.
  • If your site must be extremely fast globally, then start with static hosting + CDN or edge caching in front of whatever you run.
  • If you need custom background workers/queues, then pick PaaS with worker support or a VPS. (Serverless can do this too, but it’s not always the simplest.)
  • If you expect bursts (launches, promotions), then choose static hosting when possible; otherwise serverless or a PaaS with autoscaling.

Four common scenarios (copy/paste decisions)

Four scenario cards connected by a simple flow

  • Scenario A: Portfolio / brochure site
    If it’s mostly text + images + a contact form, then choose static hosting + CDN. Add a form provider or a small serverless endpoint if needed.
  • Scenario B: Small business site on WordPress
    If you need plugins, themes, and an editor, then choose managed WordPress. Plan for updates and keep plugins minimal.
  • Scenario C: SaaS MVP (login + database)
    If you want to ship fast without becoming an ops person, then choose PaaS for the app + managed database. Revisit VPS only when you can name the specific limitation you’re hitting.
  • Scenario D: Event-driven tool (webhooks, cron, lightweight APIs)
    If the workload is spiky and you’re mostly reacting to events, then choose serverless functions + a managed datastore.

A quick smell test: if your “needs” are mostly guesses, pick the option that’s easiest to undo later.

Checklist: what to verify before you commit

Checklist clipboard with security, backup, and monitoring icons

  • Backups: automated, tested restore, and clear retention (not just “we back up”).
  • SSL/TLS: easy certificate setup and renewal.
  • Deploys: can you roll back quickly if something breaks?
  • Logs: can you view app/server logs without SSH gymnastics?
  • Monitoring/alerts: at least uptime + basic resource alerts (or platform equivalents).
  • Performance: caching story (CDN, page cache, object cache) fits your stack.
  • Data: where the database lives, how it’s backed up, and how you’d migrate it.
  • Access control: MFA available, least-privilege users, audit trail if needed.

Takeaway: the “good enough” default

If you’re unsure: choose static hosting for static sites, managed WordPress for WordPress, and a PaaS + managed database for most small apps. Reach for a VPS when you need control and you’re ready to own the maintenance.

That’s a real decision framework: match the platform to the maintenance you can consistently handle.