Plain words
Nothing a beginner sees uses the words threshold, signal, provider or verdict. Those terms are correct and they are also a wall. There is a test in the codebase that fails if one appears on a beginner screen.
Every fake registration, every spam enquiry, every checkout bot makes a website slightly less trustworthy than it was the day before.
And the usual response to all of it is to make life harder for everybody. A CAPTCHA on the contact form. A checkbox at sign-up. Another puzzle at checkout. Nine visitors are inconvenienced so that one bot is delayed for about four seconds.
Somewhere along the way, "prove you are not a robot" became the opening line of most interactions online. You visit a site, you want to send a message, and before you can say anything at all you are identifying buses in a grid of photographs.
Good people should not be treated like suspicious visitors. Bots should.
That is the whole idea. Work out which submissions are actually suspicious rather than taxing everyone equally, and let the overwhelming majority of people finish what they came to do without noticing anything happened.
It is a harder problem to solve than showing everyone a puzzle. That is precisely why it was worth building.
The name
A gate is not a wall. Its job is not to stop people — it is to be the place where a decision gets made, quickly and quietly, by someone paying attention.
Not every visitor should be stopped. Not every visitor should be waved through. Gatekeep helps a website tell the difference, and gets out of the way the rest of the time.
That is also why there is no shield in the logo and no padlock anywhere on this site. The mark is a gateway seen from above: two posts and the gap between them.
What we hold to
Nothing a beginner sees uses the words threshold, signal, provider or verdict. Those terms are correct and they are also a wall. There is a test in the codebase that fails if one appears on a beginner screen.
Every decision is recorded with the reason attached, written as a sentence. If Gatekeep ever stops one of your customers, you should be able to find out why in under a minute.
Every figure on this site was measured against the shipping build. There is no "99.9% accurate", no invented time-saved calculation, and no review count.
About 380 bytes on a protected form, no JavaScript by default, and nothing loaded on a page view that does not need to be there. Protection you have to weigh against page speed is a bad trade.
If a verification service is down, forms keep accepting submissions. If our own code fails inside someone else's plugin, the submission goes through and the failure is recorded. An unprotected form is recoverable; a broken checkout is not.
The pricing page has a section listing what does not exist yet. It converts worse today and it is the reason anyone will still be here in three years.
The obvious question
Because a form security plugin that does not secure forms unless you pay is not a free plugin. It is an advertisement that happens to be installed.
The free version includes all 33 integrations, the whole scoring engine, the protection profiles, Monitor Mode, the activity log, the security score and the self-test. It genuinely stops spam on its own.
What you pay for is the part that needs maintaining rather than writing once: a list of 75,000 throwaway email domains that changes every day, and the work of keeping 33 integrations alive as their plugins ship major versions.
A subscription funds ongoing work. It does not unlock functionality that was being withheld.
How it gets built
Every integration is written against the actual plugin source and exercised against a live installation of it. The adapters for Divi, Elementor Pro, Bricks, Avada, Thrive, WPBakery, Oxygen, Gravity Forms, WooCommerce and BuddyPress were all built and tested that way, because writing an adapter from documentation and hoping is how integrations quietly stop working.
The test suite runs against three separate environments: WordPress 6.8 on SQLite, WordPress 7.0 with nine page builders installed, and a three-site multisite network on MariaDB with a Redis object cache.
What is not tested: PHP 7.4 and 8.0 pass static analysis but have never been run — the test matrix uses 8.3. Memcached object caches are untested; Redis is covered. That is on this page because you would rather find it here than in a support ticket.
That is the whole brief. Everything in the plugin either serves it or should not be there.