Get on the list.
Dagweave is the visual editor for Argo Workflows. It's pre-launch. Early access is the way in today. Leave an email and we'll get in touch as we bring people on.
Want to run something now? Dagweave Local is free to download today.
Draw it or import it. Send it to your repo and your clusters.
The canvas and the YAML pane
Pick each step from a searchable list and wire up the dependencies. Drill into nested sub-workflows as deep as they go. The manifest compiles next to the graph the whole time.
Your existing workflows, imported
From a GitHub repo, from a live cluster, or pasted in. Your whole file opens, retry strategies and artifact repository refs included. It goes back out as the same standard manifest, in your own repo.
Every cluster you run
Enrol as many clusters as you run. After that anyone with a Dagweave account can dispatch to them, without a kubeconfig of their own.
Straight into your GitHub repo
A direct commit or a pull request. What lands is a standard Argo Workflows manifest. It keeps working if you stop using Dagweave.
Common questions.
What is the state of it today?
Pre-launch. Leave an email and we'll bring you on as we open it up.
Can I try anything today?
Yes. Dagweave Local runs your workflows locally. It's free, and you don't need an account. Want a UI? Connect it to the Dagweave app with a paid plan. Download Dagweave Local.
Do you run my workflows?
No. Dagweave is a builder, not a runtime. It writes Argo Workflows manifests and, once you enrol the connector, sends runs, WorkflowTemplates and CronWorkflows to your cluster, and reports what comes back. Argo Workflows executes all of it, on your own infrastructure.
Why Argo Workflows rather than something else?
CNCF-graduated, and it schedules on Kubernetes natively. Dagweave adds the authoring layer and leaves the engine alone.
Do I have to choose between git and the connector?
No. The workflow lands in your repo as a manifest you own. A dispatch compiles that same workflow into a run and sends it to whichever enrolled cluster you pick.
Am I locked in?
No. The output is a standard Argo Workflows manifest, sitting in your own repo, running on your own cluster. Stop using Dagweave tomorrow, and every workflow carries on.
What does it install in my cluster?
One connector, from one Helm chart, and every connection it opens is outbound. It writes Argo Workflows objects and its own CRDs, and refuses to apply anything else. It reads pods, ConfigMaps and logs to report back, and can fetch a Secret only when it's given the name. Name your namespaces and most of that is scoped to them. Every permission it holds is on the security page.
What happens to my email?
We store your email to tell you when we open up. That is the whole use. No third-party tracking. To be removed, email hello@dagweave.com.