DORA Metrics Calculator
Calculate your DORA metrics performance tier. Input your deployment frequency, lead time, MTTR, and change failure rate to see how you compare to elite teams.
DORA metrics are four measures of software delivery performance - deployment frequency, lead time for changes, mean time to recovery, and change failure rate - drawn from Google's DevOps Research and Assessment program. Together they capture both how fast a team ships and how stable that shipping is.
This calculator is for engineering leaders and team leads who want a quick read on where their delivery sits against industry tiers. Enter what you can measure and it returns a performance tier (Elite, High, Medium, or Low) for each metric plus an overall rating, with guidance on the weakest area to address first.
Enter Your Metrics
Enter at least one metric above to see your DORA performance tier.
Next Steps to Improve
- Establish a baseline. Measure your current DORA metrics over 30 days before making changes. You can't improve what you don't measure.
- Reduce batch size. Smaller PRs and more frequent deploys naturally improve both lead time and change failure rate. Aim for PRs under 200 lines.
- Automate your pipeline. Manual deployment steps are the #1 bottleneck for most teams. CI/CD automation directly improves deployment frequency.
- Invest in observability. You can't recover quickly from incidents you can't detect. Monitoring and alerting infrastructure is the foundation of low MTTR.
About DORA Metrics
DORA (DevOps Research and Assessment) metrics are the gold standard for measuring software delivery performance. Based on research by Google's DORA team across thousands of organizations, these four key metrics predict both organizational performance and team wellbeing.
How often you ship to production
Time from commit to production
How quickly you restore service
% of changes causing problems
How it’s calculated
The calculator scores each of the four DORA metrics against published research thresholds, then averages the available scores into an overall tier.
Inputs
You provide any combination of deployment frequency, lead time for changes, mean time to recovery, and change failure rate. Partial data is fine - the tool scores only the metrics you enter.
Thresholds
- Deployment frequency: Elite is multiple deploys per day, High is weekly to daily, Medium is monthly to weekly, Low is less than monthly.
- Lead time: Elite is under one day, High is one day to one week, Medium is one week to one month, Low is more than a month.
- Recovery time: Elite is under one hour, High is under one day, Medium is under one week, Low is more than a week.
- Change failure rate: Elite is 0 to 5 percent, High is 5 to 10 percent, Medium is 10 to 15 percent, Low is above 15 percent.
Overall tier
Each metric maps to a score (Elite 4, High 3, Medium 2, Low 1). The tool averages the scores of the metrics you entered and rounds to a band: 3.5 and up is Elite, 2.5 to 3.5 is High, 1.5 to 2.5 is Medium, below 1.5 is Low.
Data source
Pull the raw numbers from your own systems - deployment frequency and lead time from CI/CD logs and version control, recovery time and failure rate from your incident tooling. Use a 30 to 90 day window so the figures reflect a steady state rather than one unusual week.
Worked example
A platform team deploys five times per week, has a lead time of three days, recovers from incidents in about four hours, and sees an 8 percent change failure rate.
- Deployment frequency: five per week is roughly 0.71 per day, which lands in the High band.
- Lead time of three days is also High.
- Recovery in four hours is High.
- An 8 percent failure rate falls in the High band as well.
All four metrics score 3, so the average is 3.0 and the overall rating is High performer. The read: this team ships well and recovers quickly, but lead time is the softest number. Shrinking batch sizes and merging smaller PRs would move lead time toward the Elite threshold of under a day without putting stability at risk.
DORA Performance Benchmarks
| Metric | Elite | High | Medium | Low |
|---|---|---|---|---|
| Deployment Frequency | Multiple per day | Weekly to daily | Monthly to weekly | Less than monthly |
| Lead Time for Changes | Less than 1 hour | 1 day to 1 week | 1 week to 1 month | More than 1 month |
| Mean Time to Recovery | Less than 1 hour | Less than 1 day | Less than 1 week | More than 1 week |
| Change Failure Rate | 0-5% | 5-10% | 10-15% | More than 15% |
Source: Google DORA State of DevOps Report 2023 · Based on 32,000+ professionals across 7 years of research
Our Take
DORA metrics are signals, not goals. Microsoft abandoned DORA as a performance metric after teams started gaming the numbers.
The original research identified what elite teams do, not how they got there. Goodhart's Law applies: when a measure becomes a target, it ceases to be a good measure. Use these metrics to identify bottlenecks and track improvement - not to judge your team or chase arbitrary benchmarks.
"Elite performers deploy 973x more frequently than low performers, with 6,570x faster lead times and 3x lower change failure rates."
— Google DORA State of DevOps Report, 2023
Key terms
- Deployment Frequency
- How often a team releases code to production. Higher frequency usually reflects smaller, safer changes rather than speed for its own sake.
- Lead Time for Changes
- The elapsed time from a commit landing to that change running in production. It measures how quickly work moves through the delivery pipeline.
- Mean Time to Recovery (MTTR)
- The average time to restore service after a production incident or failed deployment. It reflects resilience, not how fast people type.
- Change Failure Rate
- The percentage of deployments that cause a failure in production requiring a fix, rollback, or patch.
- Performance Tier
- The Elite, High, Medium, or Low band a metric falls into, based on thresholds from the DORA State of DevOps research.
Frequently Asked Questions
DORA tiers (Elite, High, Medium, Low) are based on research by Google's DevOps Research and Assessment team, which studied over 32,000 organizations across seven years. The thresholds are: Elite teams deploy multiple times per day with lead times under 1 hour; High performers deploy weekly to daily; Medium teams deploy monthly to weekly; Low performers deploy less than monthly. These benchmarks come from the annual State of DevOps Report.
Want to track this automatically?
CodePulse connects to your GitHub and calculates these metrics in real-time. No more manual data entry or spreadsheets.
Free tier available. No credit card required.
See These Features in Action
Track all four DORA metrics and benchmark against industry standards.
Track deployment frequency, lead time, and release patterns.
Related Tools
Engineering Headcount ROI Calculator
Calculate the ROI of your engineering team. See the true cost per engineer and what productivity gains would mean for your bottom line.
Developer Productivity Score Calculator
Calculate your team's productivity score across three dimensions: Efficiency, Effectiveness, and Experience. Get personalized recommendations.
DPE Maturity Assessment
Assess your organization's Developer Productivity Engineering maturity level and get a roadmap to level up. Based on practices at Netflix, Meta, and Spotify.