Self-hosted service
werf/werf avatar
werf/werf

werf: a Go CLI that glues Git, Dockerfile, Helm and Buildah into one build-and-deploy flow for Kubernetes

A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices.

4,737 stars241 forksGoApache-2.0

At a glance

What is it?
werf/werf is an Apache-2.0 CNCF Sandbox command line tool that builds container images, deploys them to Kubernetes through Helm and cleans the container registry. It runs two major version lines side by side and labels each release with a stability channel.
Who is it for?
werf suits teams that deploy to Kubernetes from a CI system and want one tool to build from Dockerfiles, tag by content, deploy with Helm and clean the registry. It does not suit teams that deploy anywhere other than Kubernetes, or teams that want a hosted pipeline instead of a CLI.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
Mainly Go, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • werf/werf4,737 ★ · +14
Star history
Repository2026-09-232026-11-15
werf/werf4.7k4.7k

14 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Your configuration stays a Dockerfile and a Helm chart, and werf handles the rest

werf's ease-of-use pitch is that you use Dockerfiles and a Helm chart for configuration and let werf handle all the rest. It integrates into your CI system and relies on technologies you may already run: Git, Dockerfile, Helm and Buildah. The project calls this gluing common technologies together.

The consequence is that adopting werf does not mean learning a new pipeline language for the basic case. Your existing Dockerfile builds the image and your existing chart describes the release. The flip side is that werf is a Kubernetes tool through and through. If part of your fleet runs on virtual machines or another orchestrator, werf covers only the Kubernetes side, and you still need something else for the rest.

It manages the whole lifecycle: build, publish, test, deploy, distribute and clean up

The first feature listed is complete application lifecycle management. In one tool you build and publish container images, test, deploy an application to Kubernetes, distribute release artifacts and clean up the container registry. werf describes itself as a CLI tool for full-cycle CI/CD to Kubernetes, and it integrates into your CI system, which means it does not replace the CI runner.

That division matters when you plan the pipeline. Your CI system still triggers jobs, holds secrets and decides when to run. werf is what each job calls. If you already have Git-based CI, the change is swapping several separate scripts for werf commands. If you are looking for a hosted pipeline with a web interface, werf is not that.

Build caching, content-based tagging and registry cleanup are the advanced features

Under advanced features the README names automatic build caching and content-based tagging, enhanced resource tracking and extra capabilities in Helm, and a unique container registry cleanup approach. Content-based tagging means images are identified by what they contain rather than only by a manually assigned version.

The aim of content-based tags is that an unchanged component keeps its identity across deployments. Registry cleanup is worth testing before you rely on it. Deleting images is destructive, and the README does not describe the cleanup policy in detail, so read the documentation on cleanup rules and try it on a non-production registry first. The same applies to the Helm extensions, since resource tracking behaves differently from plain Helm.

Two major versions are released side by side, and tags carry channel labels

The recent releases show v3.12.2 on 2026-10-29, v2.84.1 on 2026-10-29 and v3.12.1 on 2026-10-22. The release titles carry labels in brackets: v3.12.2 is marked alpha and beta, v2.84.1 is marked alpha, and v3.12.1 is marked ea, stable and rock-solid. The module path in go.mod ends in v3, so the main line is version 3, while version 2 still receives releases.

The lesson is that the newest tag is not necessarily the one to deploy. A fresh v3.12.2 carries only the alpha and beta labels, while v3.12.1 from a week earlier carries ea, stable and rock-solid. If you want the most conservative choice, pick the version with the most conservative label, and note that your choice of major line is real: v2 and v3 are both being maintained.

Built on a heavy Go dependency set: BuildKit, containerd, go-git and cloud registries

go.mod requires Go 1.26.3 with toolchain go1.26.8. The dependencies include Docker buildx and BuildKit, containerd, the Docker CLI and daemon libraries, go-containerregistry, go-git, the AWS SDK for ECR, oras, and Masterminds sprig and semver. The repository also has a stapel directory, a playground, JSON schemas for configuration, and trdl files for its release channels.

For users, the downloaded binary is the thing to install. For contributors, building from source needs a recent Go toolchain and there is a Taskfile, a golangci configuration and a CODESTYLE.md. Check which build backend your CI runners can support before you rely on a given build mode.

Guides cover five frameworks, and support runs through several channels

The documentation is available in multiple languages. The werf guides give developers ready-to-use examples for popular frameworks: Node.js with JavaScript, Spring Boot with Java, Django with Python, Rails with Ruby and Laravel with PHP, and they include a basic understanding of Kubernetes primitives. The Getting Started guide covers local setup and CI setup.

Support options are GitHub Discussions, Stack Overflow with the werf tag, GitHub issues, the werf channel in the CNCF Slack workspace, and Telegram chats, one English and one Russian speaking. The README says the team is notified when you tag a Stack Overflow question with werf. If you work in a language outside those five frameworks, the Dockerfile route still applies, but you will have no matching guide to copy.

Production use since 2017 and CNCF Sandbox status describe maturity, with different weight

The README says werf has been used in production since 2017 and that thousands of projects rely on it to build and deploy applications. It is also a CNCF Sandbox project, and the repository carries an ADOPTERS.md and a best-practices badge reference.

The two statements point in different directions. Years of production use is a signal about stability, while Sandbox status is a statement about the project's standing inside the CNCF, and neither replaces testing on your cluster. The thousands-of-projects figure has no named source in the text. The last push was on 2026-11-02 and the project is not archived. Check ADOPTERS.md for organisations like yours before you decide how much weight to give the usage claim.

Editorial conclusion

werf suits teams that deploy to Kubernetes from a CI system and want one tool to build from Dockerfiles, tag by content, deploy with Helm and clean the registry. It does not suit teams that deploy anywhere other than Kubernetes, or teams that want a hosted pipeline instead of a CLI. Before adopting it, choose a major line and a release channel on purpose, since v2 and v3 are both active, and check which channel label your tag carries.

Frequently asked questions

What does werf do?

werf is a CNCF Sandbox CLI tool for full-cycle CI/CD to Kubernetes. It builds and publishes container images, tests, deploys applications with Helm, distributes release artifacts and cleans up the container registry.

Which technologies does werf use?

werf relies on Git, Dockerfile, Helm and Buildah, and integrates into your CI system. Configuration is a Dockerfile and a Helm chart.

What do the labels in werf release titles mean?

Release titles carry channel labels in brackets. v3.12.1 is labelled ea, stable and rock-solid, while v3.12.2 is labelled alpha and beta and v2.84.1 is labelled alpha.

Official sources

  1. License: Apache-2.0
  2. Project website
  3. README
  4. Releases
  5. werf/werf on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/werf-werf.svg)](https://hysenlabs.com/projects/werf-werf)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/werf-werf.svg)](https://hysenlabs.com/projects/werf-werf)

Was this useful?