Canary rollouts: upgrade models in production without downtime
Together AI
Rollouts automate traffic migration between two model deployments by running canary, blue-green, or rolling upgrades with built-in health checks and rollback controls. The default canary traffic ladder is 5% → 25% → 50% → 100% with a wait window of at least 390 seconds per step when using metric gates. This replaces manual hard swaps or DIY staged cutovers by letting the platform enforce step ordering, pause on failed gates, and complete or cancel without leaving traffic in an ambiguous state.
Why it matters
A hard model swap exposes every user at once, and rolling back means cold-starting the old deployment under pressure. Here's how staged traffic ramps, metric gates, and automatic rollback work on dedicated inference.