An org-wide DORA dashboard hides the thing you need. One team deploying twelve times a day averages away another shipping monthly and breaking production. ArcRelease decomposes the four keys by service and by team, computed from the events it already correlates.
Release risk analytics are the DORA four keys — deployment frequency, lead time, change failure rate and time to restore — derived from real deployment and incident events rather than a form somebody fills in, and broken out by service and by team so the outlier does not get averaged away.
The org average looks fine while one payments service quietly carries all the risk.
Change failure rate is a checkbox somebody ticks after the incident review — it measures diligence, not failure.
By the time the metric reaches my board pack it describes a quarter I can no longer change.
Every figure is computed from real events and drills through to the records behind it, because a number you cannot open is a number you cannot use in a QBR.
Deployments from CI and source control, incidents from PagerDuty and Datadog.
Incidents are matched to the deploys in their blast radius; confirmed correlations set change failure rate.
The four keys are broken out by service and by team, with linkage coverage shown for each number.
Every tile opens onto the underlying deployments and incidents, so a number survives the question "where did that come from".
Metrics resolve to services and releases, not individuals. There is no per-developer leaderboard.
They follow the DORA definitions, with the honest caveat that lead time and change failure rate depend on how cleanly work links to deploys. ArcRelease shows the linkage coverage behind each number so you know how much to trust it.
Not by design. Metrics resolve to services and releases, and there is no per-developer leaderboard. Using delivery metrics as a performance ranking produces gamed numbers, so the product deliberately does not make that easy.
No, and ArcRelease keeps them on separate charts. Time to restore is MTTR — diagnosis plus fix plus deploy plus verification. Time to a candidate root cause is how fast you learn what changed.
Tell us about your release process. Connect your stack in ten minutes, run a Gaja preflight on a real release, and see the reasons behind the verdict.
Free plan · ten minute setup · we reply in one to two business days