Hi HN, I built IncidentPost (https://incidentpost.vect.pro) to solve a simple but recurring problem: writing clear, public incident postmortems without standing up a full status page or internal tooling. Many teams want to be transparent after outages, but tools like Statuspage or custom Notion/GDocs either feel too heavy or aren’t meant for public sharing. IncidentPost focuses on one thing:

writing and publishing clean, public incident reports

with a simple, structured format (timeline, impact, root cause, resolution, prevention)

accessible via a single public URL

It’s intentionally minimal:

no accounts required to read

no complex workflows

no vendor lock-in mindset

The goal is to make postmortems easier to publish, not harder. This is early-stage and feedback-driven. I’d really appreciate thoughts from engineers, SREs, or founders who’ve written incident reports in the past:

What’s missing?

What feels unnecessary?

Would you use something like this?

Thanks for reading.