# Continuous Delivery

> Keeping code ready to release at all times. Going live is one click.

**Field:** Software Development  
**Category:** DevOps & Cloud  
**Also known as:** CD, Continuous Delivery (CD)

## Think of it like

Think of it like a packed suitcase by the door. You can leave on any day you choose.

## Definition

Continuous delivery means your code is always ready to release, at the push of a button. Every change that passes the tests is built and sent to staging on its own. Going live is one click, but a person still decides when. Releases become small and boring, not big and scary. It is the step after CI.

## Example

Lucy's team can release any green build in five minutes. They choose to go live each Tuesday morning, when support staff are awake.

## Why it matters

When release is one click, you ship a fix the moment it is ready. You do not wait for the next big launch.

## Common mistake

Calling it continuous delivery while releases still need a day of hand steps. If it is not one click, it is not there yet.

## Three principles

- **Always ready.** Any green build can ship.
- **A person decides.** When to press the button.
- **Small releases.** Boring is good.

## Related terms

- [Continuous Integration (CI)](https://learn.benibix.com/term/development/continuous-integration)
- [Continuous Deployment](https://learn.benibix.com/term/development/continuous-deployment)
- [CI/CD Pipeline](https://learn.benibix.com/term/development/ci-cd-pipeline)
- [Staging Environment](https://learn.benibix.com/term/development/staging-environment)
- [DORA Metrics](https://learn.benibix.com/term/development/dora-metrics)

## Told apart from

- [Continuous Delivery vs Continuous Deployment](https://learn.benibix.com/compare/continuous-delivery-vs-continuous-deployment): Continuous delivery and continuous deployment both test and build every change on their own, but only one ships it by itself. With delivery, the code is always ready. A person clicks to go live. With deployment, there is no click. Each change that passes the tests goes straight to users.
- [Continuous Integration (CI) vs Continuous Delivery (CD)](https://learn.benibix.com/compare/continuous-integration-vs-continuous-delivery): People think CI and CD are one step, because they are written together as CI/CD, and they are not. CI checks each change: it builds the code and runs the tests on every push. CD comes after it and takes a passing change toward the live site. You can have CI with no CD, but not CD with no CI.

---

Source: https://learn.benibix.com/term/development/continuous-delivery
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-18
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
