From f89a6fb0206ed3cb6a746d85ff7e0b97877551ea Mon Sep 17 00:00:00 2001 From: Chris Portscheller Date: Mon, 17 Aug 2026 21:18:46 -0500 Subject: [PATCH] docs(wporg): 'Who builds WebDecoy?' FAQ - platform team, not a plugin shop The listing read like a solo plugin developer's project. The honest counter: the detection engine is shared with the Node SDK, edge validator, and cloud platform, parity-tested across languages, and the freemium split is a deliberate business model, not a hobby. --- readme.txt | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/readme.txt b/readme.txt index 4ffe93d..fade48a 100644 --- a/readme.txt +++ b/readme.txt @@ -160,6 +160,10 @@ The threshold is fully configurable to match your site's needs. == Frequently Asked Questions == += Who builds WebDecoy? = + +A team of security engineers who do bot detection full time, across more than WordPress. The detection engine in this plugin is the same one that runs in our Node.js SDK, our Cloudflare edge validator, and the WebDecoy cloud platform; the WordPress rules engine is kept byte-for-byte compatible with the Node implementation by a shared test suite. The plugin is free and fully functional because detection is the half of the problem we give away: the paid product is the network response built on top of it. + = Is WebDecoy an invisible reCAPTCHA alternative? = For most sites, yes. WebDecoy protects comment, login, and registration forms with invisible honeypot fields, behavioral scoring, and a background proof-of-work challenge, so real visitors never solve a puzzle, pick out traffic lights, or click a checkbox. If a request looks suspicious, the challenge runs silently in the browser instead of interrupting the person. And unlike reCAPTCHA, nothing about your visitors is sent to a third party.