Deployment Manager
Run the release, not just the deploy
One screen for dev, staging and production, backed by ArgoCD and GitOps — and above it, the release itself. Build a release from your components and their git tags, pull the scope straight out of Jira, generate the release notes from the Jira issues and the pull requests, then run the production window as a runbook whose steps have named owners and approval gates. QA approves in the tool, not in a thread.
In this capability
- One-click deploy per environment, with approval gates on production
- Release wizard: pick the system, set a git tag per component, review and create
- Jira integration — scope a release by version and group its issues by type
- Release notes generated from the Jira issues and the pull requests they came with
- Production runbook with phases, per-step owners, approval gates and wait timers
- Runbooks saved as reusable templates, so the next release starts from the last one
- Instant rollback to any previous revision, with the full history: commit, author, duration, outcome
- Serverless container targets in beta: Cloud Run, Fargate and Azure Container Apps
In Fenwave
Environments›Deployments›Releases
Built on
- ArgoCD
- Kubernetes
- Helm
- Jira
Where teams use it
More in Release
- Fenwave FlowBetaA whole release, drawn once and launched in one click
- 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.
