A related Q: why are their products so popular? I get why CDN/DDOS protection is but what about everything else? I have never ever found a use for stuff like Workers. (Sincerely asking, not dismissing them as useless)
You also don't pay for actual data transfer, so the billing is overall simpler - AWS and GCP have similar per-request compute options, but every part of the platform has extra fees (like per-gb data transfer billing, sometimes you need a VPC to interconnect services, secrets being an extra charge, etc).
however now i just have agent do it with CLI and that works well and I don't have to find the secret link
Running your stuff, even private stuff, through a tunnel is great so that you don't have to expose your VPS' IPv4.
CDN, DDoS protection, excellent DNS hosting features, web monitoring, web analytics, advanced web and service filtering and blocking, zerotrust networking / vpn options, a solid API that works great with terraform, tons of other stuff.
(Actually multiple, one for each domain)
Actually if you even search "static sites" now it just takes you to Workers & Pages in the dashboard.
Docs:
https://developers.cloudflare.com/workers/
Free plan limits:
https://developers.cloudflare.com/workers/platform/limits/#a...
On the Pages docs website there is even a header that encourages you to use workers (though I don't think you're given a choice at this point), like pages in general are being deprecated.
---
Are you sure you want to use Pages?
Workers supports most Pages use cases and offers a broader feature set. It is Cloudflare's primary platform for building applications. Start new projects with Workers.
---
https://developers.cloudflare.com/pages/
---
Edit: Found this!
https://news.ycombinator.com/item?id=46037452
"We are not sunsetting Pages. We are taking all the Pages-specific features and turning them into general Workers features -- which we should have done in the first place. At some point -- when we can do it with zero chance of breakage -- we will auto-migrate all Pages projects to this new implementation, essentially merging the platforms. We're not ready to auto-migrate yet, but if you're willing to do a little work you can manually migrate most Pages projects to Workers today. If you'd rather not, that's fine, you can keep using Pages and wait for the auto-migration later."
"Now that Workers supports both serving static assets and server-side rendering, you should start with Workers. Cloudflare Pages will continue to be supported, but, going forward, all of our investment, optimizations, and feature work will be dedicated to improving Workers. We aim to make Workers the best platform for building full-stack apps, building upon your feedback of what went well with Pages and what we could improve."
Pages are now essentially deprecated and Workers have dedicated ways to host static files and are the recommended path going forward for static and dynamic websites
> Workers supports most Pages use cases and offers a broader feature set. It is Cloudflare's primary platform for building applications. Start new projects with Workers.
And I see that the assets[0] wrangler config key can also be setup so that hits it prefers hitting static files, so that they can still be served in a free and unlimited manner.
Although I imagine an official deprecation probably is a long ways off, and if they do it I hope they'd handle a large-scale migration for each page to its own worker with assets preserved.
0: https://developers.cloudflare.com/workers/static-assets/bill...