Notion Postmortem Autopilot (Mortis)
What We Built
Mortis is an end-to-end incident response system that turns real-world signals into structured postmortems automatically.
When an incident happens (failed deploy, bug, outage), the system detects the signal, generates a structured postmortem draft using AI, writes it into Notion, and routes it through a human approval workflow. Over time, it learns from past incidents and builds organizational memory.
The architecture includes a FastAPI backend for ingestion and orchestration, a Next.js 14 dashboard for review and workflow management, and a shared schema package (JSON Schema and TypeScript types) to keep the frontend and backend aligned.
Mortis also extracts recurring failure patterns into a pattern registry. These patterns are later used to generate pre-mortem warnings during deployments, improving reliability over time.
Problem It Solves
After incidents, teams often lose time gathering context from different tools like Slack, tickets, and logs. Postmortems are frequently delayed, incomplete, or inconsistent, and the insights rarely get reused effectively. As a result, the same issues tend to repeat.
Mortis addresses this by generating a complete first draft instantly, including severity, root cause hypotheses, a five-whys-style analysis, and action items. It integrates directly with Notion, where teams already work, and provides a review queue so humans can approve, reject, or refine the output.
Instead of static documentation, incidents become structured knowledge that compounds over time.
Video Demo
https://drive.google.com/file/d/1oHYhNEyjL__4FjlYfNlXn1I3WBTxZPl_/view
Show Us the Code
Frontend: https://global-hack-week-winning-idea-bq8e-ke4i8jc7z.vercel.app/queue
Backend: https://notion-postmortem-api-production-834e.up.railway.app/
How We Used Notion MCP
Notion MCP is used as the integration layer between the system and Notion.
It enables the backend to create structured postmortem pages with consistent schemas, write incident data directly into Notion databases, and maintain a standardized format across all entries. Teams can then collaborate and make edits inside Notion after the initial draft is generated.
This approach keeps Notion as the system of record, while the backend handles automation and logic, and the frontend handles visibility and approvals. It allows the system to scale without relying on Notion for business logic.
Key Features
- Automatic postmortem generation
- Structured root cause analysis (five-whys format)
- Human-in-the-loop approval workflow
- Pattern registry for recurring incidents
- Pre-mortem deployment warnings
- Shared schema across backend and frontend
Future Vision
The goal is to evolve Mortis into a predictive reliability layer. Instead of reacting to incidents, the system would identify risks before deployments, suggest mitigations, and continuously learn from organizational data.
Built by @topupchips and @kkoorriii
Top comments (0)