Canonical: https://weaveos.com/glossary/deployment-frequency

[Home](https://weaveos.com/)/[Glossary](https://weaveos.com/glossary)/[DORA and DevOps](https://weaveos.com/glossary/category/dora-devops)/Deployment frequency

[DORA and DevOps](https://weaveos.com/glossary/category/dora-devops)

# Deployment frequency

By WeavePublished September 10, 20262 min read

## Definition

Deployment frequency describes how often a service or application is deployed to production. It can be expressed as deployments per period or as the time between deployments, using a consistent definition of a deployment.

On this page

1. [Definition](https://weaveos.com/glossary/deployment-frequency#definition)
2. [Decide which events count](https://weaveos.com/glossary/deployment-frequency#article-decide-which-events-count)
3. [An illustrative calculation](https://weaveos.com/glossary/deployment-frequency#article-an-illustrative-calculation)
4. [Interpret frequency with other evidence](https://weaveos.com/glossary/deployment-frequency#article-interpret-frequency-with-other-evidence)
5. [How this relates to Weave](https://weaveos.com/glossary/deployment-frequency#weave)
6. [Sources](https://weaveos.com/glossary/deployment-frequency#sources)
7. [Related terms](https://weaveos.com/glossary/deployment-frequency#related)

## Decide which events count

A deployment moves a version into a production environment. That is not always the same event as exposing a feature to users. A team can deploy code behind a flag and release the feature later.

Pipeline runs, deployment attempts, and completed deployments may also differ. If a pipeline retries after a temporary failure, agree on whether the records describe one intended deployment or several separate events. Keep the rule stable across reporting periods.

## An illustrative calculation

Suppose one service completes 24 production deployments during a 12-day observation period. Its frequency over that period is two deployments per day.

That average does not mean it deployed twice on each day. All 24 deployments could have occurred during a small number of busy days. The underlying timeline helps distinguish a steady release practice from bursts around deadlines.

## Interpret frequency with other evidence

More frequent deployments can accompany smaller changes, but a count does not reveal their size or usefulness. A series of urgent patches also increases deployment activity.

Inspect [change failure rate](https://weaveos.com/glossary/change-failure-rate), the nature of the releases, and the time changes spend waiting. Compare the same service with its own relevant history. Summing every microservice's deployments and comparing the total with a single mobile application's release count creates a misleading impression of relative performance.

## How this relates to Weave

Weave's delivery benchmarks can help a team examine release patterns alongside code output and quality. Before interpreting a deployment-frequency comparison, verify how deployment events reach the platform and which application boundary they describe. A higher release count needs context about what changed and how those changes performed.

[Explore Engineering intelligence](https://weaveos.com/products/engineering-intelligence)

## Sources and further reading

1. [DORA's software delivery performance metrics](https://dora.dev/guides/dora-metrics/)

## Related terms

### [DORA metrics](https://weaveos.com/glossary/dora-metrics)

[Learn the current five DORA software delivery metrics, how they differ from the original four keys, and how to use them with engineering context.](https://weaveos.com/glossary/dora-metrics)

### [Change lead time](https://weaveos.com/glossary/change-lead-time)

[What change lead time measures, where its clock starts and stops, and how it differs from ticket lead time or pull request cycle time.](https://weaveos.com/glossary/change-lead-time)

### [Change failure rate](https://weaveos.com/glossary/change-failure-rate)

[Calculate change failure rate using a clear deployment denominator and distinguish failed production changes from unrelated incidents.](https://weaveos.com/glossary/change-failure-rate)
