TapCub is live — analytics, insights and live chat, free on one platform
Glossary

What is progressive delivery? Staged rollouts and metric gates

Progressive delivery releases a change in stages, widening only when metrics stay healthy. A 1% to 100% plan, how long each stage needs, and which metrics to gate on.

Oliver Reed Reviewed by Emma Collins Also called progressive rollout Last updated Nov 20, 2026 Glossary

Quick answer

Progressive delivery is releasing a change to users in stages, such as 1%, 5%, 25% and 100% of traffic, and moving to the next stage only when measured gates (error rate, latency, a business metric) stay healthy, with traffic returned to the old version if they fail.

What is progressive delivery?

Progressive delivery is releasing a change to users in stages, starting with a small share of traffic and widening only when measured results stay healthy. It separates two things that used to happen together: deploying code to production and releasing it to people. The term was popularized by RedMonk analyst James Governor, whose August 2018 post argued that routing techniques such as feature flags and canarying deserve their own name beyond CI/CD.

In practice, each stage has a gate: a metric and a threshold the new version must meet before it gets more traffic. If the gate fails, traffic goes back to the old version. The rest of this page shows how to choose stages, how to size a gate so it can actually detect a problem, and what you can and cannot measure.

Progressive delivery vs related practices

PracticeWhat it controlsWho sees the changeTypical rollback
Big-bang releaseEverything at onceAll usersRedeploy the old version
Canary releaseShare of traffic per versionA small random share, then moreRoute traffic back
Feature flagWhich users get a featureChosen users or percentagesSwitch the flag off
Blue-green deploymentWhich full environment is liveEveryone, at the switchSwitch back to the old environment
Beta programOpt-in accessVolunteers who know it is unfinishedEnd the program
Progressive deliveryThe whole staged process with gatesGrowing share, by stageAutomatic or manual, at any stage

Progressive delivery is not a rival to canaries and flags. It is the process that uses them, plus the measurement rule that decides when to continue.

Staged rollout: an example plan

Sample data: a web service receives 400,000 requests per day. The stable version has an error rate of 0.5%. The team will not accept more than 0.3 percentage points of extra errors, so the gate is a canary error rate of at most 0.8%.

StageTraffic to new versionRequests per day at that shareGate to move on
11%4,000No crash loops; error rate not above 5%
25%20,000Error rate ≤ 0.8% and latency within 10% of stable
325%100,000Same gate, plus no drop in the main business metric
450%200,000Same gate
5100%400,000Keep watching for 24 hours

Argo Rollouts, an open source controller, expresses plans of this shape as setWeight steps with pause durations between them, and aborts the rollout if an analysis fails. Without a traffic router it approximates the percentage with replicas: with 10 replicas, a 10% step means one canary and nine stable.

How long should each stage last?

A gate is only useful if the stage collects enough requests to detect the problem you care about. For comparing two error rates (0.5% on stable, 0.8% if the canary is worse) with a two-sided 5% significance level and 80% power, the standard two-proportion sample size formula gives about 11,263 requests per arm. Treating that as a rough guide (it assumes equal arms; a small canary against a large stable group needs a little more):

StageShareTime to reach 11,263 canary requests at 400,000/day
11% (4,000/day)2.8 days (67.6 hours)
25% (20,000/day)0.56 days (13.5 hours)
325% (100,000/day)0.11 days (2.7 hours)
450% (200,000/day)0.06 days (1.4 hours)

Two conclusions follow. First, the 1% stage cannot detect a 0.3-point rise in a sensible time, so do not use it for that: use it as a blast-radius check for failures that are large. Detecting a jump from 0.5% to 5% needs only about 206 requests per arm, which 1% of traffic provides in roughly an hour. Second, the cost of a bad release is bounded by the stage share. Google's SRE Workbook gives the arithmetic: a canary with a 20% error rate on 5% of traffic raises the overall error rate by about 1% (0.20 × 0.05 = 0.01).

Choosing metrics for the gates

The SRE Workbook's guidance on canary metrics is a good checklist:

  • Start with signals users feel, such as failed requests and latency, not CPU.
  • Keep the list short, "perhaps no more than a dozen."
  • Leave out 400-level HTTP codes, which often reflect user error rather than a defect.
  • Break monitoring down by canary versus control; whole-service averages can hide a canary's errors.
  • Run one canary at a time, so you know which change moved the metric.
  • Make sure metric intervals are no longer than the canary duration.

Add one business gate to the technical ones: for a web or app change, a core conversion or activation rate, compared at the same stage between old and new.

When progressive delivery is not enough

  • Rare problems. A defect that affects 1 in 10,000 requests will not show up in a 4,000-request stage.
  • Slow problems. Memory leaks, billing errors and retention drops appear after hours or weeks. Keep the final stage under watch.
  • Shared state. Database schema changes cannot always be rolled back by moving traffic. Make them backward compatible first.
  • Unequal arms. The sample size above assumes the canary and stable groups are the same size. A 1% canary against a 99% stable group needs more canary requests for the same power, so treat the table as a lower bound.
  • Low traffic. With 4,000 requests a day, even the 100% stage is thin. Use fewer stages and longer holds.

What TapCub measures during a rollout

Imagine a mobile app update released to 5% of users first. TapCub does not split traffic or run flags, so the rollout itself happens elsewhere (your app store's staged release, a flag service or your deploy tool). TapCub only measures what each version does.

  1. Compare versions. App analytics › Users › Versions lists each version with its share of active users and crash count. Select the new version to filter the page to it.
  2. Compare stability. App analytics › Quality & attribution › Stability shows the crash-free share (1 − crash users ÷ active users); filter by the new version and read it against the previous one.
  3. Watch errors on web. Monitoring › Errors groups errors with counts, affected sessions and last-seen times, so a new error group after a deploy stands out.
  4. Get alerted. In All-platform analytics › Operations › Monitors, create a monitor on error_rate with a threshold such as 0.8%. A dry run tells you how often it would have fired over the past 30 days. A monitor only notifies; it does not roll anything back.
  5. Mark each stage. Add a note per stage in Configuration › Annotations (1%, 5%, 25%...), so every chart shows where the rollout steps were.

Sources

Was this explanation clear?

We use your answers to fix and expand this page.

Oliver Reed

Product Experience Specialist

Explores usability, user journeys, and feature adoption through practical examples of onboarding and everyday product use.

FAQ

Questions people ask

Short answers to the follow-up questions that come up most.

Still have a question?

Chat with the team behind TapCub — we usually reply within a few hours on business days.

What is the difference between progressive delivery and continuous delivery?

Continuous delivery keeps software always ready to release. Progressive delivery controls how a release reaches users: in stages, to a growing share of traffic, with metric gates that can stop or reverse it.

Is progressive delivery the same as a canary release?

No. A canary release is one technique: send a small share of traffic to the new version. Progressive delivery is the whole process, which can combine canaries, feature flags and automatic analysis between stages.

What percentage should the first stage be?

Small enough that a failure is cheap and large enough to see failures at all. 1% to 5% is common. A 20% error rate on 5% of traffic adds only about 1% to the overall error rate.

Do you need feature flags for progressive delivery?

Not always. You can stage by traffic share with a router or by replicas. Flags help when you want to stage by user group instead, or to turn a feature off without redeploying.

See this number on your own site

Add one script tag for web and apps, and the first reports fill in within minutes.

See your data clearly. Find your growth.

Every click, backed by data. Install one line of code and see your first numbers in a minute.

No credit card · Free plans for analytics and chat · Cookieless analytics