# pipe-cd/pipecd

The One CD for All {applications, platforms, operations}

Repository: https://github.com/pipe-cd/pipecd
Canonical: https://ross.abutalabs.com/products/pipecd
Homepage: https://pipecd.dev
Language: Go
License: Apache-2.0
License Family: permissive
Topics: kubernetes, terraform, serverless, gitops, infrastructure, istio, ecs, lambda, cloudrun, continuous-delivery, fargate, cd, cncf, devops, ci-cd, cicd, pipecd, cncf-project, sandbox
Last push: 2026-08-26T15:07:35+00:00

## Health v2 (maintenance only)
Score: 99/100 (v2, computed 2026-09-02T17:46:02.011165+00:00)
- activity 99, release rhythm 99, longevity 100
- inputs: {"age_days": 2273, "days_push": 7, "days_rel": 10, "gap_med": 14.0, "n_releases_24m": 29}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1346, forks 357 (observed 2026-08-28T04:04:27.421416+00:00)

## What it is
PipeCD is a GitOps-style continuous delivery platform that provides a unified deployment and operations experience for applications across Kubernetes, Terraform, AWS Lambda, ECS, and Cloud Run. It consists of a self-hosted control plane and a piped agent that runs inside your cluster, enabling pull-request-driven deployments with built-in analysis and automated rollback.

## Use cases
- deploy kubernetes applications via gitops pull requests
- unified continuous delivery across kubernetes, terraform, lambda, ecs and cloud run
- automated canary deployment analysis with metrics and logs
- automatically roll back deployments when analysis fails
- detect configuration drift in deployed applications
- self-hosted CD platform with SSO and RBAC
- multi-cluster multi-tenant deployment management

## When to choose
- you need one CD tool for multiple application kinds and clouds
- you want GitOps deployments driven by pull requests without CRDs
- you need built-in deployment analysis and automatic rollback
- you want deployment credentials kept inside your cluster

## When to avoid
- you only deploy to a single Kubernetes cluster and prefer a lighter tool like Argo CD or Flux
- you need a fully managed SaaS CD rather than self-hosting a control plane
- your team relies on CI tools to handle deployment steps PipeCD would own

## Facets
- artifact type: service
- maturity: active
- function: deployment, ci-cd, infrastructure-as-code, monitoring, secrets-management, workflow-automation
- domain: cloud-computing, infrastructure-as-code, self-hosted
- platform: cloud, self-hosted, go
- tags: gitops, continuous-delivery, cd, multi-cloud, terraform, aws-lambda, ecs, cloud-run, cncf-sandbox, deployment-analysis, automated-rollback, drift-detection, devops, containers, kubernetes, docker

## Member repositories
- pipe-cd/pipecd (main) score 99

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:27.421416+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:42:42.581452+00:00, confidence not recorded.
  - readme: https://github.com/pipe-cd/pipecd (fetched 2026-08-28T04:04:27.421416+00:00, sha e3413e4904e9)
  - homepage: https://pipecd.dev (fetched 2026-08-29T12:01:49.831357+00:00, sha 11af419b4cf3)
  - site_page: https://pipecd.dev/docs (fetched 2026-08-29T12:01:49.841040+00:00, sha 5554f203cd1a)
  - site_page: https://pipecd.dev/docs/quickstart (fetched 2026-08-29T12:01:49.853955+00:00, sha 54151488d741)
  - site_page: https://pipecd.dev/docs-v1.0.x (fetched 2026-08-29T12:01:49.867752+00:00, sha 3d6c30b15124)
  - site_page: https://pipecd.dev/docs/contribution-guidelines (fetched 2026-08-29T12:01:49.870673+00:00, sha 7d90f153fed2)
- Data as of 2026-08-30T08:39:29.467469+00:00.