Template catalog and marketplace

dagweave gives you three places to start from something instead of a blank canvas: starter blueprints, the catalog of reusable building blocks, and the marketplace where teams share workflows.

Starter blueprints

Blueprints are ready-made example workflows that ship with dagweave. Load one from the workflow menu and it lands on the canvas as editable nodes, including conditional and looping examples. They are a fast way to see how a pattern is built before you make your own. Blueprints are free.

The catalog

The catalog is a curated set of 51 reusable building-block templates, each a real WorkflowTemplate with a defined set of parameters. Several of the everyday palette nodes, such as git-checkout and git-commit-push, come from the catalog. The catalog is version-pinned and read-only, so a given catalog item behaves the same for everyone and only changes when dagweave ships an update.

Browsing the catalog is open to everyone. Six items are open to build with: http-request-curl, download-file, git-clone, run-shell-tests, timed-wait and conditional-when. That is enough to build and run something end to end. The other 45 wrap a product you need an account for, like S3, a database, an LLM or a chat notifier, and saving a workflow that uses one needs a plan that includes the catalog. It is a 402 if yours does not.

Browse and install shared workflows

The marketplace is where teams share whole workflows across the deployment. Browse every team’s listings and install one into your own workspace, where it lands as an editable copy you can use or adapt. The gallery is deployment-wide, not scoped to your own teams. You cannot install your own team’s listing; it already lives in My Templates.

Publish a workflow to the marketplace

Publish one of your WorkflowTemplates as a listing and any team on the deployment can browse and install it. This is separate from browsing: a team can install listings without being able to publish one.

Template versioning

When you use a reusable WorkflowTemplate, dagweave versions it for you. Each template is minted under a content-based versioned name (like base-v1, base-v2), so updating a template creates a new version rather than silently changing runs that already reference the old one. A marketplace listing shows its latest version.