Depot vs werf

Depot provides software delivery tools spanning source control, builds, CI runners, sandboxes, caches, and registries. Its container build service is a drop-in replacement for Docker builds, with persistent caching and native x86 and Arm support. Depot CI runs existing GitHub Actions workflows as a programmable, debuggable CI service, while Depot Registry is an OCI-compliant registry for builds, pull-through caching, and other artifacts. Integrations include GitHub Actions, CircleCI, GitLab CI, Google Cloud Build, Travis CI, Bitbucket Pipelines, Buildkite, Jenkins, and AWS CodeBuild. Cache integrations cover Bazel, Go, Gradle, Maven, Pants, sccache, Nx, and Turborepo. Each build and CI run is isolated in a dedicated virtual machine. Depot says communications use TLS and storage is encrypted at rest; it also identifies SOC 2 Type 2 compliance and time-bound, permission-based debugging access. Plans start at $20 a month, billed monthly, with a 7-day trial and no free plan. Developer includes community support; Business includes Slack Connect support.

werf has no write-up on Specifiction yet; its figures are above.