macOS
brew install werflocal Homebrew formula metadata
brew
Consistent delivery tool for Kubernetes. Version 2.72.2 via Homebrew; verified 2026-07-02.
install
brew install werflocal Homebrew formula metadata
nix profile install nixpkgs#werfnixpkgs package indexes · pkgs/by-name/we/werf/package.nix · source: api.github.com
sudo zypper install werfopenSUSE Tumbleweed package metadata · werf · source: download.opensuse.org
overview
Consistent delivery tool for Kubernetes
history
werf is a Kubernetes delivery CLI from the Flant ecosystem and a CNCF Sandbox project. The project describes itself as a full-cycle CI/CD tool that glues together Git, Dockerfile or Buildah image building, Helm-style deployment, Kubernetes, and a user's existing CI system.
The project began in January 2016 under the earlier `dapp` name, before Kubernetes deployment became central to its identity. The official tenth-anniversary history describes the starting point as an experiment in incremental Docker image building that later grew into an open source delivery ecosystem for Kubernetes applications.
In March 2017, dapp gained Kubernetes deployment via Helm charts, shifting the tool from image building toward end-to-end application delivery. The public GitHub repository dates to January 2016, and werf's own retrospective groups the pre-2019 period as the dapp and early werf era before the v1 line.
werf v1 covered the December 2018 through March 2020 transition, while the v1.1 and v1.2 eras added production-oriented behavior such as content-based tagging, distributed layer storage, bundles, and increasingly reproducible deployment artifacts. In May 2023, the project began moving away from its Helm fork toward Nelm, a Helm-compatible deployment engine developed as part of the broader werf ecosystem.
On December 13, 2022, CNCF accepted werf at Sandbox maturity. That gave the project formal cloud-native foundation status and framed it as a community project rather than only a vendor-maintained delivery tool.
werf's README says it has been used in production since 2017 and that thousands of projects rely on it. The 2026 anniversary post gives a more concrete ecosystem snapshot: 4600+ GitHub stars, 1300+ releases, 18,000+ active projects using werf, 15,000+ commits, 60+ contributors, and 6000+ merged pull requests.
Its adoption pattern is strongest among teams that want CI/CD behavior in Git but do not want to replace their existing CI service. werf is designed to run inside GitLab CI, GitHub Actions, or other CI systems while owning the build, publish, deploy, tracking, and cleanup parts of a Kubernetes release.
A typical werf project keeps a `werf.yaml` file in the source tree and lets the CLI build container images, publish them to a registry, deploy Helm-compatible charts to Kubernetes, track rollout status, and clean old artifacts. This makes werf closer to an application delivery orchestrator than a single-purpose image builder.
In package terms, werf matters because it packages several common cloud-native primitives into one repeatable CLI workflow. That role also explains its related projects: Nelm for Helm-compatible deployment, trdl for update channels, kubedog for Kubernetes rollout tracking, and lockgate for synchronization.
security posture
infrastructure mutation or orchestration signal.
orange risk · medium confidence · infrastructure
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Config paths the tool may read or write during local use.
werf.yamlCredential-bearing paths to review before unattended agent runs.
~/.werf/global_secret_key.werf_secret_keyexecutables
| Command | Kind | Exposure | Note |
|---|---|---|---|
werf | cli | global executable |
freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
install metadata
| Package key | brew:werf |
|---|---|
| Version | 2.72.2 |
| Package manager | Homebrew |
| Package manager page | https://formulae.brew.sh/formula/werf |
| Homepage | https://werf.io/ |
| Repository | https://github.com/werf/werf |
| Upstream docs | https://werf.io/docs |
| License | Apache-2.0 |
| Source archive | https://github.com/werf/werf/archive/refs/tags/v2.72.2.tar.gz |
| Last updated | 2026-07-02T12:13:46Z |
| Pulse | updated |
| Build dependencies | go |
| Bottle | available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux) |
| Homebrew post-install | not defined |
| Service | none declared |
registry facts
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | werf |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
source database matches
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
werf
nix profile install nixpkgs#werfwerf 2.68.2-1.1
CLI for the Werf CI/CD system
sudo zypper install werfwerf-bash-completion 2.68.2-1.1
Bash Completion for werf
sudo zypper install werf-bash-completionwerf-fish-completion 2.68.2-1.1
Fish Completion for werf
sudo zypper install werf-fish-completionwerf-zsh-completion 2.68.2-1.1
Zsh Completion for werf
sudo zypper install werf-zsh-completionsource trail
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
View the package source record on GitHub.