Cloudflare Reviews

We are still working with Cloudflare at my company, bKash Limited, and we continue to use Cloudflare's Cloud WAF solutions and anti-DDoS solutions.

We are using three solutions from Cloudflare. One is their DNS solution. For our on-premises workload at bikash.com, the primary DNS solution for authoritative DNS is Cloudflare's DNS solution. All traffic for the bikash.com domain is routed through Cloudflare's Anycast solution and Anycast IP. We are advertising this through Cloudflare, and Cloudflare protects our web application and API through this solution for our on-premises infrastructure. This represents 40 to 45% of our workload traffic.

We are using Cloudflare's image optimization feature called Turnstile for CAPTCHA. In some of our applications, we were previously using Google reCAPTCHA, but we are now replacing Google reCAPTCHA with Cloudflare's Turnstile solution for DDoS protection.

Cloudflare's WAF features help us address security threats including SQL injection and cross-site scripting because these protections are automated. In other solutions, we use F5 for our distributed cloud for our AWS and other workloads, and we have to configure those solutions manually. With Cloudflare, those are predefined configurations. We do not need to perform any configuration ourselves, and they ensure protections.

Cloudflare's DNS services deliver the best performance in terms of speed and reliability. We are also using AWS Route 53 for bikash.sh, where our 65% workload is located, but we feel more secure with Cloudflare rather than AWS Route 53 for authoritative DNS.

Cloudflare's custom analytics provide insights into user interactions and security vulnerabilities because we receive good information from the security dashboard about where our traffic originates and from which networks we receive the most attacks. These are valuable features, and I would say they are an added advantage from a monitoring perspective.

Their analytical dashboard is comprehensive because they provide substantial information and features that I find valuable.

From a security perspective, there remains a security loophole, as some browsers in the market can bypass the Turnstile solution, which requires approximately 40 seconds to do so. From a performance perspective, this is acceptable. We also tried Google reCAPTCHA, and that can also be bypassed. From a security perspective, I would say neither solution is completely secured.

Regarding uptime, we have faced a couple of incidents due to Cloudflare in recent years, so I cannot say we receive 100% uptime for our region. We sometimes face challenges, including downtime and other issues. As a result, we are not receiving 100% uptime from Cloudflare's solution. Since most of our customers are in this region, we need alternatives. We need something more competitive than Cloudflare. Unfortunately, in Bangladesh, Cloudflare has three points of presence already, and we cannot find any other solution provider in Bangladesh as an alternative, which presents another challenge.

Competitor solutions have more attack signatures, which ensure better security compared to Cloudflare's predefined configurations. Customers do not have options to modify any configuration parameters in Cloudflare, whereas other competitor solutions, such as F5 Distributed Cloud, allow customers to tune configurations according to their requirements. Cloudflare could improve in this area. Additionally, regarding visibility, Cloudflare has static visibility, but they could adopt dynamic graph features for their customers.

We have been using Cloudflare since 2018.

I would rate their technical support as average, neither particularly good nor poor.

Cloudflare's technical support presents challenges. First, because they are dealing with live traffic as an emerging service, their response time should be more consistent. Currently, we use other solutions where support is available through Slack channels and is more interactive, with someone responding within a couple of minutes or seconds. We also see solution providers that offer AI-based responses, providing solutions from their knowledge-based database whenever an issue occurs. Cloudflare operates traditionally with a portal where we must raise a ticket, and an engineer will engage and respond within two to three hours. This is why I rate them as average, and we need more proactive support from Cloudflare.

Neutral

We are also using AWS Route 53 for bikash.sh, where our 65% workload is located.

From an analytical perspective, we are also using DataDog and F5 WAF solutions, all with interactive dashboards. However, Cloudflare only has some predefined dashboard visibility, and the graphs are actually static and not dynamic. Other solutions have dynamic representations, but while Cloudflare provides substantial information, the representation could be much better.

I would recommend Cloudflare to other companies. However, I would recommend F5 XC Distributed Cloud first as my top priority, and then Cloudflare as my second priority.

I have experience with Cloudflare; I use them all the time, including WAF and DNS.

I'm using Cloudflare on all my domains, and any client domains I have, I set them up with a Cloudflare account.

I've been using Cloudflare DNS product since they came out; that's basically the main use of what they offer.

The best features for Cloudflare WAF are being able to control access and being able to control your security by adding that extra layer above and beyond our internal firewall. I assess the impact of Cloudflare WAF's integration with existing web technologies on my performance and security measures as being basically a front end for edge computing. All the DNS and everything is routed through Cloudflare, so anybody coming to any of the sites has to go through Cloudflare first. They are basically the first wall of defense.

The WAF's advanced reporting and analytics tools add a layer that we're able to visualize and see before it actually hits the local firewall.

For Cloudflare DNS part, I also use it as a DDoS, CSPM, or CDN; I use all the features because it hits them before it hits us. The best features of Cloudflare DNS are the tunneling and the ease of use to create new records, just being able to manage any domains that you own and then have them take care of it. They send you a bill, and it's the only way to go.

Cloudflare makes it easier for me to handle and set up DNS for multiple users and multiple clients, and basically go in and access their account, make the changes they need, and it's a one-stop shop.

I don't know what areas could be improved with Cloudflare WAF; Cloudflare is constantly improving and adding features to their feature set. They're doing a good job, and as far as DNS and support for any domains that I create or my clients create, it's mandatory for me to make sure that they have Cloudflare as their DNS provider.

The Cloudflare load balancing capability hasn't really helped in enhancing my website's uptime and resiliency because we don't really get that much traffic; it's mostly remote users, and web hosting is done by a web hosting service. It doesn't pay to try to host your own website.

I'm using Cloudflare on all my domains, and any client domains I have, I set them up with a Cloudflare account.

I assess the performance of the DNS services in terms of speed and reliability for my organization and my clients as being fine; I don't see any speed loss. Most of the encrypted DNS we put through our servers ends up at Cloudflare anyhow.

I would rate the technical support with Cloudflare as excellent every time I've had to call them; I haven't called them but three times.

Their support, regardless of whatever the problem may be, is great every time I've had to call them; I've only had to call them three times in four years.

Positive

The initial setup with Cloudflare is pretty straightforward for me; I've done enough of them.

It's also straightforward for someone new, but if you understand networking and DNS tunneling, knowing DNS is a must, but other than that, it's great.

In terms of return on investment with Cloudflare, it costs my time to set them up, but basically once they're set up, it's done, and if they're on a free plan or even if they're on a pay plan, they aren't doing that kind of volume that they really have to worry about any pricing issues.

I haven't evaluated other options such as other WAF solutions as a front end; I've used other DNS providers before, but as soon as I found out about Cloudflare, I switched all my stuff and my clients over and haven't switched back. It's a lot more valuable than what they charge.

The main differences between Cloudflare and one of the others I used, such as DynDNS, are that once they got bought out by Oracle, they turned to crap; Cloudflare allows you to set up a free account and still have DNS capabilities on the fly, and if you have to make changes, it's simple.

I have dealt with Cloudflare Web Application Firewall since they had it out.

I have a lot of clients that are basically individual businesses and non-profits, lawyers, doctors, and various other professionals.

It integrates with my existing or my client's existing systems.

I have no idea if there's anything specific that might be nice to have coming in the next releases; I don't keep up on it. Basically, when I go and set up a site or look at any of my sites, I discover they came up with something new and check it out.

My experience with the pricing or the licensing of the product is that a lot of the stuff you can do for free, so the pricing is definitely fair. A lot of my clients don't need that much of what they have to offer, and what they have to offer on free plans is generally enough, so it doesn't cost them anything.

With the WAF feature, I haven't paid that much attention to what Cloudflare is doing regarding addressing security threats such as SQL injection and cross-site scripting, but we have firewalls on all of our systems and intrusion detection that are on site.

I would rate Cloudflare DNS overall as a 10 out of 10. There's definitely a little room for improvement as they could be 10 out of 10 at some point, but they're close to 10 out of 10 now.

Since I'm managing security tools and focusing on email security, Cloudflare mainly helps me take care of DNS records that are related to email security, such as SPF, DMARC, and DKIM. That's the main scope of my interest there. I'm monitoring those records, checking if somebody has altered them, and gathering evidence if needed to warn them not to do that anymore.

Cloudflare is a great product with many useful features. A colleague of mine is leveraging the API to get all the records periodically. We're gathering them to review if everything is set up properly without the need for manual review. I appreciate the additional details about the statistics since the DKIM enablement process requires visibility over whether the DKIM keys are being used and if there were any queries against them. The statistics part lets me briefly validate if the DKIM record is in use because over time, the records stop being used and aren't cleaned up because nobody requested that.

The reporting and auditing tools are important in the use cases I mentioned earlier. There are many features I do not configure but know exist, such as web access firewall to set up accesses to certain DNS records. We were also using the Workers part of Cloudflare to share data from Cloudflare to an external app called Salt, which helped us understand where our API endpoints are in our estate. Based on that, we got information about endpoint locations and unusual API queries.

It simplifies management because you can create domain groups and associate them to countries, allowing them to manage them independently. It helps me understand which country might be responsible for specific domains. It's a great product because it's scalable, has great coverage, and is mature with good defenses against DDoS attacks.

I'm not directly configuring the WAF in Cloudflare because another team manages that, but I see they are adding more features to it, which is making us more secure.

Regarding DNS services in Cloudflare, I believe they are good, but I would consider doing some testing from external places to measure response time and compare performance.

I'm not sure if we are using the load balancing capabilities in Cloudflare on a larger scale. We are using the proxy capability, which I forgot to mention earlier. Most of our DNS records that are presented to the internet are proxied whenever possible, providing another layer of defense from our perspective.

It's challenging to comment on specific features I would want to see included in the next Cloudflare releases because I haven't investigated many existing features. I think many capabilities are already there. A feature I would appreciate is some kind of protection for modifying different types of entries. For example, protection against creating duplicated DMARC entries would be beneficial, along with setting permissions to restrict modification of DMARC or SPF records.

From a management perspective, this would be valuable because while DNS teams add records, in larger enterprises I've noticed that requests going through the ticketing system get implemented as requested, even when users don't always know how to do it properly. They submit unjustified and improper requests that get implemented because someone followed the ticket instructions. Eventually, things go sideways and require fixes when it would have been easier to prevent the issue initially.

I haven't investigated the analytics and insights into user interaction or security vulnerabilities in Cloudflare much further beyond the basic statistics regarding DNS record requests. I'm using the basic API to see if the record was used or not, when it was recently used, and what the usage was over the last week or month period. This helps me understand if the record is still being used or if we can remove it.

Cloudflare is the only solution I've worked with here for DNS and DDoS protection. I do not recall any other tools that we have for these purposes.

Pricing, setup cost, and licensing cost for Cloudflare are totally not in my scope so I do not know the costs. I only know that there are two tiers of WAF, and we are using the basic, cheaper one rather than the more advanced version. There is some differentiation where some features are available on a general basis, but others require additional licensing.

I would advise users looking into implementing Cloudflare in their environment to understand the features before implementing it so they can use all of its potential. On a scale of 1-10, I rate Cloudflare a 9 out of 10.

We are using Cloudflare for our DNS needs as well as for our WAF and security needs. We are hosting our main website on Cloudflare, managing all of our A records and MX records within Cloudflare, and we have created many security rules on Cloudflare to mitigate rate limiting and bot mitigation.

The best feature Cloudflare has is the CDN; the CDN is very good, and the cache feature is also good. We are really enjoying their WAF and bot mitigation feature.

With the CDN, it has increased the loading speed quite a lot, and with the cache, the websites are loading quite well.

Cloudflare has positively impacted our organization by giving us flexibility to manage the DNS part, being quite fast, and allowing us to manage everything from a single dashboard, which is quite handy. Since we can add multiple admins to the dashboard, it has become quite beneficial, and we are quite happy to use Cloudflare.

I think Cloudflare is already quite good; I do not feel any issues with Cloudflare at this time, as everything seems to be working fine. The dashboard is quite nice, the features are quite good, and it is quite easy to use.

The dashboard could be improved a bit to provide us with more insight about the security threats and alerts, and the email notification could also be improved.

In my current field, I have been working for over 15 years.

In my experience, Cloudflare is stable. Cloudflare's reliability and uptime has met my expectations; it has been quite good in general, apart from the recent few downtimes.

Cloudflare's scalability is quite good; it is very easy to scale whenever we want to include multiple domains, and it is very straightforward and easy.

Cloudflare's customer support is good; although we have not opened many cases, their customer support has been good whenever needed.

We did try using other solutions before Cloudflare, but at the end of the day, we were unable to replace Cloudflare with any other solution. Before choosing Cloudflare, we did evaluate other options, such as F5 Distributed Cloud and on-premises solutions, such as Akamai.

At this time, we are not integrating Cloudflare with any other solution, and since I have not used the integration capabilities, I do not have considerable insight about that feature.

The return on investment for me is significant as time is the critical aspect. Cloudflare does save time, and the time savings is the only thing I would like to add, as it saves a great deal of time.

The pricing, setup cost, and licensing for Cloudflare are a bit on the higher side overall.

The learning curve for new users adopting Cloudflare in my organization is quite good; it is a quite easy solution to learn with no difficult things, and the interface is quite user-friendly.

Cloudflare handles compliance and regulatory requirements for our organization by having all of the required compliances. We are using ISO 27001, which Cloudflare is also certified.

I find Cloudflare's documentation and resources very helpful, as we often use those documents to fine-tune our services and learn new features.

I feel that our environment is quite secure with Cloudflare in place; we have not faced any issues in the past, and we feel it is quite safe.

My advice to others looking into using Cloudflare is that it is quite easy to use, with an intuitive interface, a good learning curve, and good usability. I would rate this review a 9 out of 10.

I only implement the DNS for customers, mainly focusing on the government in Mexico and online platforms in fintech. My customers tell me the DNS is very fast.

It is a fast and secure DNS. It is very easy to deploy, and my customers are happy with this tool. Additionally, the CDN performance in Mexico is excellent, providing fast service and tools. It offers reliability during high-traffic periods, ensuring no impact on the environment. It helps my clients avoid using on-premise boxes, simplifying operations as they only use the prices on Cloudflare.

There could be more courses with engineers. I like e-learning, however, having a specialist in a classroom is more comfortable for me.

The service is very stable with no impacts during high-traffic periods. It provides fast performance.

The tool offers very good performance, even during high-traffic periods.

I find the support for Cloudflare DNS to be good, and I would rate it an eight out of ten.

Positive

Setting up Cloudflare DNS is very easy. On a scale of one to ten, I would rate it a nine for ease of setup.

Only one person from Cloudflare, myself, an engineer in Mexico, and the customer are needed to deploy the DNS.

My clients benefit significantly, as they no longer use on-premise boxes. This makes operations very easy, and they do not need to buy licenses, using only the prices on Cloudflare.

I use the free version, which has the best prices. It's very easy to upgrade the service for more complex patient needs, and I find it to be cheap.

I do not work with AI. In terms of overall performance and reliability, I would rate Cloudflare DNS a nine out of ten.

Neutral

In Cloudflare, we utilize their DNS and DDoS protection services. All incoming traffic to our server passes through the Cloudflare network. However, we face challenges when it comes to handling legitimate DDoS attacks. These attacks are well-crafted and mimic genuine requests to our publicly facing web pages. Despite Cloudflare's scoring mechanism, there are concerns about the effectiveness in blocking such attacks, as the traffic still reaches our infrastructure directly. Cloudflare recently introduced a new solution for Captcha, but enabling it poses challenges. Some customers are unhappy with Captcha, and modern AI-based DDoS tools can even bypass Captcha, further complicating the situation.

We have been utilizing Cloudflare's solution for over a year, to be precise, between one and two years. Currently, we are using their SaaS product, Cloudflare, for DDoS and DNS.

In general, the product is stable, and Cloudflare excels in DNS services. However, for DDoS protection, I would not recommend Cloudflare. While an on-prem router might be suitable, I would advise considering alternative cloud-based scrubbing solutions. We are currently exploring new options, and F5 is one of the products under consideration.

Cloudflare's technical support in this region, specifically in Bangladesh, is acceptable. However, since there is no local office here, I primarily interact with their offices in India and Singapore, which manage this territory. Unfortunately, obtaining support from them can be challenging at times. Specifically, Cloudflare should work on providing support aligned with our time zone, and in the case of DDoS scenarios, having a Security Operations Center (SOC) or similar services with a hotline number for immediate contact would be beneficial. This would help us address issues promptly, especially during unforeseen events like DDoS attacks.

Neutral

The implementation in our environment is a challenge. Since it's a SaaS product, we handle the implementation ourselves, but we also enlist Cloudflare's assistance through their implementation service. Given that the portal is on Cloudflare's side, we rely on their guidance to implement the solution. We follow Cloudflare's configuration methodologies and adhere to their shared workarounds during the implementation process.The implementation doesn't take much time, typically one to two months. However, ongoing tuning is required, especially when there are changes in my web applications. 

One challenge lies in the limited configurations, particularly in rule customization. For instance, if I have a generic rule based on my web UI, it may not be suitable for specific aspects of my infrastructure. A specific challenge involves rate limiting, where, for example, my organization's name is bikash.com, but I need to configure rate limits for bikash.com/campaign and bikash.com/contactus separately. The traffic patterns for these segments differ, with higher traffic during campaigns and lower traffic for contact us. Configuring rate limits in Cloudflare becomes challenging in such scenarios, especially when dealing with varying traffic patterns.

The pricing for the service is reasonable, neither excessively cheap nor prohibitively expensive. It aligns well with the value of their solution.

Overall, I would rate it 5 out of 10. 

For the free and Pro plans, they could use a simple bot to provide information to users. This would improve support, especially for less advanced users who utilize the free components.

We had a couple of back-and-forth communication with the Cloudflare team. The support team's responses are comparatively slow and not as optimized as they could be. So, it leads to a couple of delays.  The communication process is a bit linear, which can be frustrating.

Smaller businesses have seen great ROI due to the low investment and strong performance. 

Many regional e-commerce websites and information-based pan-India websites like WordPress. These sites were facing tech challenges, particularly with WordPress. It's one of the most popular content management systems, but it needs robust support because it's inherently vulnerable. 

WordPress security can be tricky, and that's where Cloudflare can be absolutely helpful for small businesses. They utilize its security features to combat those pesky DDoS attacks and other threats, significantly improving their website stability. It can be a pretty satisfying and decent experience.  

Cloudflare's biggest plan for initial businesses is $200 per month, and if you're an enterprise, you'll likely exceed that on either AWS or Cloudflare itself. 

For comparison, Akamai's minimum billing starts at a couple of thousand dollars. That's where Cloudflare shines for smaller businesses – it's ten times cheaper than Akamai.

Interestingly, even their enterprise solution is cheaper than other platforms like Akamai and Amazon CloudFront.

For Cloudflare, I recommend it heavily for small businesses with revenue under a couple of million dollars. Onboarding is easy, and they even have a free plan. This makes it simple for businesses in the $100,000-$500,000 range to try it out and see its value, allowing them to scale up their infrastructure as needed.

Many small businesses lack the budget for solutions like AWS and rely on GoDaddy, hosting, or even Versal plans for their initial setup. At that level, Cloudflare is the best option, even though it's not as powerful as Amazon CloudFront or Akamai. Those are built for different services, while Cloudflare caters specifically to smaller teams that eventually scale up.

For smaller businesses, they're the absolute best, so I'd give Cloudflare a nine out of ten. 

For larger businesses, it depends on the budget. Even for them, I'd rate it a seven out of ten.

I use Cloudflare for legacy websites that I need to protect because they're very vulnerable or to secure a client's critical websites. We will implement it after a review or if the website has gotten a poor grade on one of those online checks to see if the security meets the minimum requirements. 

Usually, after I show them their website is vulnerable, I get them to sign up immediately. For me, it's more of a delta suspender as a security measure. I find that many web developers do a poor job of updating their websites and keeping all the security modules.

Cloudflare has a server, and you point your DNS there. From there, you either enable the passthrough or use their full proxy. When you use their full proxy, you get all the features. If you're only doing the DNS, it's just a basic DNS server. Most people don't use it just for DNS; they use it for proxying their websites. You can proxy other services as well, but I've only used it for web applications on different ports.

Many websites require an SSL certificate because they sell stuff and want SSL. Cloudflare comes with an SSL certificate built in. It's automatic. You sign yourself up for Cloudflare, and an SSL certificate automatically protects your website. If you have a connection between your website and your host, the server, Cloudflare, and the host, you don't necessarily need a certificate, okay?

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. 

I have been using Cloudflare for several years.

Cloudflare is highly stable.

Cloudflare is highly scalable. Cloudflare is a system with a web portal that the end users like me see. It's a console where we can adjust the DNS, caching, and security features all in that console. Cloudflare owns thousands of servers across the world that cache the data. It's a powerful solution. When clients sign up for Cloudflare, they're getting this monster content delivery network, security, and a web application firewall in one. It's all rolled into one, and it's massive.

Unless you have your website hosted on a massive hosting provider, there's no way that you can deliver the amount of data that Cloudflare can provide to the end users. If you have static content, there's no way that you can ever match what Cloudflare can do. Obviously, there are competitors to Cloudflare that do the same, but I'm saying other types of solutions.

Let's say you go with F5. Great, that's on-prem. That's in your colo. You can't deliver as much data to the internet as you can with a CDN. You don't have to spend $20,000 on a net scaler, F5, or whatever Cisco's selling now. You don't have to buy that. You pay them $50 a month or $150 a month. It's totally worth it because even in five years, you'll never get the performance value, not just the actual ROI. You have to consider how much throughput you can get with Cloudflare.

It depends on the level of support. Basic Cloudflare support is average. Enterprise support is amazing. It's 10 out of 10. However, if you're paying $20, you get email-based support. 

Cloudflare is effortless to set up because you point the DNS to it, and it's working. You enable the proxy and SSL. The website is protected within 10 or 15 minutes. The biggest wait is for the internet to see that the DNS has changed. I always do the initial setup myself and then give it to one of my web guys to manage. There's a reason behind I do it that way. When ordering a client, I generally manage their DNS, email, and other services. I don't want to let the web developer mess it up.

The web developers know how to do it but don't have a stake in it like I do. If they flip a switch and forget to update the FPF or TXT records, and other essential documents start to break, it's a problem. I don't trust them to do the setup. Other than that, I let them have access. I let the web developers have access because they need to make changes. They're going to add host entries, etc., and they may want to adjust some of the features in Cloudflare.

I'm not a web expert. I have expertise in infrastructure, server planning, and SQL. I can support the whole picture, but I'm not a web expert. You don't need a web expert to do it. You can get a generalist like me, and I have many specific skills. However, I don't do that every day, and you don't have to touch it daily. In a lot of ways, it's a set-it-and-forget-it kind of deal.

The solution requires some primary care and feeding for performance problems and functionality issues, like if something doesn't work because it's a bad link. I engage with the web developer to determine if it's a problem with caching, the code, filter configuration, etc. We look at all the different features. That may require some effort. However, if you don't make any changes to the website, you might only touch it twice a year after it's configured. 

I have some clients whose sites don't do anything. It's like a virtual business card. For those sites, I give them the lowest common denominator of Cloudflare set up for that domain. The website is protected and much less likely to get hacked.

However, if I have a company that has online sales and sends out many newsletters, then they need to have a CDN. That way, if a thousand people get that email and click it at once, it will not kill their server. That's the value of having Cloudflare or something similar. It's different if a thousand people click on a server farm in one location. 

Even at AWS, you have to have this auto-scaling, and the configuration is significant. I would get paid thousands of dollars to set that up. That costs a fortune in monthly payments. I don't know of any of these different companies that host servers. I just put the website on Cloudflare, and they don't spend much money on my time. Maybe I should be smarter and push the AWS, so I get paid more.

It could range from free to $1,500 a month. I put all my clients on Cloudflare, so it's around 20 or 30 customers. One of my clients has more than two dozen domains on Cloudflare, so they pay $20 times 20 domains. He's paying $400 a month. It isn't cheap, but it's totally worth it.

I rate CloudFlare 10 out of 10. I couldn't recommend it more strongly. If you have a website, you need to use Cloudflare or something like it. Don't leave your website unprotected. That's my advice. I set up Cloudflare for every client that wants to host a website because it protects their site and makes it easier for me to manage the DNS. 

I get them to pay the $20 for it. That's the bare minimum. If you want something that can enhance the security of your website, just do Cloudflare. I always do it. I mean, I'm always going to add to my Cloudflare base. I'm never going to shrink unless I find something better. But I don't know of any other solutions that.

You can do a self-sign. That's a couple hundred dollars a year that you don't have to spend, and you don't have to manage that. You can lock down your security on your website so that only the Cloudflare data centers can access your web server. You're limiting a lot of risks.

Let's say you're hosting your site on GoDaddy. GoDaddy's server is unprotected. It's just a server out there. They have enterprise IDS and all that other stuff, but for the most part, they're vulnerable. People attack them all the time. You can limit that by only allowing access to your website from Cloudflare servers. Cloudflare stands in front of your servers as a firewall. That increases performance and security. It limits a lot of access to your servers. 

There are so many benefits here. You don't need SSL on your site, which is excellent, because you don't have to pay for that certificate. That makes it a lot easier. Troubleshooting your site for problems and not having SSL enabled between you and Cloudflare is huge. 

In my company, Cloudflare's PoC phase is going on, and so it is not an active contract we have had with them, but just basic experience is what I have with DDoS protection. I basically use Cloudflare for DDoS protection. My company recently tested the tool for its DDoS protection capabilities.

In terms of the tool's advantages, I would say that it can be highly automated and is very quick when it comes to propagation. The tool is user-friendly. The product's reporting capabilities are great. We need to do a bit of customization in the tool, but most of it is automated. The tool has a lot of artificial intelligence and machine learning. The solution has been able to compare it to the market, and I think the product has taken great strides in automating quite a bit of things, and they use a lot of AI.

I have not extensively worked with it, so I can't think of any improvements that are needed in the tool at the moment.

It is a foolproof solution. The support is great. I don't think that I can come up with any cons about the tool at the moment.

The integration of LLMs on the dashboard is something that is needed in the tool. What Cloudflare is doing internally is that it is stepping ahead in areas like detection and protection. The tool should integrate LLMs on the dashboards and assist you with policy creation.

I have been using Cloudflare for about six months. My company has a partnership with the solution.

We did not face any stability issues in the solution.

Scalability is one of the added advantages of Cloudflare as it is used across the world. It is a SaaS tool, but the fact that they have workloads deployed across the world proves that it is a highly scalable tool.

I have primarily worked not with the tool's customer support but with the product's sales engineers and technical sales engineers, who seem to know their stuff.

I have used Imperva. Compared to Imperva, I feel Cloudflare has better support and a straightforward licensing model. Cloudflare gives you a free trial for an extended period of time. The number of services Cloudflare offers in one package is also quite a lot. The number of folks Cloudflare has is more widespread compared to Imperva, so you can redirect the traffic to wherever you want and continuously do health checks, which PoP is up. If there is a PoP that is down, Cloudflare automatically reroutes you to it.

Imperva is better than Cloudflare in the area of bot protection. Imperva offers advanced bot protection, specifically in terms of the detection and protection for advanced bots it provides. Imperva is able to detect dangerous bots in a more efficient manner, making it better than Cloudflare. There are more ways to bypass Cloudflare than there are on Imperva.

The product's initial setup phase is straightforward.

One person can manage the product's installation phase.

The solution is a SaaS tool, so there is no maintenance required from the user's end.

The solution can be deployed in half an hour.

The tool is a premium product, so it is very expensive.

Cloudflare's CDN performance enhancements work in a lightning fast manner. The good thing is that there are PoPs all across the world, and I think that it is minimally required.

I saw quite a number of integration opportunities with Cloudflare. Cloudflare has a lot of capability to integrate with different tools, teams, or across on-premises or cloud networks.

I rate the tool a nine out of ten.