Pick a catalog step. Skip the manifest.
The catalog covers the parts every pipeline needs: upload to S3, query Postgres, build a docker image, post to Slack. Pick one, fill in a form, and it's a working step on your canvas.
Nobody wants to write the S3 upload step again.
Every team writes the same handful of steps: upload a file, post to Slack.
The catalog already has them written, ready to drop on the canvas.
The steps are already written
Type what you want into the node picker. The step lands on the canvas, and the inspector shows the fields it takes, straight from its schema.
- Every image is pinned by digest, not a floating tag. A workflow you shipped keeps the image it shipped with.
- We keep the images current. You take the update when you want it.
- It's yours to edit, not a black box.
pick -> s3-upload v1.0.0
fill -> bucket, key, file (from the item's own schema)
write -> a WorkflowTemplate in your registry
compile -> templateRef: s3-upload-v1A whole workflow, not just a step
Catalog items are single steps. A blueprint is a complete starter workflow, laid out on the canvas with its dependencies already drawn.
- Open one and edit it into the pipeline you need.
- They're ordinary graphs. Every step is editable as soon as it opens.
The templates your team writes
Publish a WorkflowTemplate your team wrote. Another team installs it into their own registry, where it becomes an ordinary versioned template of theirs.
- Install what another team already got working.
publish -> your WorkflowTemplate, versioned, visible
install -> a copy written into your registry, yours to edit
compile -> templateRef, same as any other templateStart with a step that's already written.
dagweave is in early access. Leave an email and we will bring you on as we open it up.