Werf website screenshot

Werf

Werf is an open-source CNCF sandbox project providing a complete GitOps-based CI/CD solution for Kubernetes. It implements the full application delivery lifecycle — building images, managing dependencies, deploying Helm charts, and cleaning up container registries — using Git as the single source of truth (Giterminism). Werf integrates natively with all major CI systems, Buildah, Helm, and Kubernetes.

Werf is profiled on the APIs.io network. Tagged areas include CI/CD, Deployment, DevOps, GitOps, and Kubernetes.

Werf’s developer surface includes documentation, getting-started guide, CLI, changelog, support, and 14 more developer resources.

24.5/100 emerging ▬ flat Agent 0/100 human only self hosted · Apache-2.0 Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
0 APIs 7 Features 5 Use Cases
CI/CDDeploymentDevOpsGitOpsKubernetesCNCFHelmContainersOpen-Source

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 90 points between them, because the conditional facet above carries the other 10. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 90% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/werf: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Features 7

Notable capabilities this provider offers.

Giterminism

Uses Git as the single source of truth, ensuring all CI/CD configurations are reproducible and auditable from version control.

Incremental Builds

Rebuilds only modified components and reuses existing container registry layers, dramatically reducing build times.

Kubernetes Deployment

Manages Helm chart deployments to Kubernetes with built-in rollback, planning, and drift detection (werf converge, werf plan, werf rollback).

Container Registry Cleanup

Automatically cleans up stale images from container registries using Git history-aware policies (werf cleanup, werf purge).

Helm Integration

Full Helm chart management including rendering, linting, bundling, and deploying with werf helm command suite.

Multi-CI Support

Native integration with GitHub Actions, GitLab CI, CircleCI, Jenkins, and other CI systems via werf ci-env.

Secure Software Delivery

TRDL component provides TUF-based secure software update distribution with GPG signature verification.

Scroll for all 7

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Werf Domain Security

TLSv1.3

SECURITY

Use Cases 5

What developers build with this provider.

Kubernetes Application Delivery

Build, test, and deploy containerized applications to Kubernetes clusters using GitOps principles.

Monorepo CI/CD

Manage CI/CD pipelines for monorepo projects with independent image tagging and selective component redeployment.

Helm Chart Management

Package, bundle, and deploy Helm charts with integrated dependency management and Kubernetes compatibility checks.

Container Registry Management

Automate container image lifecycle from build to cleanup using content-based tagging and Git-aware retention policies.

Secure Software Distribution

Distribute software updates securely using TUF framework with TRDL, ensuring integrity and authenticity of delivered artifacts.

Integrations 7

Pre-built integrations with other platforms and tools.

GitHub Actions

Native GitHub Actions for incorporating werf into GitHub-hosted CI/CD pipelines.

GitLab CI

First-class support for GitLab CI/CD environment variables and pipeline integration.

Helm

Deep integration with Helm package manager for Kubernetes, extending it with werf-specific deployment guarantees.

Buildah

Uses Buildah for rootless, daemonless OCI image builds without requiring Docker.

Kubernetes

Direct integration with Kubernetes API for deploying, monitoring, and managing application resources.

OCI Registries

Compatible with all OCI-compliant container registries including Docker Hub, GHCR, GitLab Registry, and cloud registries.

CNCF Ecosystem

CNCF Sandbox project integrating with the broader cloud-native ecosystem including Flux CD and other CNCF tools.

Scroll for all 7

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Build 9

SDKs, sample code, and the tooling you integrate with

Scroll for all 9

Access & Security 2

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: werf
deliveryModel:
  model: self-hosted
  license: Apache-2.0
  open_source: true
  commercial: false
  callable_host: false
  label: Self-hosted open source · you run it yourself
  confidence: high
  source:
  - license
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/werf.png
name: Werf
description: Werf is an open-source CNCF sandbox project providing a complete GitOps-based CI/CD solution for Kubernetes.
  It implements the full application delivery lifecycle — building images, managing dependencies, deploying Helm charts, and
  cleaning up container registries — using Git as the single source of truth (Giterminism). Werf integrates natively with
  all major CI systems, Buildah, Helm, and Kubernetes.
type: Index
url: https://werf.io/
tags:
- CI/CD
- Deployment
- DevOps
- GitOps
- Kubernetes
- CNCF
- Helm
- Containers
- Open-Source
tags_raw:
- CI/CD
- Deployment
- DevOps
- GitOps
- Kubernetes
- CNCF
- Helm
- Containers
- Open Source
created: '2025'
modified: '2026-05-03'
specificationVersion: '0.23'
apis: []
common:
- type: IssueTracker
  url: https://github.com/werf/werf/issues
- type: SecurityPolicy
  url: https://github.com/werf/werf/blob/main/SECURITY.md
- type: CodeOfConduct
  url: https://github.com/werf/werf/blob/main/CODE_OF_CONDUCT.md
- type: ContributionGuide
  url: https://github.com/werf/werf/blob/main/CONTRIBUTING.md
- type: License
  name: Apache-2.0
  url: https://github.com/werf/werf/blob/main/LICENSE
- type: DomainSecurity
  url: security/werf-domain-security.yml
- type: Website
  url: https://werf.io/
- type: Documentation
  url: https://werf.io/docs/v2/
- type: GettingStarted
  url: https://werf.io/getting_started/
- type: GitHubOrganization
  url: https://github.com/werf
- type: GitHubRepository
  url: https://github.com/werf/werf
- type: CLI
  url: https://github.com/werf/werf
  title: Werf CLI
- type: GitHubRepository
  url: https://github.com/werf/nelm
  title: Nelm (Helm 4 Alternative)
- type: GitHubRepository
  url: https://github.com/werf/kubedog
  title: Kubedog Kubernetes Watch Library
- type: GitHubRepository
  url: https://github.com/werf/trdl
  title: TRDL Secure Software Delivery
- type: GitHubRepository
  url: https://github.com/werf/actions
  title: GitHub Actions Integration
- type: GitHubRepository
  url: https://github.com/werf/nelm-chart-ts-sdk
  title: Nelm Chart TypeScript SDK
- type: ChangeLog
  url: https://github.com/werf/werf/releases
- type: Support
  url: https://github.com/werf/werf/discussions
- type: Features
  data:
  - name: Giterminism
    description: Uses Git as the single source of truth, ensuring all CI/CD configurations are reproducible and auditable
      from version control.
  - name: Incremental Builds
    description: Rebuilds only modified components and reuses existing container registry layers, dramatically reducing build
      times.
  - name: Kubernetes Deployment
    description: Manages Helm chart deployments to Kubernetes with built-in rollback, planning, and drift detection (werf
      converge, werf plan, werf rollback).
  - name: Container Registry Cleanup
    description: Automatically cleans up stale images from container registries using Git history-aware policies (werf cleanup,
      werf purge).
  - name: Helm Integration
    description: Full Helm chart management including rendering, linting, bundling, and deploying with werf helm command suite.
  - name: Multi-CI Support
    description: Native integration with GitHub Actions, GitLab CI, CircleCI, Jenkins, and other CI systems via werf ci-env.
  - name: Secure Software Delivery
    description: TRDL component provides TUF-based secure software update distribution with GPG signature verification.
- type: UseCases
  data:
  - name: Kubernetes Application Delivery
    description: Build, test, and deploy containerized applications to Kubernetes clusters using GitOps principles.
  - name: Monorepo CI/CD
    description: Manage CI/CD pipelines for monorepo projects with independent image tagging and selective component redeployment.
  - name: Helm Chart Management
    description: Package, bundle, and deploy Helm charts with integrated dependency management and Kubernetes compatibility
      checks.
  - name: Container Registry Management
    description: Automate container image lifecycle from build to cleanup using content-based tagging and Git-aware retention
      policies.
  - name: Secure Software Distribution
    description: Distribute software updates securely using TUF framework with TRDL, ensuring integrity and authenticity of
      delivered artifacts.
- type: Integrations
  data:
  - name: GitHub Actions
    description: Native GitHub Actions for incorporating werf into GitHub-hosted CI/CD pipelines.
  - name: GitLab CI
    description: First-class support for GitLab CI/CD environment variables and pipeline integration.
  - name: Helm
    description: Deep integration with Helm package manager for Kubernetes, extending it with werf-specific deployment guarantees.
  - name: Buildah
    description: Uses Buildah for rootless, daemonless OCI image builds without requiring Docker.
  - name: Kubernetes
    description: Direct integration with Kubernetes API for deploying, monitoring, and managing application resources.
  - name: OCI Registries
    description: Compatible with all OCI-compliant container registries including Docker Hub, GHCR, GitLab Registry, and cloud
      registries.
  - name: CNCF Ecosystem
    description: CNCF Sandbox project integrating with the broader cloud-native ecosystem including Flux CD and other CNCF
      tools.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/werf"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/werf/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/werf/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.