firedrill · in private beta
Scheduled failure drills, with a dated record of what survived
In brief
Turns resilience from a claim into a measurement. Drills run on a schedule against a bounded target and each is scored, so “what happens when this fails” has a dated answer before an incident asks the question.
Failure drills on a schedule against a namespace or a compose stack: pods killed, disks filled, DNS withheld, certificates expired, each scored as survived, degraded or failed with the time to first impact. Every run leaves a dated record beside Lastresort's restore log.
What it does
- Checks adopted from a catalogue per plan and pinned by version, so the score compares run to run
- Each check carries a declared blast radius and a stop condition
- The dated record is what resilience-testing obligations ask a supplier to show
A closer look
Select any screenshot to enlarge it.
The Firedrill site
The Firedrill site, further down
The Firedrill demo, signed in as its read-only viewer
The whitepapers
firedrill has no paper of its own yet; the catalogue has the thinking the lab's tools share.