Run incident review
like a program, not a punishment.

For platform leads and SRE managers running reviews across multiple teams: consistent structure, grep-able history, onboarding measured in minutes. Pilots are free — we'd rather earn the purchase order than decorate a sales deck.

The 90-day pilot

What you get

  • Team-wide activation codes — every engineer gets full generation limits instantly
  • Your standard sections baked into every generated draft
  • Bulk export of all documents your team generates (.md)
  • A named human answering email within one business day

What we ask back

  • Honest feedback from the people pasting timelines
  • One retro call at day 30 and day 85 (30 minutes each)
  • If the pilot succeeds, be reachable as a reference
  • No procurement paperwork up front — genuinely none

How billing works when the pilot converts

Plainly: we invoice, you pay by bank transfer. No card forms, no vendor-portal hostage situations, no chasing approvals through a checkout flow your finance team hates anyway. Annual prepay gets the discount below; PO-number friendly; net-15 terms available.

TierFitsPrice after pilot
PilotUp to ~50 engineers, 90 days$0 — genuinely free
TeamOne org unit, ≤25 engineers$720/yr — invoiced annually
OrgMultiple teams, SSO requirementsCustom — quoted with the pilot retro

Individual engineers never need any of this — the free tier covers real-world personal cadence, and self-serve Pro ($9/mo) exists for power users. Enterprise volume is where invoicing starts making sense.

Frequently asked by buyers' side

Do you have SSO?

Sign-in runs on WorkOS AuthKit today (Google/Microsoft/email with enterprise-grade session handling). SAML SSO and SCIM provisioning are scoped during pilots with interested orgs — AuthKit's paid features unlock without us building auth twice.

Where does our incident data go?

Your inputs generate the document and are stored solely so share links resolve. Nothing trains on your incidents; deletion requests honored at hello@postmort.dev. Infrastructure is Cloudflare Workers + D1 at the edge — no customer data leaves WorkOS/OpenRouter hands for identity and inference respectively.

Can we keep our current template?

Pilots include baking your section structure into generated drafts — most teams converge on ours because it matches what reviewers expect (exec summary → impact → timeline → 5-Whys → actions), but yours wins.

Why should we trust a young product?

You shouldn't blindly — that's why the pilot exists and costs nothing. Worst case you spent zero dollars and got free postmortem automation for one bad quarter. Best case your reviews ship in days instead of sprints.

Start a pilot

Tell us the rough team shape — activation codes usually go out same day.

Email sales@postmort.dev →

Or just email us directly — humans reply here.