Lars Koudal

cleverplugins

Grumpy AI Gate helps you stay in control as AI features spread across WordPress. It observes and intercepts outbound HTTP that other code on your site already initiates (plugins, themes, or core)—so you can see which plugin was involved, how much activity you are seeing (including helpful estimates), and optionally stop unwanted WordPress AI Client traffic for specific plugins. This plugin does not call external AI APIs for its own dashboard, analytics, or licensing. Nothing is sent to us or to a third-party analytics service.
Why use it
<ul>
<li>Visibility — Dashboard summaries, a per-plugin usage table, and a request log so surprises become visible early.</li>
<li>Spend awareness — When other software calls paid APIs, usage adds up. Logging helps you notice patterns before invoices or quotas become a problem.</li>
<li>Safer sharing — Knowing what leaves your server makes it easier to decide what belongs in prompts and what does not.</li>
<li>Optional blocking — For paths that use WordPress’s AI Client, you can block generations from selected plugins under Grumpy AI Gate → Settings (save to apply).</li>
</ul>
How it works
<ul>
<li>When the WordPress AI Client is available, the plugin records those requests from core lifecycle hooks (other code still drives the actual generation).</li>
<li>For HTTP fallback, Grumpy AI Gate hooks WordPress’s HTTP API (for example <code>pre_http_request</code>) to inspect requests that are already in flight. If a URL matches built-in recognition rules for major AI providers, a log row can be stored. Grumpy AI Gate does not open those connections for its own purposes—it only filters and classifies traffic initiated elsewhere on the site.</li>
<li>HTTP fallback does not block outbound API calls in the current release—it is there so you still get visibility when plugins talk to providers directly over HTTP instead of (or in addition to) AI Client flows.</li>
</ul>
Compatibility
The plugin requires WordPress 7.0+ (matches Requires at least in the plugin header). On WordPress 7.x, it works with core AI Client functionality where available. Release testing included WordPress 7.0 Beta 5. HTTP fallback remains important on every supported version—it records calls to recognized provider endpoints that other plugins make directly over HTTP, which is still common alongside (or instead of) AI Client–based flows.
Privacy
Everything is stored locally in your WordPress database. There is no cloud account, no telemetry, and no third-party analytics from this plugin.
For technical details on logging, double-counting avoidance, and blocking limits, see the FAQ below.
<h3>External services</h3>
This plugin does not rely on third-party AI APIs, remote analytics, or any external service for its own features. All logging and settings stay on your site.
Provider names and URL patterns included with the plugin are local matching rules only. They let Grumpy AI Gate filter and classify outbound HTTP requests that plugins, themes, or WordPress core may already be sending. They are not a list of servers this plugin calls to power the admin UI or to “phone home.”
Your site may still contact third-party AI providers when you or other software use AI features—that traffic is separate from this plugin’s own network use (which does not include calling those providers for monitoring).

Grumpy AI Gate

Intercept and log AI-related HTTP from plugins/themes; optional AI Client blocking. All data stays on your server.

devlinduldulao

Devlin Accessibility Monitor for WooCommerce helps WooCommerce merchants observe live accessibility barriers while shoppers are actively using the storefront.
The plugin focuses on real-time friction signals instead of persistent analytics. Events are sanitized, streamed into a short-lived live buffer, displayed in the WooCommerce dashboard, and discarded automatically. Settings are stored with standard WordPress options, and the live buffer uses a WordPress transient rather than a custom database table or replay store.
This plugin is built for merchants, accessibility reviewers, QA teams, and WooCommerce builders who need to understand where accessibility friction is interrupting conversion-critical journeys without introducing heavy analytics tooling or long-lived shopper tracking.
<h4>What merchants get</h4>
<ul>
<li>A WooCommerce dashboard that surfaces live accessibility friction as it happens</li>
<li>Merchant-only preview scenarios for demos, QA walkthroughs, and stakeholder reviews</li>
<li>Recommended actions that adapt to the current friction summary</li>
<li>Privacy-first capture with coarse categories only</li>
<li>No custom tables, no Redis requirement, and no third-party telemetry</li>
</ul>
<h4>Good fit for</h4>
<ul>
<li>Stores that want a lightweight live accessibility signal layer inside WooCommerce</li>
<li>Teams that need stakeholder demos before live storefront traffic is available</li>
<li>QA and product teams reviewing cart, checkout, product, and catalog usability</li>
<li>Merchants who want operational visibility without session replay or behavioral surveillance</li>
</ul>
<h4>Signals detected</h4>
<ul>
<li>Dead clicks on non-interactive elements</li>
<li>False interactivity after repeated dead clicks</li>
<li>Missing focus visibility during keyboard navigation</li>
<li>Broken aria relationships</li>
<li>Repeated invalid form interactions and unlabelled fields</li>
<li>Repeated tab loops inside overlays</li>
<li>Keyboard trap risk</li>
<li>Recovery events when a previously detected issue resolves</li>
</ul>
<h4>Privacy-first design</h4>
<ul>
<li>No typed values are stored</li>
<li>No IP addresses are stored</li>
<li>No session recordings are created</li>
<li>No external analytics or tracking libraries are used</li>
<li>No custom database tables are created</li>
<li>No Redis or paid cache service is required</li>
</ul>
<h4>WooCommerce implementation</h4>
The first release targets WooCommerce cart, checkout, product, and catalog experiences. It uses the WooCommerce Settings API, the WordPress REST API, and standard hooks so the plugin remains portable to future platform-specific adapters.
<h4>Merchant preview mode</h4>
Store owners can turn on a merchant-only preview mode from the dashboard to simulate realistic accessibility issues without requiring live storefront traffic. The preview includes walkthrough scenarios for checkout friction, keyboard navigation, catalog browsing, payment failures, and mobile tap audits. The dashboard also surfaces recommended actions that adapt to the current live or synthetic friction signals.
<h4>Operational guardrails</h4>
<ul>
<li>Incoming event payloads are capped at 1 KB</li>
<li>Per-visitor event submission is rate limited</li>
<li>Dashboard and preview controls require merchant capability checks</li>
<li>Live signals expire automatically after the configured buffer window</li>
<li>Published plugin packages do not require Composer on the destination site</li>
</ul>

Devlin Accessibility Monitor for WooCommerce

See live WooCommerce accessibility friction as shoppers hit it — privacy-first monitoring without custom tables or session recordings.

Grumpy AI Gate vs Devlin Accessibility Monitor for WooCommerce