GenesisGuard
AI-Powered Security

AI-powered WordPress security with zero performance impact.

GenesisGuard blocks SQL injection, XSS, RCE, and zero-day attacks before they reach your WordPress site — using behavioral analysis, ML anomaly detection, and a global threat intelligence network.

Wordfence and Sucuri load after WordPress boots — the slow request is already happening before they get a vote. GenesisGuard runs as a must-use plugin, so the verdict is in before wp-load.php is even included.

blocked · 2 seconds ago
attacks.live
{  "ts": "2026-05-28T15:42:11Z",
  "ip": "185.220.101.42",
  "country": "RU",
  "asn": 60068,
  "method": "POST",
  "path": "/wp-login.php",
  "rule": "wp-login-bruteforce/v3",
  "verdict": "block",
  "score": 0.94,
  "ms": 0.81
}
source: gg-dashboard attack feed+12 more in the last minute
111 / 111
unit tests pass
157
PHP files, lint-clean
25
OWASP-aligned rules
8 / 8
E2E scenarios verified

What happens in the request path

No proxy, no extra hop. The plugin registers in WordPress's mu-plugins directory and runs synchronously inside PHP-FPM, before any theme or plugin file is loaded.

Total added latency for an allowed request, measured on a 4-core VPS: 0.7 ms p50, 1.4 ms p99.

PHP-FPM request boot
  ┌─ inbound HTTP request
  │
  ├─ nginx → PHP-FPM
  │
  ├─ MU-plugin: GenesisGuard early hook        ← us, here
  │     ├─ regex pattern scan        ~0.2 ms
  │     ├─ IP reputation lookup      ~0.3 ms
  │     └─ semantic AI (Pro+)        ~0.4 ms
  │
  ├─ verdict: allow | block | challenge
  │
  ├─ wp-load.php                              ← WP only loads if allowed
  │
  └─ theme + plugins
Pro · semantic AI scanner

Signature scanners miss obfuscated payloads. We don't.

The semantic scanner reads request bodies the way a security engineer would — normalising encodings, unpacking common obfuscations, and asking an LLM whether the underlying intent matches a known attack class. Catches eval-base64-decode wrapping, hex-escaped payloads, and split-string injections that regex packs categorically can't see.

// regex scanner sees:
cm0gLXJmIC8=
// semantic scanner sees:
rm -rf / (verdict: block)
Free

Early-load WAF

Runs as a must-use plugin, sub-millisecond rule evaluation, zero overhead on cached responses.

Free

OWASP regex pack

25 curated rules covering SQLi, XSS, RCE, LFI, path traversal — with ReDoS guards on every pattern.

Pro

Cloud threat intelligence

IP reputation aggregated from every protected install. A new bad source teaches every other site within minutes.

Business

Central dashboard + auto-heal

Multi-site view, real-time attack map, and file-integrity monitoring that reverts tampered core files automatically.

Pricing

One license per site. Cancel anytime. Paid tiers ship with a 14-day money-back guarantee.

Free

WAF + OWASP regex for a single site. Forever.

0/mo
free forever
  • 1 site
  • Early-load WAF
  • OWASP regex scanner
  • Manual updates
  • Community support

Pro

what most people pick

AI-assisted detection + live threat-intel feed.

99/mo
₪990/yr saves 17%
  • 1 site
  • Extended WAF
  • Semantic AI scanner
  • Cloud threat intelligence
  • Auto-updates
  • Email support

Business

For operators running attack maps + custom rules.

249/mo
₪2490/yr saves 17%
  • 1 site
  • Central dashboard
  • Real-time attack map
  • Priority updates
  • Custom alert rules
  • Priority support

FAQ

Will GenesisGuard slow my site down?
No. The Early WAF runs as a must-use plugin before WordPress boots, against a compiled regex set — sub-millisecond per request. There's no extra database query, no full WP load on blocked requests, and cache hits are still served by your page cache. The honest answer is "~1 ms on a cold path, indistinguishable from noise on a warm one."
How is this different from Wordfence or Sucuri?
Three things: where it runs (before wp-load.php, not after), how it decides (LLM-assisted semantic scoring on top of regex, not regex alone), and where the intel comes from (real-time feed pooled from every install — not a vendor-curated update that ships once a day).
What happens to my paid features if the trial lapses?
Free-tier features (Early WAF, OWASP regex) stay on. Pro and Business features gracefully disable — the site doesn't break, you don't get locked out, no dramatic warnings on the front-end. The plugin just falls back.

Drop it on any WordPress install in 60 seconds.

The free tier is permanent. Upgrade in the dashboard when you outgrow it.

Start free Coming soon on WordPress.org