档案库 · 开发与企业工具 · 产品决策 · 2023–2024
Doctor Droid：YC W23转型后，押注值班手册变成可执行笔记本
Doctor Droid从YC W23数据湖仓转型至PlayBooks：可执行笔记本式手册，连接可观测性工具；Show HN 147点，2024-06-04
Doctor Droid
做的是什么生意
Doctor Droid's PlayBooks is an open-source, Docker-deployable runbook automation platform: notebook-style documents whose steps fetch logs and metrics from 15+ types of observability tools, query databases, run remote bash commands or call APIs, so on-call engineers investigate from one page instead of hopping across tools
起因
Dipesh and Siddarth met at an Indian food-delivery startup with a busy on-call rotation and a small tech team; business-impacting issues such as orders dropping over 5% in 15 minutes escalated to Dipesh as the long-tenured lead dev. They joined YC's W23 batch building a data lakehouse with support for dynamic log schemas, concluded it was a product in search of a market, stopped, and returned to PlayBooks, an idea they had prototyped before YC but never executed on
经过
The 2024-06-04 Show HN launch offered a sandbox with sample playbooks and described integrations for remote bash, AWS CloudWatch and Azure Log Analytics logs, PromQL/CloudWatch/Datadog/New Relic metrics, PostgreSQL/ClickHouse/JDBC queries, custom API calls, EKS/GKE events and iFrames, with goals of automated runs, shareable investigation state and no-laptop operation. The founders said a fully functional Slack workflow was a dealbreaker for the MVP and that they were piloting with a large enterprise whose 100+ SREs had tried Jupyter notebooks and ended up writing an internal SDK to make them self-serve; commenters pointed to competitors such as Rundeck, Fiberplane, moment.dev, Nurtch, Pryrite, Speedrun and Livebook and warned that getting devops engineers to leave existing workflows is the hard part
结果
Still live as of 2026-09-04: the open-source repo displayed 460 stars, 33 forks and 2,960 commits, with docs, a public sandbox, a demo-alerts Slack workspace and a YouTube channel all active; no funding or revenue figures appear in the record
背景
Dipesh和Siddarth来自一家印度食品配送初创公司，那里值班轮换繁忙且技术团队小；业务影响问题（如订单15分钟内下降超5%）会升级给老资格的负责人Dipesh。为免成瓶颈，他预写脚本在高峰时段每五分钟获取自定义指标和订单日志，以便工程师在深入泛泛探索前基于新鲜输出检查常见嫌疑。
他们参加YC W23批次构建支持动态日志模式的湖仓，意识到这是个找不到市场的产品，叫停并转向PlayBooks——一个早在YC前就原型过的可执行笔记本点子。PlayBooks把手册变成连接技术栈每个部分的笔记本式文档：获取的日志来自Amazon CloudWatch或Azure Log Analytics，拉取的指标来自PromQL、Datadog、New Relic，查询PostgreSQL或ClickHouse，运行远程bash，调用自定义API，或检查EKS/GKE事件；每一步的输出都显示在指令旁。
赌注是值班调查可以被脚本化和自动化，使警报在人醒着之前就触发常见嫌疑检查，结果在团队中共享。2024-06-04的Show HN得到147点和35条评论；创始人称正与一家大型企业试点，对方100多名SRE曾费力让Jupyter笔记本能为产品团队自助；评论者则质疑团队是否会采纳Jupyter风格工作流。到2026-09-04抓取时，仓库显示460颗星、33个复刻和2,960次提交，文档、沙盒和演示警报仍活跃。
这件事要成立，得有什么
- 在命名平台上有可追溯的势头：2024-06-04的Show HN得到147点和35条评论，创始人实时回答线程中的架构、Slack和采用问题。
- 干净的转型弧线：YC W23的数据湖仓被承认找不到市场，果断叫停，取而代之的是创始人早在YC前已原型化的PlayBooks。
- 具体的创始人起源赌注：PlayBooks将Dipesh在食品配送值班轮换中五年一遇的的指标和日志脚本泛化为适合任何SRE团队的产品。
- 可验证的轨迹：2026-09-04抓取时，GitHub仓库显示460颗星、33个复刻和2,960次提交，文档和沙盒仍然活跃。
可借鉴之处
让第二个赌注植根于自己的运营痛点：PlayBooks在YC前就原型化了，因此当W23湖仓未能找到市场时，创始人们推出的是他们早先亲历值班所积累的东西。
后续进展
截至2026-09-04，Doctor Droid的PlayBooks仍然活跃：仓库显示460颗星、33个复刻和2,960次提交，文档、公开沙盒、演示警报Slack工作区和YouTube频道均活跃。README将Doctor Droid定位为面向SRE和值班团队的手册自动化平台，可用Docker部署；路线图项目包括步骤间规则、警报触发手册、AI解释层和事后剖析执行日志。记录中未显示资金、收入或客户数量，也未说明企业试点是否转化。
资料来源
- Show HN: PlayBooks – Jupyter Notebooks style on-call investigation documents (147 points, 35 comments)
- DrDroidLab/PlayBooks — Runbook automation platform for SRE & on-call teams (460 stars)
发现哪里写错了？告诉我们。
轮到你了
你刚读完一家。说说你在做什么，看看谁在赌同一件事。
免费账号 · 3 次免费提问 · 不用绑卡