G2

Mohamed S.

founder

Small-Business (50 or fewer emp.)

8/28/2026

"Easy Edge Security & Performance with Cloudflare Workers and Global Infrastructure"

4.5/5

What do you like best about Cloudflare Application Security and Performance?

What I like most is how easy Cloudflare makes it to put security and performance controls at the edge without adding unnecessary complexity to the application itself. We have used Cloudflare Workers and its edge infrastructure while testing TrigGuard AI workloads, including controlled comparisons between direct-origin and edge-routed traffic. The deployment experience is straightforward, and being able to add an edge layer while keeping the underlying application architecture independent has been particularly useful. The combination of global infrastructure, security controls, observability and programmable Workers gives us room to experiment without locking core application logic into the edge platform. Review collected by and hosted on G2.com.

What do you dislike about Cloudflare Application Security and Performance?

The main downside is that Cloudflare’s platform has a lot of capability spread across different products, dashboards and configuration layers, which can make it harder to understand exactly which service or setting is responsible for a particular behaviour. Pricing and plan-specific feature availability can also take some investigation when evaluating a new workload. For technical teams, clearer visibility into the relationship between Workers, security controls, routing and account-level configuration would make onboarding and troubleshooting faster. Once configured, the platform works well, but the initial learning curve is higher than the simplicity of the core concepts suggests. Review collected by and hosted on G2.com.

What problems is Cloudflare Application Security and Performance solving and how is that benefiting you?

We use Cloudflare to add a programmable edge layer in front of application workloads without moving core authorization logic out of our own infrastructure. For TrigGuard AI, we tested Cloudflare Workers against direct-origin traffic using a controlled 10,000-request workload containing both permitted and denied execution decisions. The edge path preserved all 5,000 PERMIT and 5,000 DENY outcomes with zero receipt failures, zero mutation and zero deterministic mismatches. The measured latency overhead was approximately 8 ms at p50, 12.5 ms at p95 and 19.7 ms at p99. For us, the benefit is being able to introduce edge routing and security capabilities while experimentally verifying that the underlying execution-authorisation semantics remain unchanged. Review collected by and hosted on G2.com.