Hacker News new | ask | show | jobs
by victor106 3013 days ago
This is great news. Cloudflare is way too expensive. Pricing seems reasonable

Policy Charge $5 per Cloud Armor policy per month Per Rule Charge $1 per rule per policy per month Incoming Requests Charge $0.75 per million HTTP(S) requests

2 comments

> Cloudflare is way too expensive.

Eh? DDoS protection on Cloudflare is free: https://blog.cloudflare.com/unmetered-mitigation/

Which features of Google Cloud Armor are "too expensive" with Cloudflare?

(Disclosure: I'm an engineer at Cloudflare, but I'm genuinely curious what you mean here.)

Not comparing to Cloud Armor, but the $200/month minimum to bring one's own tls certificate. That alone puts Cloudflare squarely on the list of unusable options for any small project or business that is running their entire production infrastructure on less than $100/month. Also, the inability to specify cache expirations below... what was it... 30 minutes or 2 hours? Again, forced to pay too much for one of the core features of a CDN.
I never thought I'd see the day when $200/month is considered "way too much" for a CDN... We've really come a long way.

Personally I use Cloudflare's free tier for lots of projects, and it has a perfectly reasonable TLS offering.

Hmm. Cloudflare provides free TLS certificates automatically. The feature you're describing is for if you want to upload your own certificate and private key to Cloudflare for it to use on the edge. Do a lot of small projects really need that?
Do you really need your own certificate vs using their free provisioned ones?

If you need that kind of technical details than Cloudfront or Stackpath are pretty good for low traffic sites.

Gotta add load balancing charges to this as well, but still ends up cheaper than CF in some cases.
No caching provided either. Full on egress charges. Surely that makes the comparison apples/oranges.
Caching is provided with GCP HTTPS load balancers, it’s just not specified here.
At Cloudflare like egress prices?