Alert When Incident Runbooks Go Stale
Automatically track when your incident response playbooks were last updated and tested. Get Slack or email alerts before a stale runbook costs you during an outage.
Start for $29 / moNo credit card required for 14-day trial. Cancel anytime.
Freshness Scores
Every runbook gets a freshness score based on last-updated and last-tested dates.
Slack & Email Alerts
Get notified the moment a runbook crosses your staleness threshold.
GitHub & GitLab
Connect your repos in seconds. We watch commits and PR activity automatically.
Simple Pricing
Pro
$29
per month
- ✓ Unlimited runbooks & repos
- ✓ Slack + email alerts
- ✓ Custom staleness thresholds
- ✓ Freshness dashboard
- ✓ GitHub & GitLab integration
- ✓ 14-day free trial
FAQ
How does runbook freshness tracking work?
We connect to your GitHub or GitLab repositories and monitor commit history, PR activity, and optional test-date annotations in your runbook files. Each runbook receives a freshness score that decays over time.
What counts as a runbook becoming stale?
You define the threshold — for example, 30, 60, or 90 days without an update or test. When a runbook crosses that threshold, we immediately send an alert to your configured Slack channel or email.
Can I cancel my subscription at any time?
Yes. Cancel anytime from your billing portal with no questions asked. Your access continues until the end of the billing period.