dropto.run vs Cloudflare Pages
The same network underneath. The difference is whether you assemble it yourself.
We run on Cloudflare
Sites here are served from Cloudflare's edge too. Saying otherwise on a page like this would be the fastest way to lose a reader who checks a response header.
Cloudflare now points new projects elsewhere
Their own Pages documentation opens by saying Workers supports most Pages use cases and to start new projects with Workers.
One is parts, the other is a product
Pages will take a dropped zip too. What is sold here is everything after it: versions, passwords, expiry, a reader for documents, an agent interface — each of which is yours to assemble there.
When Cloudflare Pages is the better choice
- ·You are building on Workers anyway. KV, D1, R2, Durable Objects and Workers in one account is a platform this does not try to be.
- ·Their free tier is wide. 500 builds a month, 20,000 files a deployment and 100 custom domains a project, at no cost.
- ·You want control of every header and route. `_headers` and `_redirects` are yours to write, and a Worker in front of the assets can do anything you can code.
- ·You already live in wrangler. If deploying is one command you have typed a hundred times, a dashboard is not an improvement.
Line by line
Their figures were read from their own pages on 15 September 2026. Ours are the ceilings the server enforces, which is why the rows that would be numbers here point at the plans instead of repeating them.
| dropto.run | Cloudflare Pages | |
|---|---|---|
| Folder or zip to a live link | Yes | Yes — dashboard upload, wrangler or Git |
| Cloudflare account needed | No | Yes |
| Configuration file needed | No | Often — wrangler, _headers, _redirects |
| Putting an earlier version back | One click, live in under a minute | Roll back to an earlier deployment |
| A folder of Markdown served with a sidebar | Yes — no build, no theme | Through a static-site generator you run |
| Password on a site | From the Starter tier | Cloudflare Access — sign-in, and previews by default |
| Largest single file | Read from the plans table | 25 MiB per asset |
| Files in one publish | Read from the plans table | 20,000 free · 100,000 on paid plans, opt-in |
| Bandwidth counted against you | No | No |
| Builds counted against you | No build to count | 500 a month free, 5,000 on Pro |
| Reviewers comment on the page itself | On plans with comments: pinned on the live site, reviewers sign in to Drop2Run | Not documented |
| Publishing from a script or an agent | CLI, API token, MCP server | wrangler, API, Git integration |
Which rows are here is our choice, which is what every comparison page does. What is in them is not: each figure above came from their Pages limits and their note about starting new projects with Workers. If one is out of date, tell us and it is corrected with the date on it.
Nothing counts your readers.
Files are served from the edge out of storage where egress costs nothing, so there is no traffic figure for your pages to pass on — and no plan here on which one appears. What is bounded is publishing, and the calls a site sends on to your own API, and those figures are read from the same table the server enforces. Every number below comes from the API at page load, not from this page. All of them, side by side →
What Cloudflare Pages counts
- ✕Builds — 500 a month on the free plan
- ✕Assets — 20,000 a deployment, 25 MiB each
Read 15 September 2026.
What is counted here
- ✓New or changed files, against a monthly and a daily budget. Unchanged files are reused rather than uploaded again, so publishing the same site twice costs almost nothing.
- ✓Storage, counting each file once however many versions hold it. Republishing the same files adds nothing.
- ✓Calls a site sends to your own API, against a monthly allowance. Only where a site routes
/api/*to an API of yours; a page that does not never has one counted. - ✕Never visits, bandwidth, page requests or build minutes. There is no build, and traffic to your pages is neither billed nor throttled.
2,000 files a publish, free
With an account and no card. A folder of documents meets the file count long before it meets the bytes.
50 MB a publish, free
The size of one upload. What the account holds in total, across sites and versions, is a separate ceiling.
No limit on sites, free
Each on its own subdomain. What bounds an account is its storage, not how many sites it splits that into.
$5 / month with your own domain
Starter is the cheapest tier here that carries a custom domain and its certificate. On Cloudflare Pages: free, or from $5 a month on Workers Paid, on Free.
No traffic tier, at any price
There is no plan above this one that lifts a bandwidth cap, because there is no bandwidth cap to lift.
Infrastructure or a product
Everything past serving the files is what is sold here: versions kept and promoted in a click, a password, an expiry date, a QR code, traffic figures that identify nobody, a reader for a folder of documents, and an MCP server so an agent can publish what it just wrote.
None of that is impossible on Pages. All of it is work, and it is work that has to be maintained by whoever did it.
Cloudflare sells the pieces, and the pieces are excellent and cheap. If you are already in that account, adding a static site to it is a small step and the free tier is wide.
It also means the account, the CLI, the configuration and the upgrade path are yours to hold — including the part where their own documentation now tells new projects to start with Workers instead.
Looking for a Cloudflare Pages alternative
It is worth saying which part you are replacing, because it is not the network: files published here are served by a Cloudflare Worker out of R2, so a visitor is answered from the same edge either way. What changes is who assembles it. There is no account of theirs to hold, no wrangler, no `_headers` and `_redirects` file to get right, and no build budget — and their own documentation now tells new projects to start with Workers rather than Pages, which is a thing to know before starting one on Pages.
If you are already in that account every day, or you need Workers, KV, D1, R2 or Durable Objects beside the site, stay: those are the reason Pages is where it is, and none of them exists here. What is sold here is the layer above the serving — versions, a password, an expiry date, traffic figures that identify nobody, a reader for a folder of documents, an MCP server — which on Pages is work somebody has to do and then maintain.
Moving over
Whatever you publish there is already a folder, and a folder is what this takes.
- 1
Take the directory you deploy
The one you point wrangler at. Nothing about how it is produced has to change.
- 2
Drop it, or publish from CI
The same folder, either dragged in or sent by the CLI from the job that builds it.
- 3
Move the domain when you are ready
Point the DNS record here and the certificate is issued for you. Your pages.dev address keeps working until you delete the project.
Questions
You run on Cloudflare. Why not just use Pages?
If you are comfortable with an account, wrangler and a configuration file, that is a completely reasonable choice, and the free tier is wide. What is sold here is the layer above: version history, passwords, expiry, a documents reader, and publishing from an agent — all of which you would otherwise build.
Is it the same network?
Yes. Pages published here are answered from Cloudflare's edge, so a visitor is served from the same places yours would be.
Is Cloudflare Pages going away?
Not as far as they have said. What they have said is that Workers supports most Pages use cases and that new projects should start with Workers, which is worth knowing before starting one on Pages.
What about Workers, KV and D1?
Nothing here replaces them. This hosts static files and folders of documents; an application with state belongs on Workers.
Try it with the folder you already have.
No account and no card to publish. Sign in and the site stops expiring.
Cloudflare Pages is a trademark of its owner. This page is not affiliated with or endorsed by them, and every figure about their service was read on 15 September 2026.