Documentation
Run CrashPilotX professionally.
CrashPilotX uses an outbound-only Ubuntu agent, Supabase-backed storage, and a dense incident dashboard so you can keep crash evidence without opening inbound ports.
Install the agent
Create a system in the dashboard, copy the one-line installer, and verify the first heartbeat in Systems.
Monitor health
Use Health and System detail to review online status, active alerts, dmesg, capacity forecasts, and retention budgets.
Manage storage
Set per-system retention days and storage budget. CrashPilotX prunes old metric, heartbeat, alert, and incident rows as new data arrives.
Investigate incidents
Assign owners, override severity, close ignored reports, export postmortems, and keep audit history.
Get notified
Configure a Slack or generic webhook on the Health page so new alerts reach you without the dashboard open.
Recommended workflow
- 1. Connect each Ubuntu or WSL host from Systems.
- 2. Review Health daily for offline hosts, active warnings, and storage pressure.
- 3. Triage Incidents by severity, owner, and lifecycle state.
- 4. Export postmortems for major crashes and close noisy warnings.