Skip to content

Fawdy, the AI
Reliability Engineer

Fawdy product interface showing an incident investigation chat with a drafted RCA artifact

Use cases

Root Cause Analysis
web-prod-03SEV-1

Root Cause

pgbouncer crashed 6h ago and was not restarted, causing 847 direct connections to flood PostgreSQL and trigger the OOM killer.

Timeline

  1. 03:12PagerDuty alert: high memory
  2. 03:12Fawdy connects via SSH
  3. 03:14847 idle connections found
  4. 03:15Root cause identified

Action Items

P0Restart pgbouncer
P1Add systemd restart policy

Works across Linux and Windows — comfortable on the systems your team already runs

Meet your new favorite coworker

Fawdy avatar
FawdyAI Reliability Engineer
On call
Acking PagerDuty alert #4471...0.0s
Find the bad deploy from 14:32
Investigate legacy-billing-03
Post RCA draft in #sev-2-payments

Tells you what broke

Fawdy reads the logs, the metrics, and the recent deploys, then gives you a real answer. Not "have you tried restarting it."

Finishes the writeup

No more incidents ending with "we'll write it up later" and then nobody does. Fawdy drafts the timeline, root cause, and fix while it's still fresh.

Starts on day one

No agents, no ports, no two-week security review. Fawdy uses the access your team already has, the same way a new hire would on their first on-call.

Knows the boring stuff

Comfortable on the legacy servers nobody wants to be on-call for. The ones with no docs, no owner, and a runbook from 2018.