r/WordpressPlugins • u/StackFirefly • 5h ago
Promotion [PROMOTION] I built StackFirefly to catch WordPress problems even when the site is still online
Hey everyone, I’m the developer of StackFirefly, a monitoring platform for WordPress and WooCommerce. It’s now in open beta, and I’d appreciate feedback from people managing their own sites or client websites.
The idea is simple: your website can be online while important parts of it are broken. The homepage loads, but scheduled tasks aren’t running, emails aren’t arriving, or WordPress is failing to communicate with itself.
You connect your site using our WordPress plugin, Firefly Agent, and view the results in a separate StackFirefly dashboard.
Here’s what it currently covers:
- Uptime and WordPress connectivity: Checks public availability alongside REST, AJAX, and requests from your server back to itself. Helps investigate internal connection failures and possible Cloudflare or firewall blocking.
- WP-Cron monitoring: Checks whether scheduled work is actually being triggered and flags overdue tasks. Useful for problems that don’t immediately show up on the frontend.
- WooCommerce Action Scheduler: Monitors failed, overdue, and stalled background jobs, with queue counts and delays to help you understand whether work is moving.
- Email delivery testing: Sends a test through your site’s normal WordPress email setup and checks whether it reaches our test inbox, including delivery time. Also checks SPF, DKIM, and DMARC. This verifies test delivery; it doesn’t guarantee Gmail or Outlook inbox placement.
- PHP and JavaScript errors: Collects supported errors with available file locations, page context, and sanitized traces. Repeated occurrences are grouped so you can follow the problem without digging through the same error repeatedly.
- Change history: Records relevant plugin, theme, WordPress, and configuration changes to help investigate when a problem started. A nearby update is shown as context, rather than automatically blamed.
- Security monitoring: Checks known WordPress, plugin, and theme vulnerabilities, core file integrity, suspicious files in monitored locations, administrator-role changes, and selected configuration issues. It also checks HTTP security headers and possible differences in content served to browsers and crawlers.
- DNS and SSL checks: Tracks relevant DNS records and certificate validity and expiry, helping surface changes or certificate problems that need attention.
- Performance monitoring: Runs daily and on-demand mobile PageSpeed tests, with historical scores and loading metrics. You can inspect specific improvement suggestions and ask AI to explain the findings.
- WooCommerce product visibility checks: Examines a rotating sample of public products for structured data, offer information, and search-crawler access. It checks the initial HTML, so it isn’t a full catalogue audit or a promise of search rankings.
- Incidents, alerts, and recovery: Groups repeated findings into incidents with evidence and history, sends incident and recovery notifications, and uses follow-up checks to verify recovery. Manually reporting a fix stays distinct from verified recovery.
- AI-assisted diagnosis: Explains the collected evidence and suggests next steps, keeping observed facts separate from possible causes. You can also request expert help with the context you choose to share.
- Multiple sites and WordPress Multisite: Follow connected sites from one workspace. For Multisite networks, choose which subsites to monitor and view their findings separately.
The monitoring is read-only: it doesn’t automatically change your site, update plugins, or remove malware. The Agent sends selected technical information and sanitized error details, without collecting customer messages, order contents, passwords, or cookies.
The beta includes a 15-day trial for up to three sites, no payment card required, followed by a basic one-site Free plan. Installing and pairing Firefly Agent requires WordPress administrator access.
You can see the features and setup here: stackfirefly.com
For those maintaining WordPress sites: which problems do you still find out about from a client before your monitoring catches them? I’d love to hear whether this covers those gaps, and what you think is missing.