Pages pricing for static React website
Hello. Today, I found out that I can use Cloudflare pages to host static website for free.
I am long term Cloudflare DNS user and I know that there is no catch in there in terms of free DNS and proxying for my websites, but I am not sure why exactly Pages are also free? I am planning to host a static React based website and my question is if the Pages Free tier is really free for unlimited amount of requests in my case?
Thanks!
4 Replies
Yes, you get unlimited static requests with Pages, no bandwidth limit or anything. You're only limited by builds (500 per month for free) and Custom domains (100 on free per project). There is also a limit of 20k files per deployment, and 25 MiB max file size (for each file, individually)
Pricing page is here: https://pages.cloudflare.com/
As for why, well Github Pages is free too for public repos so it's not anything too new.
Pages is generous though. One factor may be KV - the backing storage of Pages, is more efficient the more requests it gets. Your files are cached in each DC rather then having to go back to one of the two central stores, so the more requests, actually more efficient for CF
Cloudflare Pages
Build your next application with Cloudflare Pages
Thats amaying 😄 Thanks 😉
One more question: Are the Pages stable? By that I mean, can I deploy it there without worry about having some large downtimes?
Its not an enterprise website (obivously :D), but it is somewhat important to have the site up and running 24/7/365
For the actual asset serving, pretty much the only time it's been down was when the entirety of CF was having issues
Pages when serving assets is really just Workers + KV glued together, that's what it uses under the hood
KV has two central stores and cache
There was that incident in November where Cloudflare lost one of their core datacenters and had issues for ~2 days, and Pages sites were completely uneffected. Albeit you couldn't push any updates, there was no interruption in service (and since then they've launched an effort to not be so reliant on a single core