I got tired of writing runbooks after incidents. So I'm building something.

posted Originally published at dev.to 1 min read

Working on a microservices-based platform, I kept running into the same frustrating cycle:
Something breaks → we figure out the fix in real time → someone says "we should document this" → nobody does → same thing breaks 3 months later.
Even when runbooks existed, they were either too generic ("restart the pod") or specific to whoever wrote them and completely useless to the next on-call person.
So I'm building RunbookAI — you describe your stack once (AKS, EKS, Node.js, PostgreSQL, whatever) and it generates incident playbooks grounded in SRE best practices. Stack-aware, not copy-pasted templates.
Very early stage — just launched a waitlist today.
My question to the Dev.to community: What's the worst runbook experience you've had? Either nonexistent, outdated, or just completely wrong? Would love to understand the real pain before I build the wrong thing.
Waitlist: runbookai.in

1 Comment

1 vote

More Posts

I’m a Senior Dev and I’ve Forgotten How to Think Without a Prompt

Karol Modelskiverified - Mar 19

TypeScript Complexity Has Finally Reached the Point of Total Absurdity

Karol Modelskiverified - Apr 23

I Wrote a Script to Fix Audible's Unreadable PDF Filenames

snapsynapseverified - Apr 20

What Is an Availability Zone Explained Simply

Ijay - Feb 12

Why most people quit AWS

Ijay - Feb 3
chevron_left

Related Jobs

View all jobs →

Commenters (This Week)

3 comments
1 comment
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!