Argo Rollouts vs PipeCD
Argo Rollouts
argoproj.github.ioPipeCD
pipecd.devSide by side
| Figure | Argo Rollouts | PipeCD |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Web | — | Yes |
| Windows | Yes | — |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Progressive Delivery Software | 9.0 (#1) | 8.4 (#8) |
| Spec score · Continuous Delivery Software | 8.9 (#2) | 8.3 (#13) |
| Spec score · Kubernetes Deployment Tools | 8.9 (#2) | 8.4 (#8) |
| Automation | Rollouts can perform automated promotions and rollbacks based on metric analysis, alongside manual judgement. | PipeCD can automatically roll back after an analysis or pipeline-stage failure, detect configuration drift and trigger deployments from defined events. |
| Integrations | Documented integrations include NGINX, AWS ALB, Apache APISIX, Istio, Linkerd, SMI, Prometheus, Datadog, New Relic, Graphite, and InfluxDB. | Analysis providers include Prometheus, Datadog and Stackdriver, while notifications can be sent to Slack or webhook endpoints. |
| Notifications | The Notifications Engine supports configurable triggers and templates, including integrations such as Slack and Microsoft Teams. | Deployment notifications can be sent to Slack and webhook endpoints. |
| Security | The project documents cosign verification of signed container images and SLSA Level 3 provenance for container image attestations. | PipeCD supports single sign-on and role-based access control, keeps credentials out of the control plane and makes only outbound requests from piped. |
Plans
In their own words
Argo Rollouts
Argo Rollouts is a self-hosted Kubernetes controller for managing how application updates reach users. It supports BlueGreen, Canary and Rolling Update strategies, with weighted traffic shifting through ingress controllers or service meshes. Without a traffic-routing provider, it can adjust ReplicaSet counts instead. Metric integrations let it assess KPIs and automate promotion or rollback, while leaving room for manual judgment. Supported providers include NGINX, AWS ALB, Istio and Traefik for traffic, and Prometheus, Datadog, New Relic, Graphite and InfluxDB for metrics. It can operate independently of Argo CD and respond to Kubernetes manifest changes whether they come from GitOps or traditional CI/CD. Each cluster running Rollout workloads needs its own controller and CRD; a Rollout specification covers one application, not dependencies among applications. Shared-resource or worker-queue applications may be a poor fit, and infrastructure applications are not recommended. Argo Rollouts is free and open source. It runs on Linux, macOS, Windows or self-hosted environments.
PipeCD
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.