CDS (Continuous Delivery Service)

CDS is a self-hosted, open-source platform for continuous delivery and DevOps automation. It fits engineering teams that want programmable pipelines, project-level delegation, and control over their delivery infrastructure. The central trade-off is clear: CDS is free software, but your organization owns deployment and ongoing operations.

Overview

CDS brings build, test, deployment, approvals, branching logic, and rollback into one workflow system. Pipeline-as-code and progressive-delivery support make it suitable for release processes that need repeatability, staged changes, or explicit recovery paths rather than a single linear job. Because the deployment model is self-hosted, teams retain control of the service and its data while taking responsibility for availability, upgrades, and security.

Installation guidance covers Docker Compose and binary setups. The Docker Compose tutorial is not a production-ready architecture by itself: production users should modify it before relying on that arrangement. CDS is therefore a better fit for organizations with infrastructure capability than for teams seeking a managed service with operations handled by a vendor.

Key features

Workflows can include builds, tests, deployments, manual or automatic gates, conditional branches, and rollback. Manual approvals help supervise sensitive releases; automatic gates and conditions support policy-driven promotion; rollback provides a defined response when a deployment must be reversed. Progressive delivery adds support for staged rollout strategies.

The web interface lets users assemble and run workflows and inspect execution logs. The cdsctl command-line client can script platform operations and browse projects and workflows, which is useful when administration and delivery tasks belong in repeatable automation rather than only in a browser.

Project users can manage pipelines and delegate access rights within their own projects. That project-level self-service can reduce bottlenecks around routine pipeline changes, while keeping access decisions closer to the teams that own the workloads.

Integrations span GitHub, GitLab, Bitbucket, Gerrit, Kubernetes, OpenStack, Kafka, RabbitMQ, LDAP, OpenID Connect, and Artifactory. Authentication supports local accounts, LDAP, GitHub, and GitLab backends, and multiple backends can be enabled together. Teams can create actions and extend CDS with plugins for custom actions, making the platform more adaptable when built-in workflow steps do not cover a process.

Pricing

CDS is completely free and open source. The CDS plan costs free and is described as an open-source platform for self-hosting. There are no paid tiers, seat charges, usage quotas, trial countdowns, or renewal terms presented for this plan. The saving comes with an operational cost instead: your team must provide and maintain the hosting environment, and the tutorial deployment requires modification before production use.

Platforms

CDS provides API and web access and can be hosted on Linux, macOS, or Windows. Workers are compatible with Linux, macOS, FreeBSD, and Windows on 386, amd64, arm, and arm64 architectures. That breadth helps organizations standardize delivery across mixed operating-system fleets, including teams that need non-x86 worker hardware.

Who it's for

Choose CDS if you need self-managed continuous delivery with pipeline-as-code, approval gates, progressive delivery, project-scoped permissions, and command-line automation. It is particularly compelling for organizations already operating infrastructure and for teams integrating several source-control, messaging, identity, artifact, or cloud platforms.

Look elsewhere if you want a hosted service, vendor-managed upgrades, or a production deployment that can be adopted without adapting the installation architecture. CDS’s free license does not remove the work of running the platform.

Pros and cons

Pros

• Broad workflow control: gates, conditions, rollback, and progressive delivery cover complex release policies.
• Project-level self-service: teams can manage pipelines and delegate rights without routing every change through central administrators.
• Extensible integration surface: many source, infrastructure, messaging, identity, and artifact connections are supported, with custom actions and plugins for additional needs.
• Wide worker compatibility: multiple operating systems and CPU architectures support heterogeneous build environments.
• No software charge: the self-hosted open-source plan is priced at 0.00 USD.

Cons

• Operational responsibility: hosting, maintenance, and production hardening remain with your organization.
• Not turnkey production deployment: the Docker Compose tutorial setup must be modified before production use.
• Self-hosting is mandatory: teams seeking a vendor-operated SaaS workflow service will need another product.

Alternatives

GoCD is another free, open-source continuous delivery server with downloadable installation when you want a comparable self-managed server.

Argo CD is the better choice for declarative GitOps delivery focused on Kubernetes through a self-managed installation.

Argo Rollouts suits teams that specifically need a Kubernetes controller and CRDs for rollout management.

Flux CD is an option for open-source Kubernetes delivery when you already have a Kubernetes cluster.

Codemagic fits teams wanting a freemium hosted build service with a free tier for one team member, monthly build minutes, one parallel build, and 30 days of history and artifact storage.

Appcircle is aimed at mobile-oriented delivery, with a free starter tier that limits concurrency, build duration, monthly builds, and CodePush updates.

Bitrise offers a freemium, free-forever hobby plan for a one-person team with small-project build credits.

KintoHub is a freemium alternative offering a free allowance for three small services, persistent data, and shared CPU.

Browse more options in Continuous Delivery Software.

Verdict

CDS is a strong choice for infrastructure-capable teams that want free, self-hosted delivery automation with complex workflow controls, delegated project administration, and broad integration and worker support. Choose it for control and extensibility; look elsewhere if you need a managed, production-ready service with minimal platform operations.