Deployment frequency
Deployment frequency is how often your organization successfully ships to production; it reflects batch size and release capability more than raw coding output.
These pages explain common engineering and delivery metrics in plain language. Definitions vary by company, toolchain, and industry; we highlight typical usage and caveats. Nothing here is legal, financial, or professional advice, and it is not a substitute for judgment in your own context.
Metrics can be misused for surveillance or stack ranking. We do not recommend using them that way. DORA performance bands from research are contextual—not targets for individuals or hiring decisions.
See the Engineering metrics glossary hub for all terms.
Definition
Deployment frequency is a DORA metric: how often your application or service is deployed to production (or released to end users) in a successful way.
Higher frequency often goes hand in hand with automation, smaller changes, and lower risk per change—but “more deploys” is not a universal goal if your users or compliance model require controlled release cadences.
How teams typically measure it
- Count production deploy events from CI/CD, release tooling, or deployment logs; exclude failed deploys that never reached users.
- In multi-service systems, decide whether you measure per service, per product, or per organization—each answers a different question.
- Mobile and embedded teams may ship less often than SaaS web apps; that does not automatically imply lower maturity.
Common pitfalls
- Gaming by splitting one logical release into many trivial deploys to inflate counts.
- Using deploy frequency as a team ranking without accounting for architecture (microservices vs monolith) and release policy.
Related terms
Browse other entries in the glossary.