# Canary Release

> Give a new version to a few users first, then to more and more.

**Field:** Software Development  
**Category:** DevOps & Cloud  
**Also known as:** Canary Deployment, Canary, Canary Rollout

## Think of it like

Think of it like testing soup. You take one spoon before you serve the pot.

## Definition

A canary release sends the new version to a small share of users first, like 5 percent. The team watches errors and speed for that group. If all looks fine, the share grows step by step until everyone has it. If errors rise, the canary is pulled and only a few users were hurt. The name comes from canaries that miners once took underground to warn of bad air.

## Example

Jack sends version 5 to 5 percent of users. Errors stay flat for an hour, so he moves it to 25 percent, then 100 percent by evening.

## Why it matters

A bug that slips past every test meets a few users, not all of them. Real traffic is the final test.

## Common mistake

Running a canary but not watching it. With no clear error and speed numbers, you cannot tell if to grow or stop.

## Three principles

- **A few users first.** Like 5 percent.
- **Watch the numbers.** Errors and speed.
- **Grow or pull.** Step by step.

## Related terms

- [Deployment Strategy](https://learn.benibix.com/term/development/deployment-strategy)
- [Blue-Green Deployment](https://learn.benibix.com/term/development/blue-green-deployment)
- [Feature Flag](https://learn.benibix.com/term/development/feature-flag)
- [Rolling Update](https://learn.benibix.com/term/development/rolling-update)
- [Shadow Deployment](https://learn.benibix.com/term/ai/shadow-deployment)

## Told apart from

- [Blue-Green Deployment vs Canary Release](https://learn.benibix.com/compare/blue-green-vs-canary): Blue-green deployment and a canary release both make a new version safer to ship, but they move users in different ways. Blue-green moves every user at once, from one full copy to the other. It can switch back in seconds. A canary moves a few users first, then more. Blue-green is quick; a canary keeps a bug small.
- [Shadow Deployment vs Canary Release](https://learn.benibix.com/compare/shadow-deployment-vs-canary-release): People think a shadow deployment and a canary release are the same careful way to launch a model, and they are not. In a canary, a few real users get the new version and see what it does. In a shadow deployment, no user sees the new model at all. It gets a copy of real requests, and its answers are only saved. A canary tests on people. A shadow tests in secret.
- [Canary Release vs Feature Flag](https://learn.benibix.com/compare/canary-release-vs-feature-flag): People think a canary release is the same as a feature flag, since both can start with 5% of users, and it is not. A canary sends some users to a new version of the whole app, on its own servers. A flag is a switch inside the code that turns one feature on for some users. A canary tests a deploy. A flag tests a feature.

---

Source: https://learn.benibix.com/term/development/canary-release
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.
