We performed a comparison between Cloudflare and Fastly based on real PeerSpot user reviews.
Find out in this report how the two CDN solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."What I like best about Cloudflare is that my company can use it to trace and manage applications and monitor traffic. The solution tells you if there's a spike in traffic. Cloudflare also sends you a link to check your equipment and deployment and track it through peering, so it's a valuable tool."
"Easier http to https redirect using page rules"
"New and innovative way to protect the client's data."
"The solution is very good at mitigating threats."
"When using services like Heroku, Cloudflare is very useful for CNAME flattening. I also use it for their end-to-end SSL with TLS authentication on nginx for securing servers."
"Cloudflare offers CDN and DDoS protection. We have the front end, API, and database in how you structure applications."
"Cloudflare allows us to self-host services such as Rocket.Chat and Node-RED, in high-availability mode, thanks to round robin DNS which allows us to share one hostname between our two locations."
"The simplicity of the overall dashboard makes it a great product for a user like me who has less understanding of the internet than a developer or other more technical people. It gives me peace of mind. I also love the easy customization of the Page Rules."
"Its initial setup process is straightforward."
"Fastly uses configuration versioning, where you can deploy a new version in less than one minute."
"Rate limiting is a good feature that protects from volumetric attacks."
"The product helps our organization to access sites located in different regions quickly."
"Support is good; the product works as advertised. We have a Slack connection with them. So we can basically ask for help, live, engage, and ring when they respond. Very quickly."
"Compute@Edge features are valuable to me."
"It should be easier to collect the logs with companies like Sumo. However, based on my discussions with the salespeople, I understand that's how they make their money. With the enterprise product, they want people doing those kinds of enterprise features to do the logging. They want them to pay a lot of money, and that's where I have an issue with them. That should be a default. You should be able to get the log no matter what. The logging should be universal."
"Cloudflare could offer a better view or maybe dashboards of the main resources used in the client."
"Although I think it's quite good, it doesn't provide me with all the features I would expect to have if I were using Imperva."
"Sometimes their more advanced caching tools can cause higher first-byte times and problems with JavaScript."
"I think the APIs are a little bit hard for us to work with. The APIs could be more open so that we could integrate better with our SolarWinds or our monitoring solution."
"We're facing challenges due to an upgrade in the machine learning model. The problem arises from some users abusing the APIs, resulting in an influx of suspicious traffic. Cloudflare's learning model mistakenly identifies this traffic as human. Consequently, it assigns it a higher trust score, akin to legitimate human traffic, causing complications in our architecture. Previously, such traffic would have been categorized as suspicious, enabling us to apply appropriate blocking rules. However, we encounter difficulties distinguishing between genuine and suspicious traffic with the new categorization. Despite these challenges, overall, Cloudflare remains the preferred solution compared to Azure, AWS CloudFront, and Google Cloud Armor."
"The solution could use more analytics on the backend to give us more insights into everything. More reports would be helpful."
"The timing aspect can lead to it being considered overpriced. This is a particular concern we have with Cloudflare, as they may struggle with accurately detecting the client."
"Stronger analytics would be helpful, like showing configurations that haven't served a certain amount of traffic in a while. With many properties, things can get lost track of - duplicates or unused configurations not properly decommissioned."
"Fastly's customer service area needs improvement."
"The product should provide improved bot detection and management."
"It is missing a "staging" platform to deploy a test configuration with all of the real settings, which would allow us to properly test before putting it into production."
"Support is not that great."
"The solution's pricing could be better."
Cloudflare is ranked 1st in CDN with 56 reviews while Fastly is ranked 7th in CDN with 6 reviews. Cloudflare is rated 8.4, while Fastly is rated 8.6. The top reviewer of Cloudflare writes "It's easy to set up because you point the DNS to it, and it's working in under 15 minutes". On the other hand, the top reviewer of Fastly writes "An easily scalable and stable product that provides exceptional support". Cloudflare is most compared with Akamai, Azure Front Door, Imperva DDoS, AWS Shield and Microsoft Azure Application Gateway, whereas Fastly is most compared with Akamai, AWS WAF, Amazon CloudFront, F5 Advanced WAF and Imperva DDoS. See our Cloudflare vs. Fastly report.
See our list of best CDN vendors and best Distributed Denial of Service (DDOS) Protection vendors.
We monitor all CDN reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.