When the book grows from a few retainers to a dozen sites, the question is no longer “did I see the CVE email?” It is “which client do I touch in this two-hour block?”
You do not have a bench of juniors. Security work competes with builds, content edits, and invoices. Plugin dashboards and host notices still arrive per site, so the loudest client — or the last tab you had open — gets the attention, not the most exposed install.
WP Triage is a decision engine for that constraint: one list, one score, a top-three fix order. It is not a remote admin, backup product, or firewall. Keep the tools you already use to apply patches; use triage to pick the work.
That pattern fits retainers you already sell. For a fuller agency-shaped Monday/Friday cadence, see for agencies. For how the numbers are produced, see WordPress risk scoring.
False positives and accepted risk can be suppressed per site or across the account. Guide: suppressing findings.
Many freelancers already have Wordfence (or host WAF), ManageWP or MainWP for updates, and a backup plugin. Those products execute. WP Triage orders. Compare the fit on comparisons.
Public beta includes 2 sites free. Starter covers 1–5 sites at $9/mo; Pro covers 6–25. Full table: pricing.
Yes. Freelancers with a growing book of client sites use WP Triage to see the highest-risk install and the next fix without buying an agency dashboard stack.
Public beta covers two sites so you can try the loop. It becomes obviously useful once you cannot keep every client changelog in your head — typically five or more installs.
No. You still apply updates in WordPress, WP-CLI, or a manager. WP Triage tells you which site and which issue to spend the next hour on.