Skip to content

Commit 5f229e7

Browse files
authored
docs(wporg): 'Who builds WebDecoy?' FAQ - platform team, not a plugin shop (#76)
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.
1 parent fc70701 commit 5f229e7

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

readme.txt

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -160,6 +160,10 @@ The threshold is fully configurable to match your site's needs.
160160

161161
== Frequently Asked Questions ==
162162

163+
= Who builds WebDecoy? =
164+
165+
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.
166+
163167
= Is WebDecoy an invisible reCAPTCHA alternative? =
164168

165169
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.

0 commit comments

Comments
 (0)