Runbook Generator
Generate step-by-step runbooks and IT procedures for deployments, incidents, and maintenance.
This is an AI tool. The text you enter is sent to our AI service to generate your result. Our own server doesn't store it or use it for training; if it's down, a backup AI provider may handle it. How we handle your input
How to Use Runbook Generator
- 1Describe the procedure — what it does, when it runs, and the steps as you currently understand them.
- 2Pick the runbook type: Deployment / Release, Incident Response, Backup & Recovery, System Onboarding, Scheduled Maintenance, or Failover / DR.
- 3Name the system — 'Kubernetes / EKS', for example.
- 4Choose the audience: Engineer (Technical), Non-Technical Operator, or On-Call (Fast Reference). On-call gets a terser document built for 3am.
- 5Generate, then replace the placeholder commands with the real ones and run through it once on a non-production system before anyone relies on it.
Frequently Asked Questions
Does it include rollback steps?
Yes — rollback steps with a verification step at the end, plus explicit 'when to abort' criteria and post-procedure checks. Those are the sections most hand-written runbooks are missing, and the ones you need when the procedure goes wrong at 3am.
What does the On-Call audience setting do?
It produces a fast-reference version: shorter, more scannable, assuming the reader is tired and under pressure. A full engineering runbook is the wrong document to read during an incident, which is why the option exists.
Are the commands real?
No — treat every command as a placeholder. The tool does not know your cluster names, your IAM roles, or which flags your version of a tool takes. The structure is the deliverable; the commands are yours to fill in and test.
Should I test the runbook before relying on it?
Always, and preferably by having someone who did not write it follow it on a non-production system. An untested runbook is a document that describes what you believe the procedure is, which is not the same as what it is.
What are the prerequisites sections for?
Required access, permissions and tools are listed up front, because the most common runbook failure is getting four steps in and discovering you do not have the role needed for step five. Filling those in accurately is the highest-value edit you can make.
About Runbook Generator
A good runbook is one someone who did not write it can follow under pressure. The Runbook Generator produces the full structure — purpose, scope, when to use it, required access and tools, numbered steps, post-procedure checks, success criteria, abort conditions and rollback — for six common procedure types.
The audience setting is genuinely useful. The same failover procedure written for an engineer, for a non-technical operator, and as an on-call fast reference are three different documents, and most teams only ever write the first one. The on-call version is the one that gets used when it matters.
Four sections carry most of the value and are the ones hand-written runbooks skip: required access and permissions up front, post-procedure verification, explicit abort criteria, and rollback steps ending in a check that the rollback worked. Getting those right matters more than the prose.
Every command in the output is a placeholder. Replace them with your real ones, then have someone else follow the runbook end to end on a non-production system — an untested runbook describes what you think the procedure is. Keep credentials and sensitive internal addressing out of the input. Your text goes to our own AI server over HTTPS, is used once, and is never stored or used for training. If our server is down, a backup AI provider may handle the request under its own data policy.