CDS (Continuous Delivery Service) review
A free, self-hosted workflow orchestrator for teams that want pipeline control in code.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
CDS (Continuous Delivery Service) is an open-source continuous delivery platform developed at OVH. It is designed for teams that need to define, run, and manage build, test, and deployment workflows through pipelines, stages, jobs, conditional branches, and approval gates. Workflows can be managed in a web interface or through the command line, while REST APIs support workflow, pipeline, and rollback operations. Its self-hosted model suits engineering organizations that want control over their delivery environment and pipeline code.
The published model is completely free and open source, with no paid tier structure to compare. Teams can store and version workflows in Git repositories, select worker requirements for job execution, and pass artifacts between jobs and workflow runs. The platform connects with GitHub, GitLab, and Bitbucket Server, and supports deployment integrations including Kubernetes, OpenStack, Docker Swarm, and VMware vSphere. PostgreSQL and Redis are part of the self-hosted installation requirements, while S3, Swift, and WebDAV are available for storage integrations.
CDS stands out for workflow orchestration rather than specialized progressive delivery. Conditional branching, concurrent jobs, automatic or manual deployment conditions, configurable reviewers, and reviewer inputs give teams control over complex delivery paths. Artifact and log handling add operational structure across workflow runs. However, teams seeking canary or blue-green delivery patterns, or automated rollback triggers, should choose a platform with those capabilities. CDS is a strong fit for organizations comfortable operating self-hosted infrastructure and managing delivery logic as code; it is less suitable for teams seeking a managed service or a narrow progressive-delivery tool.
CDS (Continuous Delivery Service) pros and cons
- Where it wins
- Conditional workflows with concurrent jobs and manual approval gates
- Pipeline definitions can be versioned as code in Git repositories
- Integrations span major repositories, deployment platforms, and storage services
- Where it doesn't
- Self-hosted installation requires services such as PostgreSQL and Redis
- Does not provide documented progressive delivery capabilities
- Does not provide documented automated rollback triggers
CDS (Continuous Delivery Service) fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update