Gus can
- •Diagnose plugin/theme conflicts, white screens, and 500 errors
- •Safe core/plugin/theme updates with automatic rollback
- •Isolate broken updates and patch incompatibilities
- •Bulk operations across your fleet with smart scheduling
- •Surface neglected “ghost” sites before clients notice
- •Draft and apply code-level fixes when permission allows
Gus won’t
- •Replace your judgment on product/design decisions
- •Bypass your approval mode when a site is set to ask-first
- •Claim malware removal parity with dedicated security suites (yet)
- •Act without an audit trail — every step is logged
Permission levels
Per site, choose how much autonomy Gus has. Monitoring tools only alert. Gus acts — inside the rails you set.
Observe
Diagnose and recommend only. No production writes.
Ask first
Queue every change for your approval before apply.
Auto-resolve
Fix within policy: rollback, isolate, safe patches.
Resolution narratives
Checkout 500 at 3:04 AM
- 3:04 AM — Plugin update conflicted with WooCommerce; /checkout returned 500.
- 3:04 AM — Gus rolled back, isolated the conflict, patched, redeployed.
- 8:30 AM — You read the closed incident in the log. Client never knew.
White screen after PHP bump
- Staging-first run caught a fatal in a legacy plugin.
- Gus held production, queued an ask-first note with the stack trace.
- You approved a targeted disable; site stayed up.
Ghost site resurfaced
- Gus flagged a site with no heartbeat in 14 days.
- Connector reconnected; outdated plugins queued for safe update.
- Client report included the recovery — retainer justified.
Frequently asked questions
The objections we hear most — answered up front.
Start free trial
Or read Security & trust