tei.forrester.com
The Total Economic Impact™ Of Cloudflare - Forrester
Excerpt
##### Key Challenges Before adopting Cloudflare, interviewees’ organizations faced a range of operational and security challenges that hindered performance, increased risk, and created inefficiencies. Legacy environments relied on fragmented point solutions, on-premises hardware, and manual processes that were costly to maintain and slow to adapt. These limitations resulted in frequent downtime, inconsistent security coverage, complex vendor management, and poor user experiences — particularly for remote access and global application delivery. Interviewees noted how their organizations struggled with common challenges, including: - Security gaps and inconsistent protection. Many interviewees said their organizations lacked a unified web application firewall (WAF) or DDoS solution. Some external-facing applications had no protection at all, leaving them vulnerable to attacks and compliance risks. - Frequent downtime and attack disruptions. Interviewees’ organizations experienced outages from DDoS attacks, bot abuse, and credential-stuffing attempts. Interviewees from retail and gaming firms said that downtime during peak events like Black Friday or major sports games caused lost revenue and customer churn. - Complex, fragmented vendor landscape. Multiple point solutions (e.g., Akamai, F5, Infoblox) created operational complexity at the interviewees’ organizations. Their teams had to manage different consoles, policies, and hardware across regions, slowing response times and increasing costs. - On-prem hardware and maintenance burden. Interviewees said DNS and security services often ran on physical appliances, requiring monthly maintenance windows and weekend work. Coordinating global downtime for upgrades was disruptive and unpopular with staff. - Slow time-to-market for new apps. Before Cloudflare, launching new applications at the interviewees’ organizations required provisioning hardware, securing licenses, and scheduling maintenance windows, which often took weeks or months. - VPN performance and user frustration. Legacy VPN solutions were slow, unreliable, and difficult to scale for remote work. Interviewees said their employees faced latency and frequent disconnections, especially during global events like the COVID-19 pandemic.
Related Pain Points
Frequent downtime from DDoS attacks and bot abuse
9Organizations experience significant downtime from DDoS attacks, bot abuse, and credential-stuffing attempts, causing lost revenue and customer churn, particularly during peak business events.
Legacy VPN performance and user frustration
7Legacy VPN solutions are slow, unreliable, and difficult to scale for remote work, with employees experiencing latency and frequent disconnections, especially during global events.
Lack of built-in DDoS and WAF protection
6Railway does not provide built-in edge protection, Web Application Firewall (WAF), or DDoS mitigation out of the box. Developers must add extra layers (CDN, proxy, WAF) manually if their apps need strong security or resilience against bot traffic.
Developer productivity blocked by manual cluster provisioning
6Developers lack Kubernetes expertise and want to consume infrastructure without delays, but provisioning new clusters is time-consuming and expensive. This creates bottlenecks where developers wait for ops to provision infrastructure rather than focusing on feature development.
Siloed security tools prevent unified S3 security visibility
6Organizations use fragmented point-product security tools for S3, making it difficult to gain a holistic view of security posture and creating gaps in coverage.
On-premises hardware maintenance burden and downtime
6DNS and security services running on physical appliances require monthly maintenance windows and weekend work, with global downtime coordination being disruptive for staff.