Cloudflare One Reviews

We have to make sure that we are protected in our domain, our website from the public Internet because we don't want any compromise to our site.

With DDoS, we have to ensure that we are not hijacked. So that's why we want to eliminate the attacks on our infracturer. 

The capabilities of the software are strong enough for me to do what it's supposed to do. For me, we don't need to do a lot of configuration on our site. We just enable it and monitor it.

Cloudflare is good at consolidating the solution embedded into one single console, which makes it interesting for us to explore more on Cloudflare. Besides that, the CDN performance has also helped us improve the accessibility of the site to the public.

There is little room for improvement dashboard-wise. 

In future releases, I would like to see alerts. The software has automated alerts, but the automated alerts are not available in the mobile app.

Now, we have to be fast to get ready, not just from the end-user site, but we have to know first if possible.

I have been using Cloudflare DDoS for almost three years. 

So far, we haven't received any complaints or issues from our application site. So far, we don't see any issues that are concerning. Because I am the one managing the infrastructure, the others are managed by my application team.

So, it has been a stable product for us. 

There are more than five end users in our company. So, we added a key percentage that manages the product and the system.

When I stepped into the current company, the system was already onboarded.

We use Cloudflare WAF CDN and DDoS protection for our domain.

The initial setup is easy and straightforward. For me, it's easy because we only need to point our DNS to Cloudflare, so we receive traffic from Cloudflare.

I'm suggesting using Cloudflare based on our experience. This is in terms of compliance. So, it complies with the top tech standards. And configuration is easy for us. We don't need to stress it for customization or configure rules. We enable it, and it's done. We only monitor the logs and any issues. So I'm suggesting you use Cloudflare if you want to.

Overall, I would rate the solution an eight out of ten. 

We use the solution as a web application firewall.

The blocking feature is very good. The traffic feature is also very good. The product has a lot of good features that we can use on-premises or on the cloud. I like the product very much. It is a very good defense tool.

The solution must improve support. The response time for support must be reduced.

I have been using the solution for one and a half years.

The tool is pretty stable. I rate the stability a nine out of ten.

I rate the tool’s scalability an eight out of ten. More than 40 people in my organization are using the tool.

We get people to support us when we contact them. However, it takes them too long to respond. The first response is quick, but the follow-ups are slower.

Positive

The initial setup was easy. The time taken for deployment depends on the devices we deploy, the logs we want, and the kind of product we are deploying.

The deployment was done in-house.

The solution is not that expensive. It is moderately priced.

The documentation is easy to follow. The documentation is really helpful for first-time users. Overall, I rate the product a nine out of ten.

We use the product to mitigate the security risk of dynamic DDoS attacks. In these attacks, millions of requests come from millions of different IPs to get our server down. If we do not have a security solution to mitigate this risk, the service for other users will be down. The server will be down due to the huge consumption of resources.

The solution has different options that can be used to differentiate DDoS attacks. Cloudflare has a user agent, which can be used to define rules. If I do not want MacBook users to access the system, I can use the user agent to drop the traffic for MacBook users. It is very valuable. It helps me mitigate risks.

The product gives us many tools to mitigate risks. It is one of the most powerful solutions on the cloud. The documentation is good.

The onboarding process can be improved a little bit.

I have been using the solution for nine months.

I did not face any stability issues in the past nine months.

I recently contacted support to get more information about certain attacks. I wanted to get a full report about an incident, and they sent me all the details I needed.

Positive

The initial setup is not complex at all. It is too simple.

We just have to integrate the node IP address of AWS and change the public IP as a DNS record. Then, Cloudflare will send all the data after mitigating any risk to AWS. The deployment takes five to seven business days. We need one or two engineers for the security part of the deployment. For testing and services, we need a team.

It is a cloud solution. We have integrated it with Amazon AWS. Sometimes we can't mitigate the DDoS attacks using AWS WAF. It doesn’t detect the attacks. AWS WAF does not have some options to differentiate the type of attacks.

I use the tool only as a DDoS solution. I just use the DDoS service to protect myself. There's no scalability for this option. Documents already exist for all the cloud solutions. I wouldn’t prefer an automated solution for integration because apps are built based on customers’ requirements. The requirements differ, so the default profile for automation can't fit all the customers. Overall, I rate the product a nine and a half or ten out of ten.

I mostly use Cloudflare Access for protecting some specific areas of my website, specifically public access. So I can do it using two-factor authentication. So it only allows some registered emails to access that part of my website.

For Cloudflare Access, I am using the free plan. So they are allowing 50 users to use it together. So we can say it is not only for personal use but also beneficial for a small team of fifty people. We can use it in a small company or startup also.

The most valuable feature is their protection. Also, its custom rule set is something we can use to specify whether we want to allow a user to access a specific application-specific software.

I'm just a beginner in Cloudcare Access. So I have used their basic functionality. So, I didn't find any issue with their basic functionalities.

They don't have a person to provide support for customers using the solution under their free plan. So, the aforementioned area can be considered for improvement.

I have been using Cloudflare Access for three to four months. I'm using Cloudera Access for my personal use.

I haven't contacted technical support.

The solution is deployed on the cloud. So, it is mainly deployed on Cloudflare infrastructure. We can use that to protect our application or step on our own server or any software as a service application.

They have Web2py, which we can use for setup. But before that, we have to add the domain we want to protect with Cloudflare Access to Cloudflare DNS. So I want to say that before using Cloudflare Access for a specific domain, we have to add them to Cloudflare DNS. Only then can we use Cloudflare Access.

Whether to use the solution or not will depend on your requirements. For basic security, we all have already implemented a password and a username on our website. But nowadays, it is possible to crack passwords because of modern computation. So, if we want to secure our services, it is really good to add a two-factor authentication using Cloud Access to improve security.

Without adding any manual code or any more software to our servers, I can easily implement zero trust Cloudflare Access, which is because of their simple UI, by just adding my domain and specifying a role. So it's easy.

I rate the overall solution a ten out of ten.

We use this solution for our web application firewall. We are partners of Cloudflare and I am a system architect and specialist. 

This is a simple, user-friendly solution. You turn it on and that's it. It's a perfect solution from my perspective; it's easy to understand and easy to configure. 

I would like them to include a VPN feature to provide a secure connection to the data center.

I've been using this solution for two years. 

The solution is stable. 

The solution is scalable, we have around 70 users in the company. 

We used the local technical support team in Singapore and they were very helpful.

The initial setup is straightforward, deployment took about an hour. 

Licensing costs are reasonable, I believe we pay around $4,000 per month.

We evaluated several options, including Radware and F5, and carried out a POC. Cloudflare came out on top.

I recommend this solution and rate it 10 out of 10. 

I am not a reseller, but an implementer. We help our customers utilize this solution.

Cloudflare Access is primarily used in government homage for DDoS protection.

We decided to use Cloudflare Access to solve a problem with DDoS protection.

It covered the things that we needed at the time.

The pricing is an area that can be improved. Pricing, as far as I recall, was the source of our problems.

I have been working with Cloudflare Access for the last 12 months. I am working with a company that has many customers in different areas, and we have absolutely used Cloudflare for some of them.

I became familiar with Cloudflare Access four years ago.

Cloudflare Access is a stable solution.

Cloudflare Access is scalable.

I especially remember that we got great support.

I would absolutely rate the support a five out of five, they helped us a lot.

Positive

It's been a while, but I don't recall any problems with setting it up.

At the time, it was me and two other technicians to manage this solution.

The prices are slightly expensive.

I evaluate many things to educate myself in the work that I am doing.

We have used others as well, but I think that they are pretty comparable to other solutions that are available. Cloudflare, in my opinion, was easy to implement.

It was very good, I would rate Cloudflare Access an eight out of ten.

I use the solution for scrubbing internet-based traffic that comes toward a particular company’s data center. The traffic is directed to Cloudflare first. Cloudflare does the traffic scrubbing and sends the clean traffic toward the company's data center.

I have worked with many DDoS solutions. Cloudflare is by far the most effective solution that I have come across. It is really good. The product’s signatures are good. The people in the accounting and technical management teams are nice. Support is also good.

Operating and tuning the product is difficult.

I have been using the solution for almost one and a half years.

The tool is pretty much stable. I rate the stability a ten out of ten.

I rate the scalability a nine out of ten. The solution has a huge customer base. In our organization, 10,000 people are using the solution.

When we often face issues with the service, we contact the support team. The team is really good. However, support could be improved.

The onboarding process was pretty simple.

We deployed the product two years ago. We took a couple of months to deploy it.

If someone wants to set up a DDoS solution for the first time, they should choose Cloudflare. Overall, I rate the product a nine out of ten.

We use the solution to protect some of the services. It helps us protect our applications and infrastructure.

The solution is user-friendly in terms of graphical interface and is easy to deploy.

Our subscription plan for the solution has a limitation of bot signatures.

It is a stable solution.

It is an in-built tool in our Cloudflare infrastructure, and we use it as a DNS service. Thus, we don't necessarily have to configure it. We add it as a service, and it works great for us.

The solution is excellent. It helped us a lot with DDoS issues. I rate it a ten out of ten.