Continuous deployment
Definition
Continuous deployment is the practice of automatically releasing every code change that passes all automated tests and pipeline gates directly to production — no manual approval required.
Continuous deployment is the most advanced point on the delivery automation spectrum: CI → continuous delivery → continuous deployment. The difference from continuous delivery is the absence of a manual release gate. In continuous deployment, if the build is green, it ships.
This requires an extremely high level of trust in the automated test suite. A test that misses a critical bug will ship that bug to production immediately. The tradeoff is speed and feedback: teams practicing continuous deployment can ship dozens or hundreds of times per day, collecting real user data faster than any manual-approval process allows.
Teams that practice continuous deployment typically combine it with feature flags. Code ships continuously, but features are controlled by flags — so a new feature can be in production (dark launch) before any users see it. When the team is ready, the flag flips and the feature is live. This decouples code deployment from feature release, removing a major source of anxiety about automatic deployment.
Examples of organizations with mature continuous deployment practices: Amazon (reportedly thousands of deployments per day across teams), Netflix, Etsy, Flickr (famously documented their CD journey in a 2009 Velocity talk that helped launch the DevOps movement).
Continuous deployment is appropriate for web services and APIs where rollback is fast. It's less common for mobile apps (where App Store review is a mandatory gate) and regulated systems (where human-approved change control is required).
Examples
- SaaS API: every merged PR triggers a pipeline; if all checks pass in 8 minutes, the new code is live in production
- Feature flag deployment: new algorithm ships to production disabled; data team enables it for 1% of users, then 10%, then 100%
- A/B test via deployment: two versions ship simultaneously; traffic splits by user cohort; winner gets 100% rollout
- Hotfix deployment: bug fix commits to main, pipeline completes in 6 minutes, production is patched — no release meeting required
Related terms
Snap a continuous deployment. Ship its actions.
BoardSnap turns any whiteboard — including this one — into a summary and action plan.