Static Site Hosting

For the last decade, "deploying a website" has moved from "rent a VM, run nginx" to "push to git, your platform takes care of the rest." Static site hosts handle building, deploying to global edge, preview environments per pull request, environment variables, edge functions, and SSL — all for free at small scale.

This is distinct from Object Storage + CDN (you assemble the pieces) — static hosts are the opinionated platform version.

What "Static Site Hosting" Means Now

The term is misleading — modern "static" hosts also run server-side code at the edge:

A modern "static" host is closer to a frontend platform — you build a Next.js / SvelteKit / Nuxt / Astro site and it deploys with the right runtime split between static, edge, and serverless.

The Players

For new projects in 2026:

• Next.js heavy → Vercel (best integration) or Cloudflare Pages (cheaper).
• Framework-agnostic, simple pricing → Netlify or Cloudflare Pages.
• OSS / docs site, free → GitHub Pages or Cloudflare Pages.
• Self-host requirement → Coolify or plain CDN + Object Storage.

What You Get Out of the Box

Push to git:

git push origin main
  │
  ▼
Platform detects framework (Next.js, Nuxt, Astro, ...)
  │
  ▼
Builds in a CI environment (yarn, pnpm, npm — auto-detected)
  │
  ▼
Deploys static assets to global CDN
Deploys server functions to edge / serverless runtime
  │
  ▼
Atomic activation: new URL serves new version; old version available for rollback

The default state for a new project is a free site, on a .vercel.app / .pages.dev / .netlify.app subdomain, with HTTPS, auto-deploying from main.

Preview Deploys (The Real Magic)

Open a PR → platform builds it → unique URL pointing at that branch's build.

main         → https://myapp.com (production)
PR #42       → https://myapp-pr-42.vercel.app (preview)
feature/foo  → https://feature-foo-myapp.vercel.app (preview)

This single feature transformed frontend dev. Designers and PMs can review changes in a real browser before merge.

Some platforms (Vercel, Netlify) post the preview URL as a PR comment automatically.

Frontend Framework Conventions

Most modern frameworks integrate with these platforms:

The frameworks know how to compile for each platform's runtime (Vercel's Lambda, Cloudflare Workers, Netlify Functions). You don't write platform-specific code in most cases.

Learning Path

When NOT to Use a Static Host

Honest cases:

• Backend-heavy app with significant Node/Python/Go service work — a static host's serverless functions get pricey or limited. Use Render, Fly, Railway, or proper Kubernetes.
• Stateful workloads (databases, queues, WebSocket servers) — static hosts don't do this.
• Strict data residency that platforms don't support.
• Need full Linux container — Render / Fly / your own infra.

For pure frontend + small API endpoints, static hosts win. For "I have a real backend service," look at full-stack platforms or PaaS.

Cost Considerations

The free tiers are generous; the scaling cost can surprise.

Cloudflare Pages has free egress — the biggest cost item for high-traffic sites. Vercel's "fast pretty" comes at a premium.

For mid-scale sites: Cloudflare Pages is dramatically cheaper if you're not deep in Vercel-specific features.