4 ways to configure the Vercel's firewall: 1. ClickOps via the UI 2. Using the API if you have really special requirements 3. Terraform for git controlled configuration management 4. And now via vercel.json as part of the deployment lifecycle These all have their trade-offs. We added the vercel.json option because some rules are quite static and folks wanted to just deploy them like other software. The regular activation cycle of firewall rules is not tied to Vercel deployments such that you *can* make changes in emergencies when deploying may be too slow or have negative consequences (like clearing caches)
Vercel’s WAF rules can now be managed directly in vercel.json. Both developers and agents can declaratively write and push rules that are versioned with code and tied to git commits. vercel.com/changelog/web-…