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. 

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.

I rate Cloudflare eight out of 10. The basic setup is straightforward, but you may need to configure some advanced settings in some cases. We finished the setup in under an hour. However, we need to do some regular maintenance. 

The initial setup is very easy.

I rate the tool's ease of deployment a ten out of ten. It's very quick. Deployment time largely depends on how we configure it, whether done through coding or the UI. For a single-user setup, it's straightforward. However, for more complex configurations with multiple use cases, it can vary. However, setting up a single zone for production load typically takes less than an hour.

The initial setup for Cloudflare is easy because you only have to connect it to your private cloud based on your requirements. I didn't experience any issues connecting the tool.

In my company, deploying Cloudflare required a lot of equipment, so it took four to five days to complete the deployment, but there was no problem with the process.

Cloudflare is very straightforward. It is easy to set up.

There is no installation, you just go through the configuration process.

The initial setup is very straightforward. You need to know something about DNS domains and so forth, but if you're familiar with setting up a website then it's straightforward. The deployment takes about 15 minutes.

The initial setup was really simple and user friendly.

The tool's setup straightforward. 

The initial setup is pretty straightforward and doesn’t require any technical knowledge, since everything is done on their site.

The initial setup was very straightforward.

The initial setup is straightforward and takes a few hours. One person can do that.

The solution is easy to setup and share with customers. We categorize a customer's needs and recommend the best plan based on traffic and whether they need load balancing, bot management, routing, and unlimited bandwidth.  

On this particular system, I didn't have as much budget as I would have liked, but I still had the redundancy that I wanted. The complexity was that things don't work the way they used to so I had to rethink things. In the end, deployment for the actual solution took about 10 minutes. It was a matter of just literally giving them a credit card and flipping a switch. It's been fine ever since. 

The initial setup is not difficult. All the steps for deployment are documented. We followed the step-by-step instructions for configuration.

Initial setup was straightforward. CloudFlare's setup wizards made it easy.

It is very easy for someone who knows DNS. It is somewhat opinionated and pushes you into higher tiers, but overall it is easy.

The setup was super simple, and it still is.

CloudFlare is very intuitive and the setup has been straightforward from the beginning.

Initial setup is straightforward and easily configurable, even if a person doesn't have any knowledge of CloudFlare. He/she can easily set up CloudFlare.

The initial setup is extremely easy but will require access to your Domain Name Servers.

The installation was complex until I learned what I had to learn. Once you learn about domains, DNS, name servers, propagation, and web server management, CloudFlare is simple. Before you learn, it's quite hard to understand and debug DNS and configuration issues.

For example, I was once trying to SSH into the domain instead of an instance's IP address. It took me forever to understand why it was not going to work.

I'll say that you have to be used to managed webservers such as Apache or NGINX. It's pretty straightforward, but you have to take care with some configuration details. If you do it incorrectly, it could make your website temporarily unavailable sometimes.

I think any DDOS solution is going to be complex. But we could actually follow the process and implement the solution. So it was not that complex, in that sense. And the tech support was there to provide feedback and support.

We didn't get any training other than you reading up materials and working with tech support.

The product is very straightforward and simple to implement. Those are the main reasons for using it.

Initial setup was simple enough for novices. They have plenty of documentation on their site.

The initial setup was stressful. You have to tune the configuration for the integration which is important to have it done correctly.

It was very easy to get setup on Cloudflare. They have made it even easier recently, and all that needs to be done is to enter your DNS records into their interface and the configuration is done.

We were used to the CNAME setup. Initially, this was not offered but now it is. The only issue is handling the non-www redirections that, with CNAME setup, requires us to use an external server. (Incapsula does not.)

The initial setup is straightforward.

Cloudflare is not complicated to set up. It is fairly straightforward. Deployment times depend on the website. Because I already read the documentation before the first setup, it actually took no more than 10 minutes. I did it all by myself.

Very straightforward, we were set up in minutes.

Initial setup is very straightforward.

The initial setup is extremely easy. There's absolutely no complexity.

Deployment times will depend on the customer due to the fact that we will need to change the authoritative main servers and customer domain. We can typically do this in one day. It totally depends on the customer and their requirements and processes. 

There is no downtime involved in the deployment. 

The initial setup was neither simple nor complex. It was somewhere in the middle, However, we did have help with the implementation, which was very useful for us.

The deployment took about 11 days in total. It wasn't too long.

Once it is deployed, there is no maintenance required of us. 

Initial setup is straightforward and guided by Cloudflare. NS changes for new site is easy. For existing NS migrated to Cloudflare, user must recheck current DNS records to ensure all records already available in Cloudflare.

With every service out there, there will be hiccups every now, and then but as far as the deployment goes Cloudflare is extremely simple to implement. It is a low-risk solution since we can manipulate which DNS zones get cached and which don't. In case there's any trouble, we can disable CloudFlare, and switch to our local DNS in less than a couple of minutes.

Setting up CloudFlare is an easy gig. The only issue you might encounter is having your domain registered through a vendor that doesn't allow direct name-server manipulation.
For example, Enom resellers are known to have their domain control interface completely locked, so you have to rely on their support to handle this for you. If their support team has an issue with handling requests within the SLA - you have a problem.

The setup was ok, but the deployment took a long time.

I have a lot of people on my team.

The initial setup was quite straightforward. There is a button with an explanation. We deployed it within minutes. It has an SQL database and it only took minutes to apply it on the website.