I agree that giving Enterprise users more control over Cloudflare's edge-level security rules would be useful.
For smaller websites and web tools, being able to filter unwanted traffic before it reaches the origin server can help reduce unnecessary resource usage. Rules for specific countries, ASNs, bots and rate limits would give site owners more control without having to manage separate proxy configurations.
It would be especially useful if Cloudways could provide a simplified WAF rule builder in the dashboard, while still handling the underlying Cloudflare Enterprise configuration.
I recently built a lightweight https://tallycounts.com website, and having straightforward control over traffic filtering and security at the edge would be valuable as these types of sites grow.
Even allowing Enterprise customers to submit custom rules to Cloudways support for implementation would be a good alternative.
I agree that giving Enterprise users more control over Cloudflare's edge-level security rules would be useful.
For smaller websites and web tools, being able to filter unwanted traffic before it reaches the origin server can help reduce unnecessary resource usage. Rules for specific countries, ASNs, bots and rate limits would give site owners more control without having to manage separate proxy configurations.
It would be especially useful if Cloudways could provide a simplified WAF rule builder in the dashboard, while still handling the underlying Cloudflare Enterprise configuration.
I recently built a lightweight https://tallycounts.com website, and having straightforward control over traffic filtering and security at the edge would be valuable as these types of sites grow.
Even allowing Enterprise customers to submit custom rules to Cloudways support for implementation would be a good alternative.