CI/CD · Visual Explainer
CI vs CD vs CD
The concept
Continuous Integration: every commit is automatically built and tested. Continuous Delivery: every passing build is packaged and one human click from production. Continuous Deployment: remove the click — every passing build ships itself.
Key distinctions
| Term | What it means |
|---|---|
| CI | Answers 'does everyone's code work together?' — the foundation everything rests on. |
| Delivery | Answers 'could we release right now?' — the human gate is a business decision, not a technical bottleneck. |
| Deployment | Removes the gate — needs honest test coverage, fast rollback, and monitoring that catches failure before customers do. |
| The insight | Deployment isn't more advanced than Delivery — it's a different risk posture. The only difference is one approval button. |
Why it matters in practice
Most client-service businesses rationally stop at Delivery, because the approval gate is where client review and coordinated launches live. Choosing the gate deliberately is engineering.