Try a new build on part of your traffic with canary deployments
October 24, 2026 · release
@voicethere/cli · @voicethere/client
Until now a deploy replaced your agent for everyone at once. With a canary deployment you run the new build on some of your plan's pods, and the same share of new sessions goes to it. On Advanced that is 1 or 2 of 3 pods, on Ultimate anywhere from 1 to 7 of 8. Calls already in progress are never moved.
New sessions are split by round robin, so 1 of 3 pods means exactly every third session. If you would rather keep one caller on one version, name a field of the customerContext your client sends, such as user_id, and the same value lands on the same build for as long as the split stays put.
Seeing how the canary does
Every session now records the build it ran on. The project's Deployments page shows sessions, failed sessions, failure rate and the most common failure reasons per build, over the last hour, day or week, and the sessions list can be filtered by deployment.
A canary aborts itself when more than 20 % of its ended sessions fail, once at least 20 have ended. Both numbers are yours to change, and you can switch auto-abort off. When the canary looks good, promote it and it becomes the stable build.
Try it
voicethere deploy --build-id <id> --canary-pods 1 --wait
voicethere canary status
voicethere deployments metrics --since 24h
voicethere canary promote --yes
The routing modes, the API routes, the SDK option and every error code are in Canary deployments. Canary deployments are not available on Free, Budget and Budget+.