The RunWhen Authors Community: Royalties For Runbooks
summary
RunWhen builds a massive library of templated steps for troubleshooting, starting with the Kubernetes ecosystem and top Helm charts, and claims to inherit thousands of automated steps so AI can search and stitch millions of runbooks. Authors submit repositories, get code reviewed and tested in company-provided sandboxes, and receive royalties and bounties (example: paid work to update GitLab 3.8→3.9 scripts). Tasks execute in hermetic containers inside customer infra, return only structured metadata, and current scale: 4 active contributors, ~36 queued, aiming to cover ~600 charts.
AI-written summary · about
chapters (9)
- 0:00Introduction and background
- 2:31Runbooks and observability challenges
- 5:57RunWhen’s author program
- 9:29Questions about the author program
- 10:33How troubleshooting steps work
- 13:00Author tools and community support
- 17:12AI-driven automation and next steps
- 22:13AI-assisted troubleshooting script generation
- 23:39Q&A session
related talks
22mThe RunWhen Authors Community: Royalties For Runbooks
28mDo you Know a Runbook From a Flip Book?...
35mOpen-source releases: Everything we've learnt in 4 years
24mAutomate your CloudOps and Spend Less Time Doing Operations
13mOpen Source Opening Doors - Michelle Noorali, Sr. Software Engineer, Microsoft (Part 1)
33mBlueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform
22mCreating a Micro Open-Source Community with Helm
29mOpen-Source Framework for AI-Powered CI/CD Pipelines