Free
Live error log viewer
Read your debug.log and the PHP error log right in wp-admin — fatals, warnings, and deprecations, grouped with counts, searchable, updating live. No FTP, no SSH, no downloading log files.
Crash → one-tap fix
Your site crashed.
One tap brings it back.
FatalGuard catches the fatal behind the white screen, texts you the second it happens, and hands you a one-tap link to turn off the culprit and restore the site — no FTP, no wp-config, no panic.
- < 5s
- crash → alert
- ∞
- recoveries, free
- 0
- wp-config edits
Free on wordpress.org, works on any host, AI-ready via MCP, GPL licensed.
The white screen of death
A blank page tells you nothing. Your client tells you everything.
When a fatal error hits, WordPress shows a blank white page — no error, no clue, no notice to you. On a site you check hourly, that's an annoyance. On a client site you touch once a month, it can sit broken for days, costing sales and trust, until an angry email arrives. The crash isn't the problem. Finding out last is.
debug.log · live tail streaming
[20-Aug-2026 04:12:07 UTC] PHP Fatal error: Uncaught Error: Call to undefined function acme_init() in /wp-content/plugins/acme/acme.php:42 [20-Aug-2026 04:12:07 UTC] Request: POST /checkout [20-Aug-2026 04:11:55 UTC] PHP Deprecated: Passing null to parameter #1 [20-Aug-2026 04:09:31 UTC] PHP Warning: Undefined array key "gateway_id"
How it works
From crash to fixed, in seconds.
- 01
Install & activate.
A self-installing drop-in starts watching every request. Nothing to configure, no wp-config editing.
- 02
A fatal hits.
FatalGuard captures it — type, message, file:line, and the URL that triggered it — instead of letting the page die silently.
- 03
You're told, and you fix it.
An instant alert lands on your phone with the error and a one-tap “turn off the culprit & restore” button. Site back in seconds.
Pro · the AI wedge
The first WordPress error monitor your AI can actually read.
Every dev now debugs alongside an AI — but it can't see your site. FatalGuard is the only WordPress error/log plugin that plugs straight in: connect Claude, Cursor, VS Code, or any MCP client and ask about your site in plain English, answered from your real error history. Read-only, secured by a scoped, revocable key. No pasting stack traces — the assistant has already read your logs.
Claude Cursor VS Code any MCP client
See how AI access works Claude · connected to fatalguard
What's the most recurring error on my site this week?
fatalguard · query_error_history · since=7d
A PHP fatal, by a wide margin — ×37:
Uncaught Error: call to undefined function acme_init()
at
/wp-content/plugins/acme/acme.php:42.
Started after Acme 3.2 auto-updated. Roll back to 3.1 to stop the white screens.
Which deprecations are in my active theme? What broke after my last deploy? Show me every fatal from WooCommerce this month.
What's inside
A log viewer, an alarm, and a fix button — in one plugin.
Free
White-screen recovery
When a plugin crashes the site, the alert carries a secure one-tap link to deactivate exactly that plugin and restore the site. Unlimited, on every plan.
Free
Telegram alerts
Get pinged the instant a fatal happens — delivered by Telegram, so the alert reaches you even when wp-admin itself is down.
Pro
AI access (MCP)
Connect Claude, Cursor, or any AI and ask what's crashing your site in plain English — answered from your real error history, read-only.
Pro
Searchable error history
Every fatal kept in a database — grouped, with counts and first/last-seen — so you can answer “when did this start?” long after the log rotated away.
Pro
More channels
Slack, Discord, email, and custom webhooks — send alerts wherever your team works.
Pro
Built for agencies
Route a plugin's fatals to their own chat, hide the plugin from client admins (stealth mode), and get a weekly email digest.
Pro · error history
Every fatal, searchable — long after the log is gone.
Log files rotate and truncate, so “when did this start?” is usually unanswerable. Pro keeps every fatal in a database, grouped, with counts and first/last-seen — the timeline that pins an error to the change that caused it.
search errors…
Fatal Deprecated Warning
- Fatal ×37
Uncaught Error: call to undefined function acme_init()
plugins/acme/acme.php:42 · first 3d ago · last 4m ago
- Fatal ×4
Allowed memory size of 268435456 bytes exhausted
plugins/woocommerce/includes/wc-core.php:118 · first 9d ago · last 2d ago
- Deprecated ×512
Passing null to parameter #1 ($string) of type string
themes/aurora/functions.php:301 · first 21d ago · last 1m ago
- Warning ×63
Undefined array key "gateway_id"
plugins/pay-lite/checkout.php:77 · first 6d ago · last 12h ago
Why not just… the tools you already have?
| FatalGuard | Query Monitor | Manual debug.log | Email-only plugins | |
|---|---|---|---|---|
| Catches the white screen of death | Included | Not included | partial | Included |
| Alerts you off-site (phone) | Included | Not included | Not included | Included |
| Works when wp-admin is down | Included | Not included | Not included | partial |
| One-tap recovery / restore | Included | Not included | Not included | Not included |
| Grouped, searchable log viewer | Included | Included | Not included | Not included |
| Database history (first/last-seen) | Included | Not included | Not included | Not included |
| AI access (MCP) only us | Included | Not included | Not included | Not included |
*debug.log records the error but shows you nothing until you go read the file.
- < 5s
- from crash to alert
- 0
- lines of wp-config to edit
- ∞
- one-tap recoveries on free
- [X]+
- active installs
Built for the people who get the 2 a.m. message.
⚠ Placeholder quotes — replace before launch
“I found out a client's checkout had been down for a day — from the client. Never again. FatalGuard pings me before they notice.”
[Name], freelance WordPress dev]
“The one-tap restore link is the whole thing. A plugin update took a site white; I fixed it from my phone on the train.”
[Name], agency lead]
“Being able to ask Claude “what's crashing this site this week” and get a real answer is unreasonably good.”
[Name], full-stack dev]
Sends where you already are.
- Telegram
- Slack
- Discord
- Custom webhooks
- Claude
- Cursor
- VS Code
Free to catch & recover. Pro to debug with AI.
Free
$0 / forever
- 1 site
- Live log viewer
- Telegram alerts
- Unlimited one-tap recovery
- 🔒 AI access (MCP) — available in Pro
Most popular
Pro Solo
$39 / year
- AI access (MCP)
- Searchable error history
- Slack / Discord / email / webhook
- Alert routing · stealth mode
- 1 site (+ subdomains)
Pro Agency
$99 / year
- AI access (MCP)
- Everything in Pro Solo
- Up to 20 sites
- Priority support
- Central dashboard (coming soon)
14-day money-back guarantee. No account needed for the free version. Compare every plan →
FAQ
Questions devs actually ask.
Does it work on any host?
Yes. FatalGuard needs no special server access, no shell, and no wp-config editing. It runs on shared, managed, and self-hosted WordPress alike (WordPress 6.0+, PHP 7.4+).
Will it slow my site down?
No. It's a tiny drop-in that stays out of the way and only acts when a fatal actually occurs. There's no heavy background process on normal requests.
How do I get the alert if the whole site is down?
The alert and recovery link go out over Telegram (and your other channels), delivered by their servers — not by your site. So you still get it when wp-admin is unreachable.
Do I need an account?
No for the free version — install it and go. Pro is delivered as a license key; no third-party account required to receive alerts.
Is it open source?
Yes. The free version is GPL and hosted on wordpress.org.
What's the difference between Free and Pro?
Free catches fatals, shows the live log viewer, sends Telegram alerts, and gives unlimited one-tap recovery. Pro adds AI access (MCP), searchable database history, Slack/Discord/email/webhook channels, alert routing, stealth mode, and a weekly digest.
Can I really use AI to debug my site?
Yes — Pro exposes a read-only MCP endpoint. Connect Claude, Cursor, or VS Code and ask about your errors in plain English. It can read your history; it can't change anything.
Can I upgrade later?
Anytime — start free, move to Pro Solo or Agency whenever you need the extra channels, history, or site count.
Stop finding out about crashes from your clients.
Install FatalGuard, connect Telegram, and the next fatal is a 30-second fix from your phone — not a two-day outage.