HOME / PRODUCT
The reliability layer for WordPress
FaultPilot is a WordPress reliability, diagnostics and recovery engine — a single system that observes, explains, prevents and recovers. Built for people who treat WordPress like production infrastructure.
Not a logger. Not a scanner. An engine.
Most WordPress tools do one thing: dump errors, run a scan, or ping a URL. FaultPilot is designed as a complete reliability loop — the same discipline site reliability engineers apply to infrastructure, applied to WordPress.
It lives inside your site, observes real request traffic, normalizes what it sees into fingerprinted signals, groups those signals into incidents, correlates them with the changes that caused them, and — when things go seriously wrong — gives you recovery mechanisms that work even when wp-admin does not.
500 Internal Server Error — check your logs
// FaultPilot
INC-1042 critical · FP-82A19C · 37 occurrences
component: woocommerce-emailer 3.4.1 (by file path)
change: update 3.4.0 → 3.4.1 @ 14:02 · failure @ 14:32
confidence: Strong correlation
recovery point: available (14:01:47, pre-update)
action: quarantine plugin / rollback — your call
Architecture
Three tiers, one contract
FaultPilot is modular and container-wired: every capability is a lazily-factored service, adding near-zero cost to requests that are not its own.
Design principles
The rules the engine is built on
Honesty over spectacle
Checks return “skip” with a reason when data is not observable. The analyzer returns confidence tiers, never certainty. Sections without data say “not observable”. A reliability tool that lies to you is worse than no tool.
One storage contract
All persistence goes through a single store interface. Runtime uses portable SQL; the architecture leaves room for future remote storage without touching the engines that produce the signals.
Near-zero overhead
Zero front-end overhead; admin assets load only on FaultPilot screens; events are buffered per request and batch-written; deprecations are sampled; heavy work runs in wp-cron.
Prepare for AI, require nothing
A stable, structured diagnostic-context payload exists for a future AI layer — but no diagnostic depends on an external service. Everything works offline, locally, privately.
Scope — stated plainly
What it is, and what it is not
WordPress 6.0+
Works on single site and multisite, with or without WooCommerce.
PHP 7.4+
Degrades loudly on older versions — never fatally.
Zero front-end
Collectors ride existing hooks; nothing extra renders on public pages.
GPL-2.0-or-later
Free Edition available today. Commercial editions in preparation.
See the engine work
The demo walks through a realistic incident with the actual information model.