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.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Werf the way a machine reads it — 20 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Werf scores 15.6/100 (emerging), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Werf
Each block below is one kind of artifact we hold for Werf. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Features 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
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 within the panel for all 7 ·
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
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 tell you where this provider already fits in a stack.
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 within the panel for all 7 ·
Resources
Every other property we hold for Werf — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Build 8
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 8 ·
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/werf · machine-readable index on apis.io