Collect context
Bring alerts, telemetry, deploys, configuration changes, service ownership, and code references into one investigation view.
Daran Docs
Daran starts as an autonomous incident operator, then becomes the intelligence and action layer between production signals and operational decisions.
What Daran Does
Section titled “What Daran Does”Daran turns reliability signals into evidence-backed Incident Handoffs and, when an application-side fix is safe to prepare, opens a GitHub PR with the supporting context. When an alert, error spike, trace anomaly, deploy, configuration change, or code change matters, Daran gathers the surrounding operational context and organizes the evidence into a reviewable artifact.
The goal is to shorten the first investigation and repair loop: what happened, which services are affected, what changed recently, which hypotheses are plausible, what evidence supports or weakens them, what should be checked next, and whether Daran created a branch and PR for an application-side fix.
Preserve evidence
Keep links back to sources, capture times, confidence, and raw references so operators can inspect the basis for every claim.
Generate hypotheses
Identify likely causes and keep them tied to supporting evidence, uncertainty, and disconfirming signals.
Hand off clearly
Produce an Incident Handoff that a responder or coding agent can use to continue the investigation without starting from scratch.
Open reviewable PRs
For scoped application repositories, create a branch and GitHub PR with changed files, validation results, evidence links, and revert guidance.
What Daran Is Not
Section titled “What Daran Is Not”Daran is not a replacement for your incident management system of record. The first release is not focused on on-call scheduling, status pages, incident room management, postmortem management, or unapproved production operations.
Those tools coordinate the response. Daran investigates the system, prepares the handoff, and opens reviewable PRs when the fix belongs in application code.