PipeCD is an open-source, self-hosted continuous delivery platform that uses GitOps-style workflows to deploy and operate applications. Deployment operations run through Git pull requests, with one interface for Kubernetes, Terraform, GCP Cloud Run, AWS Lambda, AWS ECS, and other targets. A plugin architecture lets users add deployment support for custom applications or platforms. PipeCD says a pipeline definition and application manifests are needed, without changes to CRDs or application manifests. Built-in analysis evaluates deployment impact using metrics, logs, and emitted requests. The platform can roll back after an analysis or pipeline-stage failure, detect configuration drift, and trigger deployments from defined events. Its interface provides pipeline views, per-deployment logs, real-time application-state visualization, and delivery-performance insights. A Control Plane manages deployments centrally, while piped agents execute them through plugin binaries. Security features include single sign-on and role-based access control; credentials stay out of the control plane, and piped makes only outbound requests. For private Git repositories, piped requires an SSH key pair configured with the public key added to the repository. The project is released under the Apache 2.0 license.
Who it is for
PipeCD may suit teams seeking self-hosted delivery workflows across different deployment targets. Its Git-based operations, deployment analysis, and plugin architecture fit teams that need automated rollback or custom platform support.
What is good
- One interface supports several deployment targets.
- Can roll back after analysis or pipeline-stage failures.
- Detects configuration drift and defined deployment events.
- Supports single sign-on and role-based access control.
- Open source under the Apache 2.0 license.
What to know first
- Requires self-hosting on your infrastructure.
- Private Git repositories require SSH key setup.
- Help is directed to documentation, GitHub, and CNCF Slack.
Verdict
PipeCD brings Git-based deployments, analysis, visibility, and rollback into a self-hosted platform. Teams should account for operating its Control Plane and piped agents, and SSH setup for private repositories.
PipeCD plans and pricing
All plansCompared on GitOps tools
- Pipeline as code
- Yes
- Approval gates
- Yes
- Progressive delivery
- Yes
- Automated rollback
- Yes
- Deployment model
- self-hosted
