I built IncidentPost because I realized that the worst part of an outage isn’t the fix—it’s the three hours of manual log-digging and report-writing that follows when you’re already exhausted.
Most of us just want to ship the report and get back to sleep, but stakeholders need professional transparency.
What it does: You paste your raw incident notes, Slack timestamps, or CLI logs. The AI (Gemini) reconstructs the timeline, identifies the root cause (using 5 Whys logic), and generates a professional markdown report.
Why I built it this way:
No Subscriptions: I’m tired of everything being a SaaS. This is a one-time payment per incident. If you don't have outages, you don't pay. No Signup Required: You can generate and preview the whole report for free without giving me your email. Export-Ready: It gives you the markdown, a public incident page, and even drafts for HN/Twitter. Privacy: We focus on a "No-PII" workflow. Users confirm no private data is pasted, and we process it to generate the report.
I'd love to hear your feedback on the report structure and what other export formats (Jira? Confluence?) would actually be useful in your workflow
check here: https://incidentpost.vect.pro/