3 ms·

I use both pages.dev and netlify.com: pages.dev, even in open beta, is a fantastic product if it suits all your needs, but the limitations [0], if you hit them,

I use both pages.dev and netlify.com: pages.dev, even in open beta, is a fantastic product if it suits all your needs, but the limitations [0], if you hit them, are a dead-end and there are no ETAs as to when some of those limitations would be addressed. That is not the case with netlify.com which boasts a myriad of features, is equally as fast, production-ready, and competitively priced. With pages.dev, I believe, you pay per every domain you host, whilst with netlify.com, there's no cap on number of domains per account, though they do charge for bandwidth (unlike pages.dev). Workers Sites [1] is a viable alternative and I quite prefer it over pages.dev. [0] https://developers.cloudflare.com/pages/platform/limits https://developers.cloudflare.com/pages/platform/limits [1] https://developers.cloudflare.com/workers/platform/sites https://developers.cloudflare.com/workers/platform/sites

benatkin 6y ago
How do you know that Netlify is production ready? I found Netlify Identity to not be production ready* and now I'm not so sure about the rest of the platform. * Three reasons. 1) The identity widget has people setting it up in such a way that tokens aren't refreshed and logins last only an hour. https://github.com/netlify/netlify-identity-widget/issues/117 https://github.com/netlify/netlify-identity-widget/issues/11... 2) Netlify Identity keeps bumping me out despite having gone out of my way to get it configured properly. I don't know why but the issue has lasted for weeks. 3) In development mode, the token can't be verified without making a request to Netlify Functions, and the suggested path (in Redwood.js at least) is to just parse the JWT without verifying it.
- ignoramous 6y ago
  > How do you know that Netlify is production ready? I meant in a way that pages.dev is in "open beta" and netlify.com don't market themselves as such. Besides, in my personal experience, I never hit any issue with netlify that didn't have a solution.
no_wizard 6y ago
There is a strong chance that when Pages comes out of beta, Worker Sites is going to be transitioned into Pages, at least thats kind of how I feel about some of the verbiage on this page: https://developers.cloudflare.com/pages/migrations/migrating-from-workers https://developers.cloudflare.com/pages/migrations/migrating...
- kmf 6y ago
  hey, kristian from the workers team here - i wrote these docs, so this is good feedback :) we don't have any plans to get rid of workers sites! but we do think that for most people deploying static sites, pages is a better fit than workers sites. when we do talk about the future of pages versus workers sites, we're generally talking about making it easier to deploy serverless functions /with/ your pages sites - providing better tooling and DX around that is a super high priority for us. the interplay between workers serverless functions and static asset serving via workers sites is still a really strong use case (and IMO a thing that workers is uniquely capable of doing) that we don't have any plans to shelf. again, i wrote the docs here so this is on me if it came across as "we're getting rid of workers sites" - i'll take a shot at improving these docs and helping clarify that next week!
kmf 6y ago
> With pages.dev, I believe, you pay per every domain you host nope, we do unlimited sites on pages! here's the free plan [1]: > 1 build at a time > 500 builds per month > Unlimited sites > Unlimited requests > Unlimited bandwidth you can upgrade to the pro ($20/mo) or business ($200/mo) plans for more concurrent builds and builds per month. still not priced per domain or site! [1]: https://pages.cloudflare.com/#pricing https://pages.cloudflare.com/#pricing
- StavrosK 6y ago
  Hey, do you plan to support Gitlab repos? I'd love to use pages but I can't because my repos are on Gitlab.
  - rita3ko 6y ago
    hi there! cloudflare pages pm here :) we certainly plan to (nothing against gitlab!!), likely in the next couple months. my email is rita at cloudflare. happy to keep you posted
- ignoramous 6y ago
  Thanks. > ...still not priced per domain or site! It was my understanding that I had to upgrade each domain to "pro" with $20/month (say, if I wanted pro features like web-analytics on each). Is that not the case? On netlify.com, "pro" is $19/month per account (not per domain).

benatkin 6y ago

How do you know that Netlify is production ready? I found Netlify Identity to not be production ready* and now I'm not so sure about the rest of the platform. * Three reasons. 1) The identity widget has people setting it up in such a way that tokens aren't refreshed and logins last only an hour. https://github.com/netlify/netlify-identity-widget/issues/117 https://github.com/netlify/netlify-identity-widget/issues/11... 2) Netlify Identity keeps bumping me out despite having gone out of my way to get it configured properly. I don't know why but the issue has lasted for weeks. 3) In development mode, the token can't be verified without making a request to Netlify Functions, and the suggested path (in Redwood.js at least) is to just parse the JWT without verifying it.

ignoramous 6y ago
> How do you know that Netlify is production ready? I meant in a way that pages.dev is in "open beta" and netlify.com don't market themselves as such. Besides, in my personal experience, I never hit any issue with netlify that didn't have a solution.

no_wizard 6y ago

There is a strong chance that when Pages comes out of beta, Worker Sites is going to be transitioned into Pages, at least thats kind of how I feel about some of the verbiage on this page: https://developers.cloudflare.com/pages/migrations/migrating-from-workers https://developers.cloudflare.com/pages/migrations/migrating...

kmf 6y ago
hey, kristian from the workers team here - i wrote these docs, so this is good feedback :) we don't have any plans to get rid of workers sites! but we do think that for most people deploying static sites, pages is a better fit than workers sites. when we do talk about the future of pages versus workers sites, we're generally talking about making it easier to deploy serverless functions /with/ your pages sites - providing better tooling and DX around that is a super high priority for us. the interplay between workers serverless functions and static asset serving via workers sites is still a really strong use case (and IMO a thing that workers is uniquely capable of doing) that we don't have any plans to shelf. again, i wrote the docs here so this is on me if it came across as "we're getting rid of workers sites" - i'll take a shot at improving these docs and helping clarify that next week!

kmf 6y ago

> With pages.dev, I believe, you pay per every domain you host nope, we do unlimited sites on pages! here's the free plan [1]: > 1 build at a time > 500 builds per month > Unlimited sites > Unlimited requests > Unlimited bandwidth you can upgrade to the pro ($20/mo) or business ($200/mo) plans for more concurrent builds and builds per month. still not priced per domain or site! [1]: https://pages.cloudflare.com/#pricing https://pages.cloudflare.com/#pricing

StavrosK 6y ago
Hey, do you plan to support Gitlab repos? I'd love to use pages but I can't because my repos are on Gitlab.
- rita3ko 6y ago
  hi there! cloudflare pages pm here :) we certainly plan to (nothing against gitlab!!), likely in the next couple months. my email is rita at cloudflare. happy to keep you posted
ignoramous 6y ago
Thanks. > ...still not priced per domain or site! It was my understanding that I had to upgrade each domain to "pro" with $20/month (say, if I wanted pro features like web-analytics on each). Is that not the case? On netlify.com, "pro" is $19/month per account (not per domain).