Blog/Private AI for incident postmortem drafting
Engineering

Private AI for incident postmortem drafting

By Samuel Seidel · Updated September 9, 2026

A drafting model on a dedicated machine turns a raw timeline of logs and chat messages into a structured postmortem without sending it to an AI vendor. That saves on-call engineers time they rarely have after an incident closes. It also matters what the draft is built from: system architecture, internal hostnames and exact failure conditions, close to a map of how to break the system again.

What a postmortem draft contains

A thorough incident writeup includes the sequence of events with timestamps, relevant log excerpts and stack traces, which services were affected and how they're connected, what the on-call engineer tried before the fix worked, and often a section on what made detection slow. Together, that's a detailed description of the architecture and its weak points, written by the people who know where they are. Companies don't publish it, or publish only a heavily redacted version.

Pasting that raw material into a general-purpose AI tool to get help with the writeup sends architecture detail, service names, and sometimes accidentally-included secrets or tokens from log output to the AI vendor. Usually nothing comes of it, but the exposure is there every time, and it grows with each incident the team writes up the same way.

What changes when the drafting model is self-hosted

On a dedicated DGX Spark, the whole loop (logs in, structured draft out) runs on your own model on a machine assigned only to your team, not an AI vendor's API, so no vendor retention or training policy applies. That matters more for incident data than most documents, because a postmortem records where and how a system failed. The Spark is a GPUwerk-run machine (its own in Czechia, or a partner's in the country the console shows), operated under its published DPA: scrub secrets from the logs before pasting, as you would anywhere.

A practical setup runs Open WebUI with the team's postmortem template loaded as a system prompt, so drafts come back in the right format (timeline, impact, root cause, remediation items) without re-explaining the structure each time. Teams that index past incidents, as in on-premise RAG, can have the model check a new draft against prior incidents for a recurring root cause.

What the model is good at, and what it isn't

Turning a scattered timeline into readable prose, checking that a draft covers every section a team's template requires, and suggesting a first-pass list of follow-up action items from the narrative are all things a drafting model does well. Determining the actual root cause is not something to hand off. That requires someone who understands the system, and a model asked to guess at causation from partial logs will produce a plausible-sounding explanation whether or not it's correct. Every root cause in the final document should trace back to something a human engineer verified.

What this doesn't solve

A dedicated drafting model doesn't fix logging hygiene: secrets shouldn't end up in log output wherever the postmortem is written. It doesn't replace an incident review meeting, and it doesn't decide which parts of the writeup are safe to share externally if the company publishes a public version. What it removes is one exposure: architecture and failure detail sitting in an AI vendor's logs because that's the tool an engineer reached for out of habit. See pricing for what a dedicated instance costs for an engineering team.

Related pages

First top-up: pay $20, get $30 in credit

Draft postmortems without an AI vendor in the loop.

A dedicated Spark for engineering, starting at $0.79/hour, deployed in minutes from EU-Central. Read the Open WebUI setup →

Your data stays on a machine assigned only to you. GPUwerk processes it under its published DPA.

Create account See private LLM hosting