What problem does it solve? Securing a Vercel project against attacks and abuse requires navigating custom WAF rules, IP blocking, rate limiting, and emergency attack response, and a single misconfigured rule can block real users or break production traffic. ## Core Features & Use Cases - Custom WAF Rules: Create, edit, reorder, and stage firewall rules with conditions on paths, headers, geo, JA4 fingerprints, and actions like deny, challenge, log, bypass, and rate_limit. - IP Blocking & System Bypass: Block abusive IPs or CIDRs and exempt trusted networks from all firewall checks, with staged drafts and publish workflows. - Attack Response & Rate Limiting: Guide Attack Mode activation, DDoS mitigation controls, and per-endpoint rate limit rules with a staged log-first rollout. - Use Case: When an API endpoint is being hammered by abusive clients, stage a rate_limit rule in log mode, review firewall metrics, then tighten and enforce it in production without touching legitimate traffic. ## Quick Start Ask the assistant to add a Vercel firewall rule that rate limits the /api path to 100 requests per minute per IP, staged as a draft for review.
