Ship a workflow like you ship software
A change is planned as a changeset, executed, and then weighted between versions from 0 to 100% — so a new version proves itself on a slice of real traffic before it owns all of it.
Reviewable changesets, traffic weighted between versions from 0 to 100%, and configuration promoted between environments.
How a change ships
- Deploy as a reviewable changeset — A deployment is planned first, so you see what it will change before it changes anything, then executed — or cancelled. Every stage is audited, and the resource changes it makes are correlated back to it, so a release reads as one unit rather than a scatter of edits.
- Weighted traffic between versions — Route a percentage of incoming events to a new version and leave the rest on the old one. Send 5% first, watch the error rate on the monitoring view, then move the dial — or move it back, without a redeploy.
- Promote configuration between environments — Export a workspace's configuration and import it elsewhere, with an explicit strategy for what happens when something already exists. Staging stops being a place where you retype what production already knows.
- Environment-scoped variables and secrets — The same workflow definition points at different endpoints and credentials depending on where it runs. Promotion moves the shape of the workflow without dragging production keys into a test environment.
Platform capabilities
- 0–100%: Traffic weight per version
- Plan → execute: See the change before it lands
- Export/import: Move config between environments
Can I roll a new version out gradually?
Yes. Traffic is assigned to versions as weights from 0 to 100, so you can start a new version on a small share of live events, compare its error rate against the previous version, and shift the weight in either direction without redeploying.
What happens to runs already in flight when I deploy?
Versions coexist rather than replace one another, so an execution keeps running against the version it started on. The weight decides which version new events enter — it does not reach in and rewrite work that is already under way.
Do I have to rebuild my workflows in each environment?
No. Configuration is exported from one workspace and imported into another, with a conflict strategy that says what to do about anything already present. Variables and secrets stay scoped to their environment, so the definition travels and the credentials do not.