Fenwave Flow
A whole release, drawn once and launched in one click
A release is rarely one deploy: three frontends from their tags, the backend to production, a storage sync, then the cache to flush by hand. Flow turns that into a runbook you draw once — numbered stages, steps side by side when they can run in parallel, manual steps as gates — and launch whenever the request comes in. Each step goes through the same pipeline as its own screen and runs with the permissions of the person who launched it.
ReleaseBeta
In this capability
- Designer with a palette of steps: frontend deploy, environment deploy to dev, staging or production, storage sync, manual step
- Steps in the same stage run in parallel; a stage starts when the one before is done
- Manual steps with instructions and a checklist pause the run until someone marks them done
- At launch, fill every step up front and untick what is not needed this time; production asks for an explicit confirmation
- Live run view: retry a failed step, skip it, or cancel the run; a failure blocks only what depends on it
- Slack pings when a manual step is waiting and when the run finishes; “Launch again” reuses the last values
In Fenwave
Deploy›Flows›New flow
Built on
- Argo Workflows
- ArgoCD
- Slack
More in Release
- Deployment ManagerRun the release, not just the deploy
- Frontend AppsBetaShip SSR and static frontends without a cluster
- ShopifyBetaShip Shopify themes and apps like any other service
See Fenwave on your own projects
Thirty minutes, on your repositories and your clusters. We will point out three requests your platform team would stop receiving as soon as next week.