Deployment Frequency
Deployment Frequency measures how often an organization successfully releases to production. It is one of the four DORA metrics defined by the DevOps Research and Assessment program, and is the primary indicator of an engineering team's delivery throughput.
Formula
Deployment Frequency = Total production deployments ÷ Time period Example: 42 production deployments in 30 days = 1.4 deployments per day For teams with multiple services, calculate per-service frequency and report both individual and aggregate rates. Elite performers deploy multiple times per day per service.
Industry Benchmarks
| Performance Level | Benchmark (deployments per day / week / month) |
|---|---|
| Elite | Multiple deploys per day |
| High | Between once per day and once per week |
| Medium | Between once per week and once per month |
| Low | Fewer than once per month |
Benchmarks from the 2023 State of DevOps Report (DORA). "Elite" and "High" performers ship significantly faster and have better stability outcomes than "Medium" and "Low" performers, disproving the speed-stability tradeoff assumption.
Data Sources
- GitHub Deployments API and GitHub Actions deployment workflows
- Vercel, Railway, Netlify, Render, Fly.io, and AWS CodeDeploy webhook events
- CI/CD pipeline completion events (GitHub Actions, CircleCI, Jenkins)
- Container orchestration events (Kubernetes rollouts via kubectl or ArgoCD)
Why Deployment Frequency matters
Higher deployment frequency is strongly correlated with better stability, not worse. Teams that deploy more frequently deploy smaller changes, which are easier to test, easier to revert, and less likely to cause incidents. Deployment frequency is also a leading indicator of organizational health: teams that can deploy on demand have solved the organizational, process, and technical problems that slow delivery. A low deployment frequency often signals undifferentiated work, large batch sizes, or manual handoffs that create risk.
Common measurement mistakes
Counting all environments instead of production only. Deployments to dev, staging, or QA do not count toward DORA deployment frequency. Only production (or production-equivalent) environments should be included.
Conflating deployment frequency with release frequency. A "release" may bundle multiple deployments; DORA measures individual deployment events, not release versions.
Measuring across teams without normalizing for team size. A team of 3 engineers deploying 10 times per week is performing at an elite level; comparing that raw number to a team of 50 engineers is misleading.
How Koalr measures Deployment Frequency
Koalr counts production deployment events from all connected deployment platforms (Vercel, Railway, Netlify, Fly.io, Render, AWS CodeDeploy) and GitHub Deployments. Each successful deployment to an environment tagged as "production" increments the counter. Koalr displays deployment frequency per service, per team, and organization-wide, with trend lines over 7, 14, 30, and 90-day windows. Failed deployments are excluded from frequency but tracked separately for change failure rate.
Related DORA metrics
See your Deployment Frequency in Koalr
Connect GitHub and your deployment platform to start tracking all four DORA metrics automatically. No manual data entry, no spreadsheets.