AnyoneLearnAI
LevelEasyStart
Build garageTry it → read → next · ~10 min

Tutorials · Chapter D (4/4) · ~10 min

Canary deploy lab

Try it → see it → read → next

Ship **v2 to 10% traffic** first — promote when metrics hold, rollback when they don’t.

On paths: Builder · Student

Try tools: Code & developers

Try yourself

Playground

Canary deploy desk

Split traffic, watch metrics, rollback or promote — never big-bang without a safety net.

Route 10% traffic to v2

Canary, rollback, or promote?

Recap

What you just did

You chose canary vs rollback vs promote for each release step.

Read

[Runbook](/reference/runbook)

  1. Keep v1 as instant rollback target
  2. Route 5–10% to v2 with same request IDs in traces
  3. Compare [p95 latency](/reference/p95-latency), error rate, groundedness
  4. Promote or rollback — never leave a bad canary running