Apps & Software
What Is Deployment Frequency?
Deployment frequency is how often a team successfully releases changes to production. Here is the DORA definition, how to measure it, and how to read it without turning it into a target.
SEO and Content Specialist
3 min read
Short answer: deployment frequency is how often a team successfully releases changes to production. DORA defines it as the number of deployments over a given period, or the time between deployments. It is a throughput metric, so read it together with the stability metrics and measure it per application, not as a number imposed on every team.
“How often is this application released?” is a question that comes up when a company evaluates an application vendor or its own development team. What is deployment frequency, and which number is worth recording? This article answers briefly. An overview of all the DORA metrics is in Four DORA Metrics, and the automated pipelines that usually make releases more frequent are covered in What Is CI/CD.
What is deployment frequency and what does it count?
According to the DORA guide, deployment frequency is “the number of deployments over a given period or the time between deployments.” The Four Keys project from the DORA team words it more practically: how frequently a team successfully releases to production, for example daily, weekly, monthly, or yearly.
Two key words in that definition decide how to count:
- Production. What counts is a release to the environment real users work in. Deployments to a test environment do not count.
- Successfully. A release that is rolled back right away because it failed does not add to the number. Failed releases are recorded in other metrics.
DORA classifies deployment frequency as a throughput metric, alongside change lead time and failed deployment recovery time. The stability side is represented by change fail rate and deployment rework rate.
How often is considered good?
DORA gives no numeric thresholds in its guide. The Four Keys repository provides color bands for its dashboard, described as roughly following the ranges of the 2019 State of DevOps report:
| Band | Release frequency to production |
|---|---|
| Purple | On demand (multiple times per day) |
| Green | Daily to weekly |
| Yellow | Monthly |
| Red | Between once a month and once every six months |
Treat this table as orientation, not a standard. An application that rarely changes is not automatically a problem because it is rarely released.
How to measure deployment frequency in your company
- Pick one application or service. DORA recommends applying the metrics per application, not blended across the whole organization.
- Define what counts as a deployment: a successful release to production.
- Take the dates from records you already have, such as pipeline history or deployment logs.
- Count them per week or per month.
- Record it as a baseline, then compare against yourself over time.
DORA suggests starting with a conversation about friction points in the release process and with the DORA Quick Check, before building data integrations.
Common misreadings
- Making it a target. DORA warns that mandating a specific number of releases pushes teams to game the metric. Splitting releases into small pieces just to raise the count fixes nothing.
- Comparing across teams. The goal is to improve that team’s own performance, not to compete with other teams or companies.
- Reading it alone. If releases become more frequent but the change fail rate rises too, speed is being bought with stability.
How Legia uses it
In the DevOps & CI/CD service, Legia measures four numbers before and after the work: release frequency, time from finished code to running on the server, recovery time after a problematic release, and release failure rate. If your application rarely changes, Legia will tell you that an automated pipeline is probably not yet worth it. Other services in this pillar are on the Applications & Software page.


