IncidentScribe v1.0 — an on-device postmortem drafter for the buyers cloud AI can’t reach
If you’re an SRE at a regulated bank, a healthcare company, a defence contractor, or a post-2023 Samsung-shaped enterprise, you have an internal policy that prohibits pasting incident data into ChatGPT, Claude, or any other cloud LLM. The policy got written after one of the 2023 leaks and has been tightened with each subsequent vendor-side incident.
Meanwhile, every cloud incident-management vendor — incident.io, Rootly, FireHydrant, PagerDuty/Jeli, Datadog, Squadcast, Better Stack, Grafana OnCall, Atlassian Compass — shipped AI postmortem drafting in 2024–2026. All of it requires shipping incident data to the vendor’s cloud. None of it solves the buyer-cloud-AI-prohibited problem. The buyers themselves write postmortems by hand, late at night, after a 4-hour pager-driven incident, with only their willpower and a Confluence template between them and a half-finished doc that gets rubber-stamped.
IncidentScribe ships today on the Mac App Store. It runs Apple’s on-device Foundation Models. It has no telemetry, no cloud sync, no third-party SDKs, no remote logging. App Sandbox enforces every claim mechanically. Your incident data never leaves your Mac.
What it does
Drop in your incident artefact — a Slack export, a PagerDuty incident dump, a raw log file, or just a freeform paste. IncidentScribe extracts a structured timeline of events, then drafts a five-section postmortem from that timeline: Summary, Timeline, Root Cause, Contributing Factors, Action Items. Every drafted claim cites the events that justify it; every event cites its source line. Two clicks from any claim back to the original log line.
The trust UI
Click any drafted claim → the cited timeline events highlight. Click any event → the source slice highlights with the actor’s name underlined. The same trust chain shows up on export: Markdown uses footnote-style citations that link to a per-event definitions block; PDF renders the same; a “minimal” toggle strips the citations for clean Confluence/Notion paste when you don’t want footnote markers in the rendered output.
What we cut
Cloud incident-management vendors do a lot. IncidentScribe doesn’t. There’s no on-call rotation, no paging integration, no status-page bridge, no team workspace, no “AI assistant” chat surface, no Slack bot. v1.0 does one thing: turn incident artefacts into a structured-and-cited postmortem you sign off and export. That’s the whole product. If you need on-call rotation, run it in PagerDuty. If you need a status page, run it in Statuspage. IncidentScribe slots in at the postmortem step, not before.
The Pro tier
Two tiers, both StoreKit 2 subscriptions on the Mac App Store. Individual at $19/mo or $190/yr. Pro at $49/mo or $490/yr. Yearly plans include a 14-day free trial via the App Store’s introductory offer.
Pro adds two opt-in features. First, BYO cloud key — route the drafter through Anthropic, OpenAI, or Gemini using your own API key (Keychain-stored, master compliance lock defaults to OFF). Useful when your organisation is OK with cloud LLMs but you want IncidentScribe’s structured pipeline + citation chain on top. Second, template customisation — edit the per-section drafter prompts to match your team’s postmortem voice and conventions.
Both are off by default. Most users will never enable either. The on-device pipeline is the product; Pro is the escape hatch for teams whose constraints are different.
Where to get it
Two-week free trial on the yearly plans. Cancel in System Settings → Apple Account → Subscriptions if it’s not for you. No newsletter, no drip campaign — the only thing on the marketing-site mailing list is the v1.0 launch announcement (which is this post).
If you ship IncidentScribe in production at a regulated buyer, we’d love to hear about it — hello@incidentscribe.app. No customer logos, no testimonials — just real-incident feedback to make v1.1 sharper.