I built a free, online tool that enables people to copy Cloudflare WAF rules from one source zone, to a list of target zones. This is especially useful when you have hundreds or thousands of domains.<p>2 questions that you may want to ask right off the bat:<p>1. Why not just use Terraform? A: There’s a sizeable minority who aren’t comfortable with IaaC - managers of ecommerce sites, for example.<p>2. Doesn’t Cloudflare’s account-level WAF config solve this? A: Only if all your zones are in that account. Often not the case when you reach the scale where my tool comes in handy.<p>The UX is a bit quirky - people have to upload the list of zones with API credentials via a CSV file. I chose this approach for the MVP because I didn’t want to invest time in a) figuring the UI flow, and b) building the right safeguards for storing this highly-sensitive data.<p>I’d like to expand it to managing all Cloudflare settings, and to add templates - but it’s a big endeavor. I want to figure out a monetization strategy first - I’ve no clue at the moment.<p>Welcome any feedback - whether it’s on its positives, or flaws! It’ll help me decide whether to invest more time into this project. Thanks!