Skip to content
dagweavedagweave docs

Dagweave Local

Dagweave Local runs a dagweave workflow on your own machine instead of a cluster. No Kubernetes to install, nothing to connect, and no dagweave account needed for any of it, other than the optional step at the end that shows your runs in this app.

It is a single binary, and that binary is the whole product. There is no separate CLI to install alongside it and no companion tool to hunt down: every command on this page and the ones after it is dagweave itself.

Installing

Section titled “Installing”

macOS and Linux:

Terminal window
curl -fsSL https://github.com/dagweave/local-releases/releases/latest/download/dagweave-$(uname -s | tr '[:upper:]' '[:lower:]')-$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/') -o dagweave && chmod +x dagweave

Windows, in PowerShell:

Terminal window
irm https://github.com/dagweave/local-releases/releases/latest/download/dagweave-windows-amd64.exe -OutFile dagweave.exe

Move it onto your PATH as dagweave. You’ll need Docker installed if your steps run containers.

Want a specific build instead of the one these commands detect? Pick the file for your machine from the releases page:

Your machine File
Linux, Intel/AMD dagweave-linux-amd64
Linux, ARM dagweave-linux-arm64
macOS, Intel dagweave-darwin-amd64
macOS, Apple Silicon dagweave-darwin-arm64
Windows, Intel/AMD dagweave-windows-amd64.exe
Windows, ARM dagweave-windows-arm64.exe

The GitHub CLI fetches a build and the files that verify it in one go:

Terminal window
gh release download <tag> --repo dagweave/local-releases \
  --pattern 'dagweave-linux-amd64' --pattern 'SHA256SUMS*' --pattern 'cosign.pub'

Swap in your platform’s filename for dagweave-linux-amd64 and the tag the releases page showed you for <tag>.

Verifying the download

Section titled “Verifying the download”

Every release carries SHA256SUMS, a cosign signature over it (SHA256SUMS.sig), and the public key that signature checks against (cosign.pub); the gh release download command above fetches all three alongside the binary. Verify what you got before you run it:

Terminal window
cosign verify-blob --key cosign.pub --signature SHA256SUMS.sig SHA256SUMS
sha256sum --check --ignore-missing SHA256SUMS
chmod +x dagweave-linux-amd64
./dagweave-linux-amd64 version

If you downloaded through a browser

Section titled “If you downloaded through a browser”

Dagweave Local is not signed by Apple or Microsoft, only by cosign, which is what the commands above check. Cosign proves the binary came from this build and nothing altered it in transit. It does not stop your OS asking who Apple or Microsoft think published it, because neither of them has been paid to say. That dialog is a browser thing: curl, irm, and gh never mark a file this way, so the commands above never trigger it.

macOS refuses outright to run a binary a browser downloaded, because the browser marks the file quarantined. If you already have a quarantined copy, clear the mark yourself:

Terminal window
xattr -d com.apple.quarantine ./dagweave-darwin-arm64

Windows shows a “Windows protected your PC” SmartScreen screen instead of refusing outright. Click More info, then Run anyway, or clear it up front from PowerShell:

Terminal window
Unblock-File -Path .\dagweave-windows-amd64.exe

Next steps

Section titled “Next steps”