Hosting & CDN

Website hosting and content delivery: compare deployments, previews, domains and static or server-rendered requirements.

Explore the directory

All categories20 →
10 results
Editorial top 3

Our order reflects the workflows described below and public product information. It is an editorial judgment, not a performance benchmark.

Netlify — Official website#2Editorial pick

Netlify connects site builds with publishing and change previews, fitting frontend teams organizing the release of pages within a single workflow.

An alternative for teams seeking a convenient static-site and preview workflow.

Hosting & CDNHosting platform
Vercel — Official website#3Editorial pick

Vercel focuses on deploying web applications and frontends, fitting teams connecting code changes, previews and production hosting within one release process.

A fit when Next.js integration and the frontend development workflow are central.

Hosting & CDNHosting platform

More products to explore

GitHub Pages — Official website

GitHub Pages publishes a static website from a repository, fitting documentation and smaller projects whose content and change history already live alongside the code.

Render — Official website

Render combines web-service hosting with related infrastructure, fitting projects that extend beyond a static website and require a backend.

Railway — Official website

Railway deploys applications alongside services and databases, fitting teams seeking a short path from a repository to a working project.

Firebase Hosting — Official website

Firebase Hosting targets static websites and single-page applications. Preview and deployment through the Firebase CLI connect hosting with the development workflow.

bunny.net — Official website

bunny.net connects content delivery with edge storage and optimization, fitting sites whose images, files or media need a dedicated delivery layer.

Fastly — Official website

Fastly is an edge platform for delivering and protecting digital products, fitting technical teams that need a managed layer between the application and user requests.

Common ownership disclosed. Featured placement is commercial, not an independent score. Methodology

What to check before you start

Hosting decisions start with the application’s runtime requirements. A static landing page and a server-rendered application can use different deployment paths and resources. Cloudflare Pages, Netlify and Vercel are included as real publishing options; listing them does not migrate this directory away from its existing Cloudflare project.

01

Runtime fit

Confirm the framework output, server functions and external connections your application needs. Build a small production-like page and verify the required behavior before changing providers.

02

Publishing workflow

Test preview, production promotion, custom domains and rollback. Keep environment configuration and private credentials separate from the publicly delivered static files.

03

Usage and limits

Estimate builds, requests, bandwidth and server execution from your workload. A no-cost starting tier is not a promise that every feature or future traffic level will remain free.

↗

Compare with context

Start with official sources, confirm the terms and run your own bounded test.

Methodology→