postmortem.so monitors your endpoints, detects incidents, and generates publish-ready post-mortems — automatically.
Free forever for 1 project · No credit card required
The problem
The average post-mortem takes 3–5 hours to write. Most teams skip them entirely. The ones that don't ship them days after the incident — when the details are already fuzzy.
Someone has to dig through logs, Slack threads, and Grafana screenshots just to piece together what happened.
Post-mortems vary by author, team, and how tired everyone is. Most are forgotten in a Confluence graveyard.
Engineers write post-mortems while already behind on the next sprint. Quality suffers. Nobody reads them.
How it works
Add your API endpoints. We check them every minute from multiple regions, recording latency and status codes.
Three consecutive failures open an incident automatically. Subscribers and on-call get emailed within seconds.
Claude reads the full check history and writes a publish-ready post-mortem. Review it, publish it, done.
See it in action
Real output from a real incident. Claude analysed 47 minutes of check data and produced this — no human input required.
A 47-minute outage of /v1/payments/charge caused approximately 3,200 failed payment attempts on 14 February 2025 between 14:03 and 14:50 UTC. The root cause was connection pool exhaustion on the primary PostgreSQL replica, triggered by a 3× traffic spike during a flash sale.
A flash sale drove checkout traffic to 3× baseline. The payments service exhausted its PostgreSQL connection pool (limit: 100). Incoming requests queued, hit the 30-second timeout, and returned HTTP 503. The connection pool limit had not been reviewed since the service's initial deployment 14 months prior.
Pricing
Start free. Upgrade when you need AI post-mortems or more projects.
Free
For personal projects and side hustles.
Pro
For teams that ship fast and recover faster.
Team
For engineering organisations with compliance requirements.