Changelog
Each row is a customer-visible change from the repository history, with the pull request number. Internal build, cache, and deploy commits are not listed. This is not a reconstruction of work from before these notes.
Shipped
| Date | What shipped |
|---|---|
| 2026-10-07 | When AWS changes the rules in a group you run, the Advisor will not say Promote from counts gathered on the older list. A new rule stays in count until it has its own count. A blocking group stays on its current version until you click Update, unless the only change is added rules, which start in count. |
| 2026-10-07 | A blocked visitor can report the Request ID from the default CloudFront block page, including one that ends with =. Stop watching removes a fitted rate limit that is still in count. That removal is a click. Support saves of custom rules and path exceptions record the same before and after the owner sees in change history. |
| 2026-10-07 | Tuning, rate cards, and the under-attack card show rule capacity. A Promote that would not fit stays Hold. Always allow runs first. A path allow runs after a temporary response, an IP block, a country block, and a rate limit, and it does not turn those off. A save that would not fit, or that would put rules in the wrong order, stops before anything changes. Saving custom rules or exceptions keeps a rate limit, a temporary response, or another exception that landed while the page was open. |
| 2026-10-07 | The Advisor remembers Undo, keep in count, a confirmed false positive, and a saved exception. A later card can only move to Hold or Needs allowlist, and you clear a lesson with a click. An active lesson does not expire on a timer. |
| 2026-10-07 | A blocked visitor can share the reference or report the block. The owner sees the matching request, the rule, and the Advisor’s read. A narrow exception, count, or Undo still takes a click. A report does not unblock anyone. |
| 2026-10-07 | When live traffic looks like an attack, Tuning and the sites list say so, and the attack-spike channel sends one note within its cooldown. A temporary rate limit, block, or challenge is narrow, expires, and is installed only after a click. Undo is read back from the firewall. Checkout, webhooks, verified crawlers, and Always-allow addresses stay out of that rule. |
| 2026-10-05 | A client viewer can turn on a weekly email of their own usage for the last 7 days. It lists only the client labels assigned to that login, with the same sites, live, needs attention, counted, and blocked as their page. A missing rollup stays not confirmed. It does not include other clients or the agency-wide file. It is off until they turn it on. The agency-wide weekly email stays with the owner and admins. |
| 2026-10-05 | When Report branding is set, the weekly client-usage email and the printable client usage summary show that agency name, https logo, and support line. If it is not set, the email stays the WAF Cybersecurity note. The rest of the dashboard is not rebranded. A client viewer still cannot turn the email on or download every client. |
| 2026-10-05 | Client usage can email the last 7 days once a week. It is off until you turn it on. The numbers match the page. A client viewer does not get that email. |
| 2026-10-05 | Billing and the trial recap name monthly or annual cadence. An annual plan shows the yearly total, not a $150 monthly total. Days left use the stored trial end when Stripe has one. |
| 2026-10-05 | Client usage groups sites by client label, with a printable summary and a CSV for the last 7 or 30 days. Counted and blocked stay separate. A client viewer cannot download the agency-wide file. |
| 2026-10-05 | Example Tuning adds a fictional WooCommerce store beside Example University. Login, a media file, cart, and checkout are example counts. Promote stays a human click. Bot management and account-fraud protection are not on in that example. |
| 2026-10-05 | Add several domains from one page, each with its own readiness answers. WordPress and WooCommerce templates preview groups and apply them in count only. Promote stays a human click. |
| 2026-10-05 | Public status page for this app. It is the current check only: the app, the health check, and whether that request came through the public edge. Customer edges are not listed. |
| 2026-10-05 | Investigate this request from Events or Tuning sends one counted or blocked sample to support. The outcome is recorded in change history. Nothing is promoted from that flow. |
| 2026-10-05 | Protection reports can show an agency name, https logo link, and support line from Account. Client viewers see the same header. Printing is still the handoff. |
| 2026-10-05 | Launch checklist beside Tuning, and a tuning review request that carries the Advisor verdict. Promote stays a human click. |
| 2026-10-04 | Public example Tuning walkthrough for a fictional site. Example data. You still click Promote. |
| 2026-10-04 | Live sites can show a CloudFront 5xx card when the origin looks unhealthy. It does not probe the origin or change WAF mode. Pull request 202. |
| 2026-10-04 | Setup failures name what happened, whether DNS or blocking changed, and one next step. |
| 2026-10-04 | Public DNS cutover and rollback page, with a save-your-records reminder on the go-live checklist. |
| 2026-10-04 | Hold and Needs allowlist cards say what would change the recommendation. Pull request 192. |
| 2026-10-04 | Read-only per-site WAF change history. Pull request 191. |
| 2026-10-04 | Trial recap of protection so far, without inventing zeros. Pull request 190. |
| 2026-10-04 | Read-only Estate Brain for multi-site owners and the fleet. Pull request 189. |
| 2026-10-04 | CVE-to-count virtual patch card on Tuning. Pull request 188. |
| 2026-10-04 | Dismissible next-step card on the first-run path. Pull request 187. |
| 2026-10-04 | Count-window timeline on Tuning. Pull request 186. |
| 2026-10-04 | Printable per-site protection report. Pull request 185. |
| 2026-10-04 | The Advisor holds unless the window and the samples are safe. Pull request 184. |
| 2026-10-04 | Alert mail names the spike, waits out a cooldown, and points at one next click. Pull request 182. |
| 2026-10-03 | Public example WAF Cybersecurity Advisor page. Pull request 180. |
| 2026-10-03 | Needs allowlist path for false positives, including saving the allowlist. Pull request 179. |
| 2026-10-03 | Multi-site queue for what needs a human. Pull request 178. |
| 2026-10-03 | Go-live state stays honest until DNS points at CloudFront. Pull request 177. |
| 2026-10-03 | Analytics and the Advisor share one WAF traffic rollup. Pull request 176. |
| 2026-10-03 | Email when rules are ready to promote. Pull request 175. |
| 2026-10-03 | Count-to-promote loop explains evidence, preview, and undo. Pull request 174. |
| 2026-10-03 | Scan-to-trial next click on the public funnel. Pull request 171. |
| 2026-09-16 | Operator guides for setup, concierge DNS, refer-a-friend, platforms, and campus estates. Pull requests include 145, 146, 148, 152, 153, and 155. |
| 2026-09-14 | Optional origin verify header on Advanced. Pull request 127. |
| 2026-09-10 | Scan-to-trial funnel, including an optional email of the grade. Pull request 124. |
| 2026-09-08 | Site Analytics: 24-hour, 7-day, and 30-day ranges. Pull request 114. |
Guide and blog posts shipped in the same history are linked from Guides and Blog. They are explanations, not extra product behavior beyond the pages above.