Skip to content
SPECIFICTION
Get listed

PipeCD

pipecd.dev

Free plan Open source WebmacOSLinuxAPISelf-hosted
Visit pipecd.dev
Spec score 8.5 #8 of 35 in GitOps Tools

What it is

PipeCD is a self-hosted continuous delivery platform that coordinates deployments through Git pull requests. Its shared deployment interface supports Kubernetes, Terraform, GCP Cloud Run, AWS Lambda, AWS ECS and other targets, while plugins let teams add custom applications or platforms. PipeCD says deployment setup needs a pipeline definition and application manifests, without changes to CRDs or application manifests. Built-in analysis assesses deployment impact with metrics, logs and emitted requests; the platform can roll back after analysis or pipeline-stage failures, detect configuration drift and launch deployments from defined events. Its UI presents deployment pipelines, per-deployment logs, live application state and delivery-performance insights. A centralized Control Plane works with piped agents that run deployments using plugin binaries. Security features include single sign-on and role-based access control, and credentials stay outside the Control Plane. PipeCD is open source under Apache 2.0 and costs nothing. For private Git repositories, piped needs a private SSH key and its corresponding public key added to the repository.

Spec sheet

What it does
PipeCD is a GitOps continuous-delivery platform intended to give one deployment and operations interface across applications and platforms.Read 15 Oct 2026 · pipecd.dev
Product
PipeCD is a GitOps-style continuous delivery platform for consistent deployment and operations across applications.Read 1 Oct 2026 · site.pipecd.dev
API
The control plane provides gRPC connectivity for piped agents and web/API endpoints for clients.Read 15 Oct 2026 · pipecd.dev
Integrations
Analysis providers include Prometheus, Datadog and Stackdriver, while notifications can be sent to Slack or webhook endpoints.Read 1 Oct 2026 · pipecd.dev
Security
PipeCD supports single sign-on and role-based access control, keeps credentials out of the control plane and makes only outbound requests from piped.Read 1 Oct 2026 · pipecd.dev
Support
The project directs users to documentation, GitHub issues and discussions, and the CNCF Slack #pipecd channel for help.Read 1 Oct 2026 · github.com
License
PipeCD is released as open source under Apache License 2.0.Read 15 Oct 2026 · site.pipecd.dev
Analysis integrations
Named analysis integrations include Prometheus, Datadog, Stackdriver and CloudWatch.Read 15 Oct 2026 · pipecd.dev
Architecture
The control plane is a web service exposing UI, API endpoints and metadata storage, while piped is a lightweight agent that runs plugins.Read 15 Oct 2026 · pipecd.dev
Automatic rollback
The product can stop a failed deployment and roll back to the preceding state.Read 15 Oct 2026 · pipecd.dev
Automation
PipeCD can automatically roll back after an analysis or pipeline-stage failure, detect configuration drift and trigger deployments from defined events.Read 1 Oct 2026 · pipecd.dev
CNCF code metrics
CNCF reports 176 GitHub stars, 239 forks and estimated software value of $17.7 million.Read 15 Oct 2026 · cncf.io
CNCF contributors
CNCF reports 494 contributors and 118 contributing organizations for PipeCD.Read 15 Oct 2026 · cncf.io
CNCF health score
The CNCF project page shows a health score marked Concerning (33).Read 15 Oct 2026 · cncf.io
CNCF project age
CNCF lists PipeCD's first commit as March 9, 2020.Read 15 Oct 2026 · cncf.io
CNCF status
CNCF accepted PipeCD as a Sandbox project on May 17, 2023.Read 15 Oct 2026 · cncf.io
Control-plane storage
The architecture supports managed or self-managed MySQL-compatible data storage and managed or self-managed object/file storage such as S3 or Minio.Read 15 Oct 2026 · pipecd.dev
Credential handling
PipeCD states that deployment credentials remain in the cluster and are not stored in the control plane.Read 15 Oct 2026 · pipecd.dev
Deployment analysis
PipeCD can evaluate deployments with metrics, logs and emitted requests through analysis providers.Read 15 Oct 2026 · pipecd.dev
Deployment targets
The same deployment interface supports Kubernetes, Terraform, GCP Cloud Run, AWS Lambda, AWS ECS and more.Read 1 Oct 2026 · pipecd.dev
Documentation
Documentation includes overview, concepts, quickstart, installation, user and contributor guides, examples, feature status, FAQ and release links.Read 15 Oct 2026 · pipecd.dev
Drift detection
PipeCD detects configuration drift and can notify users about changes.Read 15 Oct 2026 · pipecd.dev
Event triggers
Deployments can be triggered by events such as a container image push or Helm chart publication.Read 15 Oct 2026 · pipecd.dev
GitOps workflow
PipeCD enables deployment operations through pull requests on Git.Read 1 Oct 2026 · pipecd.dev
Installation prerequisite
Single-machine installation requires a registered piped identifier and key, plus an SSH key for private Git repositories.Read 15 Oct 2026 · site.pipecd.dev
Internal usage
CyberAgent reports PipeCD is used by more than 3,500 internal applications and supports thousands of deployments per day.Read 15 Oct 2026 · cyberagent.co.jp
Latest release
GitHub lists PipeCD v0.58.0 released on August 23, 2026.Read 15 Oct 2026 · github.com
Limit: API authorization granularity
An open GitHub issue requests API-key scopes beyond the existing READ_ONLY and READ_WRITE choices.Read 15 Oct 2026 · github.com
Limit: deployment interruption
An open GitHub issue reports that restarting piped during a stage cancels and rolls back the deployment.Read 15 Oct 2026 · github.com
Limit: plugin process reliability
An open GitHub issue reports that piped health can remain OK after a plugin process exits.Read 15 Oct 2026 · github.com
Limit: quickstart compatibility
An open GitHub issue reports legacy quickstart applications failing because no plugin is specified.Read 15 Oct 2026 · github.com
LinkedIn organization size
PipeCD's LinkedIn profile lists the organization as a nonprofit with 2–10 employees.Read 15 Oct 2026 · linkedin.com
Maker identity
CyberAgent describes PipeCD as an open-source continuous-delivery tool it developed and operates through its Developer Productivity organization.Read 15 Oct 2026 · cyberagent.co.jp
Manifest requirement
PipeCD says no CRD or application manifest changes are required; only a pipeline definition and application manifests are needed.Read 1 Oct 2026 · pipecd.dev
Multi-tenancy
Multi-cluster and multi-tenant operation is implemented by separating the control plane from piped agents.Read 15 Oct 2026 · pipecd.dev
Network model
The piped agent makes outbound requests only and can run in a restricted network.Read 15 Oct 2026 · pipecd.dev
Notifications
Deployment notifications can be sent to Slack and webhook endpoints.Read 15 Oct 2026 · pipecd.dev
Operational requirement
For private Git repositories, piped requires a private SSH key and the corresponding public key added to the repository.Read 1 Oct 2026 · site.pipecd.dev
Plugin architecture
PipeCD uses plugins so users can create plugins and deploy custom applications or platforms.Read 1 Oct 2026 · pipecd.dev
Plugin extensibility
Plugins are external binaries loaded by piped, and official plugins are versioned independently from PipeCD.Read 15 Oct 2026 · site.pipecd.dev
Plugin SDK
The official Go SDK supports stage, deployment, live-state and plan-preview plugin types; the setup guide requires Go 1.26 or newer and SDK version 0.4.0.Read 15 Oct 2026 · pipecd.dev
Praise: progressive delivery safety
CyberAgent highlights staged canary exposure, metric checks and immediate rollback as ways to reduce user impact from failed releases.Read 15 Oct 2026 · cyberagent.co.jp
Praise: unified multi-platform delivery
CyberAgent says PipeCD reduced learning and maintenance costs by providing one interface across heterogeneous deployment platforms.Read 15 Oct 2026 · cyberagent.co.jp
Progressive delivery
Deployment plugins provide canary and blue-green rollout modes for Kubernetes applications.Read 15 Oct 2026 · pipecd.dev
Project status
PipeCD is released as open source under the Apache 2.0 license.Read 1 Oct 2026 · pipecd.dev
Release changes
Version 0.58.0 added StatefulSet and DaemonSet configuration-hash annotations and fixed several plugin, rollback, Git worktree and panic defects.Read 15 Oct 2026 · github.com
Security controls
Official materials list single sign-on, role-based access control and built-in secrets management.Read 15 Oct 2026 · pipecd.dev
Self-hosting
Operators can install the control plane themselves and run piped as a Kubernetes pod, ECS container, serverless function or local process.Read 15 Oct 2026 · pipecd.dev
Supported application platforms
The documented platform providers are Kubernetes, Amazon ECS, Terraform, Google Cloud Run and AWS Lambda.Read 15 Oct 2026 · pipecd.dev
Visibility
The web interface includes pipeline status, per-deployment logs, real-time application state and delivery insights.Read 15 Oct 2026 · pipecd.dev

Plans and prices

Open source Free Apache 2.0 license Read 1 Oct 2026 · pipecd.dev

Every PipeCD plan and price →

Strong points and limits

Strong points

  • Supports Kubernetes, Terraform and cloud deployment targets
  • Plugin architecture supports custom applications and platforms
  • Analysis uses metrics, logs and emitted requests
  • Automated rollback and configuration-drift detection
  • Open source under Apache 2.0

Limits

  • Self-hosted deployment model
  • Private Git repositories require SSH key setup

Who it suits

PipeCD suits teams that want Git-based deployment operations across the listed infrastructure targets, with self-hosting and plugin support. It may also fit teams needing deployment analysis, approval gates or automated rollback.

Verdict

PipeCD combines Git-based deployment workflows with analysis, visibility and rollback automation. Its self-hosted architecture and private-repository key requirement are important setup considerations.

Where Specifiction places it

Alternatives to PipeCDAll alternatives →