---
title: "Blue-green deployment"
description: "Two identical production environments with traffic switched between them, so a release can be rolled back by switching back."
canonical: https://aigovernanceengineer.com/glossary/blue-green-deployment
author: "Jorge García Aibar"
license: "CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)"
doi: https://doi.org/10.5281/zenodo.22956197
version: "0.5.0"
updated: 2026-09-25
---

# Blue-green deployment

Two identical production environments with traffic switched between them, so a release can be rolled back by switching back [1]. It gives an AI system a tested, instant path to the previous version.

- Developed in: [ch. 15, Progressive delivery as a control](https://aigovernanceengineer.com/bok/governing-deployment#progressive-delivery-as-a-control); [ch. 05, Pattern: Staged Rollout with Rollback Criteria](https://aigovernanceengineer.com/patterns/staged-rollout-rollback-criteria)
- Chapters: [ch. 05, Patterns](https://aigovernanceengineer.com/bok/patterns) · [ch. 15, Deployment](https://aigovernanceengineer.com/bok/governing-deployment)
- Contrast with: [Canary release](https://aigovernanceengineer.com/glossary/canary-release)
- In the glossary chapter: https://aigovernanceengineer.com/bok/glossary#t-blue-green-deployment

## Sources

[1] "BlueGreenDeployment" (two identical production environments; switch back on failure). Martin Fowler. 2010-03-01. https://martinfowler.com/bliki/BlueGreenDeployment.html (verified: primary)