After an outage, your biggest customers want the full story: timeline, root cause, what changes. That level of detail doesn't belong on a public status page, but it shouldn't be a messy email thread either.
Why not a public link or an attachment
A private postmortem page lets you include architecture details and graphs that you'd never put on a public blog, and you control exactly who can read it.
Your agent can draft it from the incident channel and logs, then publish it locked when you say "share the postmortem with the affected accounts".
Settings that fit
A per-customer password if accounts shouldn't see each other's details.
--block-pii so a pasted token or key stops the publish.
--expire 60d to retire the page after the follow-up review.
FAQ
Can I update the postmortem as we learn more?
Yes. Republish with the same slug and password (-s inc-1118 -p ...) and the same link serves the update.
Can my AI agent do this for me?
Yes. Hushdrop ships as a CLI, an MCP server and a SKILL.md, so Claude Code, Codex, Cursor, Gemini CLI or anything that can run a shell command or call an MCP tool can publish for you. Tell it "share this with the client, locked" and it returns the link and password.
Turn a page into a link right now
Free, no account. Paste HTML here, or connect your agent once and it publishes for you.