Seven hosts, and where each one wins.
Every page here picks the rows we win on — so does everybody else's — and then says plainly what the other service does better. Nothing on any of them was read from its owner's pages earlier than 15 September 2026, each page prints its own date, and every figure is linked so you can check it rather than trust it.
- Drag-and-drop hosting
dropto.run vs Tiiny Host
The same drag-and-drop. They count five things about your site; here nothing counts your readers.
Where they win — You are sharing one PDF.
- Static hosting from a CLI
dropto.run vs Surge
Surge is a command. This is a command and a page — the same publish, from a browser, for somebody who does not have a terminal open.
Where they win — You publish from a terminal and want that to be free.
- Hosting from a repository
dropto.run vs GitHub Pages
GitHub Pages wants a repository. This wants a folder.
Where they win — The site belongs to a public repository.
- Platform with a build pipeline
dropto.run vs Netlify
Netlify prices a deploy and a gigabyte in credits. Here neither is counted.
Where they win — Your site needs to run code.
- Framework platform
dropto.run vs Vercel
Vercel's free plan is for personal projects only. A static folder should not need permission.
Where they win — You are shipping a Next.js app.
- Infrastructure you assemble
dropto.run vs Cloudflare Pages
The same network underneath. The difference is whether you assemble it yourself.
Where they win — You are building on Workers anyway.
- One-page site builder
dropto.run vs Carrd
Carrd builds the page for you. This publishes the page you already have.
Where they win — You do not have a site yet.
Four of the seven count your readers. None of the counting happens here.
Visits, bandwidth, requests, credits — Tiiny Host, Netlify, Vercel and GitHub Pages each bound at least one of them. Cloudflare does not count your readers, only your builds; it sells the parts rather than the product. Surge counts nothing it publishes a figure for, and Carrd counts sites rather than visits — it bounds how many things you can have, and each is one page. Files here are served from the edge out of storage where egress costs nothing, so there is no traffic figure to pass on and no plan on which one appears.
- ✓Publishing is what is bounded, by how many new or changed files you upload in a month. Unchanged files are reused rather than sent again.
- ✓The ceilings are published and enforced from one table. The pricing page reads the same API the server checks against, so what you are shown and what refuses you cannot drift apart — which is also the difference from a service that says "unlimited" and publishes no figure: an unpublished limit is one you find out about.
- ✕No build minutes, because there is no build. What goes up is the folder you already produced, which is also why there is nothing here for a site that needs rendering per request.
Leaving one of them in particular
Each page below is written for the question in its own link — what the service does well, what it counts, and who should stay where they are.
- ·Tiiny Host alternative — Drag-and-drop hosting.
- ·surge.sh alternative — Static hosting from a CLI.
- ·GitHub Pages alternative — Hosting from a repository.
- ·Netlify alternative — Platform with a build pipeline.
- ·Vercel alternative — Framework platform.
- ·Cloudflare Pages alternative — Infrastructure you assemble.
- ·Carrd alternative — One-page site builder.
Or skip the reading.
Drop the folder you were going to compare hosts for. No account, no card, and the link comes back when the upload finishes.