Congratulations! The difference between pure agentic exploration and deterministic steps is spot on. Runbooks give ops more confidence on the data exploration and save time/context.
Curious how much savings do you observe from using runbook versus purely let Claude do the planning at first. Also how the runbooks can self heal if results from some steps in the middle are not expected.
Congrats on the Relvy launch and YC! Automating on-call runbooks is a massive pain point. Have you considered how generative AI might further enhance the diagnostic or remediation steps, perhaps by suggesting solutions based on past incidents?
How does this differ from cursor cloud agents where I can hook up MCPs, etc and even launch the agent in my own cloud to connect directly to internal hosts like dbs?
This is a great tool for enterprises specifically the customer support teams that can quickly triage the customer escalations and take the first stab at the issues without escalating to internal teams. All the best guys!! Rooting for you!
Interesting! tbh, we don't have any runbooks and pretty minimal telemetry set up (we're a very small team :), do you have any recommendations on which telemetry service to use to get started? right now, our services run on a combination GCP Cloud Run + Vercel
Amazing product guys! I tried it on a few of my issues and it was pretty spot on in finding the root cause. Loved it!
Are you planning to support auto PRs for fixes? Would be a cool addition
Interesting!
In my experience using custom harnesses has worked better eg: Stripe etc all did it custom largely because of the sensitive integrations. How would you handle that?
25 comments
Curious how much savings do you observe from using runbook versus purely let Claude do the planning at first. Also how the runbooks can self heal if results from some steps in the middle are not expected.