Ross ROSS = Recommend OSS · open-source software intelligence for agents

werf

A solution for implementing efficient and consistent software delivery to Kubernetes facilitating best practices. observed · 2026-08-28

github.com/werf/werf · homepage · Go · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

94/100

  • Activity 99
  • Release rhythm 85
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 2.0
  • age_days: 3873
  • days_rel: 22
  • days_push: 7
  • n_releases_24m: 187

Full methodology

Adoption not part of the score

4717 stars · 238 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

werf is a CNCF Sandbox CLI tool that implements full-cycle CI/CD for Kubernetes, integrating with your CI system to build, publish, test, and deploy container images using Git, Dockerfile, Helm, and Buildah. It provides deterministic, reproducible delivery with features like content-based tagging, incremental builds, enhanced Helm resource tracking, and automated container registry cleanup.

Use cases

  • deploy applications to kubernetes from ci
  • build and publish docker images in a ci pipeline
  • gitops delivery to kubernetes
  • clean up unused images in a container registry
  • manage helm deployments with better resource tracking
  • reproducible container image builds from git
  • ci/cd for monorepo with multiple services
  • implement infrastructure as code for kubernetes delivery

When to choose

  • you want an all-in-one build-and-deploy tool for Kubernetes that glues Git, Dockerfile, Helm, and Buildah
  • you need deterministic, reproducible CI/CD with Git as the single source of truth (giterminism)
  • you want automatic build caching, content-based tagging, and registry cleanup out of the box
  • you deploy from a monorepo and need independent image tagging per component
  • you want a production-proven tool (used since 2017) with CNCF Sandbox backing

When to avoid

  • you deploy to non-Kubernetes targets like VMs or serverless platforms
  • you already have a mature pipeline with separate tools (e.g., plain Docker + Helm + Argo CD) and don't want to migrate
  • you need a GUI or dashboard-driven delivery platform rather than a CLI
  • your team is unwilling to adopt werf.yaml configuration and the giterminism workflow

Facets

cli-tool · maturity stable

deployment build-tool container-runtime ci-cd infrastructure-as-code developer-tools cloud-computing infrastructure-as-code developer-tools windows cli cloud go kubernetes helm gitops dockerfile buildah giterminism container-registry cncf-sandbox continuous-delivery image-cleanup devops containers automation linux macos docker

5 sources

Member repositories

RepositoryRoleHealth v2
werf/werfmain94
werf/nelmbackend91

For agents

markdown · JSON · MCP: product_card(name="werf/werf")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem