Docs that run
Each step is executable, with a check before and after.
01Runbooks that execute
Turn the incident doc into a checked, replayable script that pages with a plan.
Nokonomicon is the boring, load-bearing part of runbooks that execute. Built by a small team, shipped weekly.
Overview
Runs
Policies
Traces
Settings
Runbookslive
11 mindatabase failover at 3 AM
0steps skipped under pressure
Docs that runok
Time-boxed stepsok
Post-incident proofok
Teams shipping with Nokonomicon
NorthwindKestrelRuangPolarTokoLumenBakauVela
Inside the product
One screen, the whole picture.
Overview
Runs
Policies
Traces
Settings
Runbookslive
11 mindatabase failover at 3 AM
0steps skipped under pressure
Docs that runok
Time-boxed stepsok
Post-incident proofok
What you get
Three things Nokonomicon does properly.
Time-boxed steps
A step that hangs past its budget escalates instead of stalling the incident.
02Post-incident proof
The run leaves a transcript you can attach to the review.
03“At 3 AM nobody reads a wiki. They ran the runbook and it told them what to do next.”
Bagus N. — SRE, Berlin
11 mindatabase failover at 3 AM
0steps skipped under pressure
1transcript per incident
Questions
The things people ask first.
Is this a workflow engine?+
It is a document that executes, with a human able to stop at any step.
Can steps require approval?+
Yes, and the approval is recorded with the transcript.
What if a step fails?+
It branches to the documented fallback instead of aborting the incident.
Pricing
Start free. Pay when it earns it.
Nokonomicon is open for design partners.
Small team, direct access to the people who build it. Bring a real workload.
Request access