“Affordable” hosting is not one number. A ZIP site can be cheap to publish but costly to run if the host meters bandwidth, requests, build minutes, seats, server execution, or credits. Compare the cost model and the limits that apply to your traffic—not a headline price copied from an old plan table.
Classify the site first
A brochure site made of HTML, CSS, JavaScript, and images has different needs from a portal with logins and a database. For static sites, compare asset delivery, custom domains, HTTPS, storage, deploy workflow, and support. For application code, also price the runtime, database, background work, and security controls.
Four pricing models
| Model | How it works | Check carefully |
|---|---|---|
| Flat plan | One monthly or annual fee includes defined limits. | Projects, uploads, transfer, visitors, and collaborator caps. |
| Allowance plus overage | A plan includes usage, then charges for extra transfer, requests, compute, or storage. | Automatic overages and the measurement unit. |
| Credits | Several activities consume a shared monthly balance. | How deployments, requests, bandwidth, and functions turn into credits. |
| Pay as you go | Billing follows direct resource use. | Bot traffic, traffic spikes, and available spend controls. |
Use official sources immediately before purchase
Prices change. Vercel’s current pricing page describes its plan prices and included usage, while its pricing documentation explains that infrastructure may be measured by data transfer, requests, and compute. Netlify’s pricing page explains its credit model, including production deploys, bandwidth, and web requests. Cloudflare’s Pages documentation distinguishes static asset requests from Functions, which use Workers quotas. These are examples of why “free” or “from $X” is incomplete information.
Estimate your own month
- Measure a representative page in browser DevTools → Network.
- Multiply monthly page views by average transferred bytes, then add downloads and media.
- Count requests per page; every image, CSS, font, and script can be a request.
- List requirements such as domains, history, private projects, analytics, and team access.
- Read what happens after each limit and save the terms you accepted.
Example only: 20,000 views × 1.2 MB transferred per page is approximately 24 GB before caching effects. Use the measurements from your own site rather than this illustration.
Keep cost predictable
- Optimize large images before upload and serve appropriate dimensions.
- Keep source maps, backups, and private files out of public deployment unless required.
- Enable billing alerts or a spending cap where the provider offers one.
- Review traffic after campaigns, not only at invoice time.
- Do not choose a static plan for an application that needs a database only because its first month looks cheaper.
The most affordable host is the one that fits the site’s requirements, publishes clear limits, and does not create a surprise when visitors arrive.