Tools & downloads

All of this ships with YakDeploy already. Until now none of it was linked from anywhere in the product, which is a poor way to treat a Terraform provider.

Command line

One static binary, no runtime. Deploy, watch a run, tail a log, cut a release — carrying the same role and environment scope as your account. Current build 1.0.0.

• linux · amd64
• yakdeploy-linux-amd64-df738180a4fbecffa1056c8529de7453

yakdeploy deploy yakdocs --to staging --wait

GitHub Action

Keep building where you build today and hand the deploy over.

- uses: yakware/yakdeploy-action@v1
  with:
    project: yakdocs
    environment: staging

Terraform provider

Projects, environments, targets and variables as resources, so the thing that describes your infrastructure also describes how it gets deployed.

terraform {
  required_providers {
    yakdeploy = { source = "yakware/yakdeploy" }
  }
}

Runners on Kubernetes

A Helm chart with KEDA scaling: runner pods appear when the queue grows and go away when it drains. The scaler reads /runner-api/queue-depth.

helm install runners yakdeploy/runner --set token=$YAK_DEPLOY_RUNNER_TOKEN

Run YakDeploy yourself

One container and a Postgres. Same product, your hardware, no phone-home — and a backup script that restores, which is the only kind worth shipping. Self-hosted runs at the top plan's limits.

curl -O https://yakdeploy.com/selfhost/compose.yml
docker compose up -d