The postmortem drafter for SREs who can’t paste into ChatGPT.
Apple Intelligence, on-device, timeline-first. macOS only.
Open in Mac App Store See pricing
14-day free trial on yearly plans. Requires macOS 26 or later, Apple Silicon, and Apple Intelligence enabled.
How it works
-
Drop in your incident artefacts
Paste a Slack export, a PagerDuty incident dump, or a raw log file. Multi-thousand lines is fine.
-
On-device extraction
IncidentScribe extracts a structured timeline of events from your raw input. Every event is verified against the source text before it lands in the timeline — fabricated participants and timestamps are dropped before you ever see them.
-
Five-section postmortem draft
Summary, Timeline, Root Cause, Contributing Factors, Action Items. Drafted from the structured timeline, not the raw text. Every claim cites the timeline events that support it; every event cites its source slice. Two clicks back to the original log line.
-
Edit, sign off, export
Markdown or PDF, to a destination you choose. Nothing leaves your Mac — the Mac App Store sandbox is the verifier.
See it in action
Five screens from the canonical workflow. Click any image to see it full-size.
Available now on the Mac App Store. Requires macOS 26 or later, Apple Silicon, and Apple Intelligence enabled.
Why on-device
Every cloud incident-management vendor shipped AI postmortem drafting in 2024–2026 — incident.io, Rootly, FireHydrant, PagerDuty/Jeli, Datadog, Squadcast, Better Stack, Grafana OnCall, Atlassian Compass. All require shipping incident data to the vendor’s cloud.
Some buyers can’t do that. Wells Fargo, Bank of America, Citi, Goldman, JPMorgan, Samsung post-2023, Apple internal, healthcare under HIPAA posture, defence, pharma. Standing enterprise ChatGPT bans haven’t softened — the 2025 ChatGPT share-indexing incident, the November 2025 OpenAI/Mixpanel breach, and the September 2025 Anthropic three-issues postmortem all hardened them further.
IncidentScribe is a Mac-native postmortem drafter built for the regulated-buyer market. It runs Apple’s on-device Foundation Models with no telemetry, no cloud sync, no third-party SDKs, no remote logging. App Sandbox enforces every claim mechanically.
Built for SREs by SREs
IncidentScribe is built by a team that’s been on call. Every design choice serves the operator who’s writing a postmortem at 2 a.m. on a Tuesday, with their security team’s policies hanging over their shoulder.
The product is Mac-native, indie, and shipped through the Mac App Store. No team tier, no enterprise tier. If your stack is small enough to fit on one operator’s Mac, IncidentScribe is built for you.
Built for your constraints
IncidentScribe is built for operators the cloud incident-AI wave left behind. If your security team won’t let incident data leave the building, start here:
- For banks & financial services — postmortems without sending incident data to a vendor cloud.
- For healthcare & HIPAA posture — PHI-adjacent incident data never leaves the Mac.
- For defence & aerospace — an air-gap-friendly shape; no external egress.
- For SRE & on-call teams — a messy channel in, a cited postmortem out.
How it’s built
- Citation chains — every drafted claim two clicks from its source line.
- Timeline extraction — schema-constrained, validated, deduplicated.
- On-device privacy — enforced by the App Sandbox, not promised.
- Apple Foundation Models — a real shipping app on Apple Intelligence.
Weighing it up? See vs. cloud incident tools, vs. ChatGPT, and vs. writing by hand — or the FAQ.
Ready when you are
IncidentScribe v1.0 is live on the Mac App Store. Yearly plans include a 14-day free trial.