Skip to main content
DORA (DevOps Research and Assessment) defines four widely-used measures of software delivery performance. DevPerform computes all four from your ingested data and shows them at the top of the Delivery & Quality page (“DORA — the four keys”) with Elite / High / Medium / Low bands — the same page also covers cycle-time phases, CI/CD health, flaky tests, code rework, and issue-tracker planning.

​
The four keys

​
Deploy signal: merges vs. actions

Deployment Frequency and Lead Time depend on knowing when you ship. DevPerform supports two modes, set per org in Admin → Org Settings:
Every merged pull request counts as a deploy. Lead time is measured PR open → merge. This works with zero CI configuration.

​
Where failures come from

Change Failure Rate and Time to Restore need incident data. DevPerform treats issues carrying your org’s incident label as incidents (GitHub/GitLab labels; Bitbucket matches on title) — no separate incident tool required. Set the label in Org Settings. CFR is incidents ÷ deploys over the window; Time to Restore is the median open→close time of those issues.

​
Bands

Each key is labeled Elite, High, Medium, or Low against published DORA thresholds, so you can see at a glance where a team sits without memorizing target numbers. Bands are reference points for improvement, not grades.
DORA is part of the Growth plan and up. See Plans.