Runwhen
Digital assistant platform for SREs that automatically runs troubleshooting tasks and playbooks across Kubernetes and cloud.
Our Verdict
Useful SRE automation concept, but ROI hinges on how much runbook work you're willing to codify.
Pros
- Automates SRE troubleshooting playbooks
- Chat-driven diagnostics across Kubernetes and cloud
- Reduces MTTR for common recurring issues
- Codifies tribal knowledge into runbooks
Cons
- Requires investment to build playbook library
- Early-stage with limited public references
- Overlaps with Rootly and Shoreline.io
- Impact depends on existing runbook quality
Best for: SRE teams with recurring incident patterns wanting to automate diagnostics.
Not for: Small teams without existing runbooks or standardized troubleshooting.
When to Use Runwhen
Good fit if you need
- Automated Kubernetes troubleshooting playbook execution
- SRE digital assistant running diagnostic commands
- Codified runbooks triggered by alert conditions
- Cloud resource remediation without manual SSH access
Lock-in Assessment
Medium 3/5
Lock-in Score 3/5
Pricing
Price wrong?Runwhen Pricing
- Pricing Model
- freemium
- Free Tier
- Yes
- Entry Price
- —
- Enterprise Available
- No
- Transparency Score
- —
Beta — estimates may differ from actual pricing
1,000
1001K10K100K1M
Estimated Monthly Cost
$25
Estimated Annual Cost
$300
Estimates are approximate and may not reflect current pricing. Always check the official pricing page.
Project Health
C
Health Score
25 12
Bus Factor
4
Last Commit
today
Release Freq
7d
Open Issues
21
Issue Response
N/A
License
Apache-2.0
Last checked: 2026-04-21
Community Discussion
Comments powered by Giscus (GitHub Discussions). You need a GitHub account to comment.