A unified GitOps continuous delivery platform for multi-cloud applications including Kubernetes, Terraform, Cloud Run, Lambda, and ECS.
PipeCD is a GitOps-style continuous delivery platform that provides a consistent deployment and operations experience for applications across multiple platforms and clouds. It enables engineers to deploy faster with more confidence by managing deployment operations through pull requests on Git. The platform supports Kubernetes, Terraform, GCP Cloud Run, AWS Lambda, and AWS ECS applications with a unified interface.
DevOps engineers and platform teams managing deployments across hybrid or multi-cloud environments, particularly those seeking a unified GitOps solution for diverse application types. It is also suitable for organizations scaling from small projects to thousands of cross-platform applications.
Developers choose PipeCD for its unified pipeline definition that works across multiple platforms without requiring changes to CRDs or application manifests, ensuring simplicity and consistency. Its security-first design, built-in deployment analysis, and delivery insights provide confidence and measurable performance improvements in deployment workflows.
The One CD for All {applications, platforms, operations}
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides the same deployment interface for Kubernetes, Terraform, GCP Cloud Run, AWS Lambda, and AWS ECS, simplifying management across heterogeneous environments as highlighted in the README.
Keeps deployment credentials within the application cluster, preventing exposure outside and enhancing security, a key feature emphasized in the project description.
Integrates analysis into the pipeline to measure impact based on metrics, logs, and emitted requests, helping teams deploy with more confidence as per the README.
Designed to manage thousands of cross-platform applications in multi-cloud environments, making it suitable for large-scale deployments while also working for small projects.
Requires configuring multiple components as detailed in the installation guide, which can be more involved than simpler, platform-specific CD tools.
Relies entirely on Git-based workflows and pull requests for deployments, which may not fit teams preferring other triggering mechanisms or with non-Git systems.
As a CNCF Sandbox project, it has a smaller community and fewer third-party integrations compared to more established alternatives like Jenkins or ArgoCD.