RunBookKit About

About

What RunBookKit is for, what it is not, and how it fits the .tools suite.

Purpose

Enable organizations to respond to incidents calmly, consistently, and repeatably under pressure.

Core problem
  • Missing structure
  • Unclear ownership
  • Fragmented documentation
  • Cognitive overload under stress
What RunBookKit is for
  • Incident runbooks (response, escalation, recovery)
  • Vendor onboarding and dependency context (incident-relevant)
  • Incident timelines
  • Blameless postmortems
  • Release and change readiness checks
  • Exportable, audit-ready artifacts
What RunBookKit is not
  • Not an alerting system
  • Not a ticketing system
  • Not a monitoring platform
  • Not an AI decision-maker
Operating rules
  • No accounts. No login.
  • No storage. Inputs stay in your browser.
  • Stable URLs. Paths do not change.
  • Deterministic outputs. Same inputs produce the same artifacts.
  • Exports. Print/PDF, Markdown, JSON (CSV where applicable).
Related tools

RunBookKit owns response and recovery. NetReady owns connectivity preparedness. ReadyCheck owns readiness validation.