What Is the Continuous Delivery Market?

Continuous Delivery (CD) is the engineering practice of automating the release pipeline so that software can be deployed to production safely, quickly, and sustainably at any time. The tooling and platform market that supports CD has grown significantly alongside the broader DevOps movement, driven by enterprises’ need to shorten release cycles, reduce deployment risk, and respond faster to customer feedback.

The global CD market encompasses standalone CD platforms, CI/CD suites, and cloud-native pipeline services. Adoption spans on-premises deployments—common in regulated industries—and cloud-hosted or SaaS models favoured by digital-native organisations.

Key Vendors in the Continuous Delivery Space

The following vendors are frequently cited as significant participants in the CD tooling ecosystem. Each takes a somewhat different approach to pipeline automation, release orchestration, and integration with broader DevOps toolchains.

• Atlassian – Offers Bitbucket Pipelines and integrates tightly with Jira and Bamboo for end-to-end traceability from issue to deployment.
• IBM – Provides CD capabilities through IBM DevOps (formerly UrbanCode Deploy), targeting enterprise release automation at scale.
• XebiaLabs (now Digital.ai) – Known for XL Release and XL Deploy, focused on enterprise release orchestration and compliance-heavy environments.
• CA Technologies (now Broadcom) – Delivers release automation tooling aimed at large enterprise IT operations.
• Electric Cloud (now CloudBees) – Specialised in pipeline orchestration and analytics; merged into the CloudBees portfolio.
• Puppet Enterprise – Approaches CD through infrastructure-as-code and configuration management, enabling consistent environment provisioning alongside application delivery.
• Chef Software (now Progress Chef) – Similar infrastructure-automation focus, with InSpec for compliance and Habitat for application packaging.
• CloudBees – Offers the CloudBees CI/CD platform built on Jenkins, targeting enterprise-grade pipeline management and governance.
• Microsoft – Azure DevOps (formerly VSTS) provides integrated pipelines, artifact management, and release gates tightly coupled with the Azure cloud.
• Flexagon – Provides FlexDeploy, a release automation and DevOps platform with strong Oracle technology support.
• Micro Focus – Offers release management and deployment automation through its ALM and ValueEdge portfolios.
• Clarive – A DevOps platform combining pipeline orchestration, configuration management, and service management in a single interface.

Deployment Models

CD platforms are generally available in two deployment models, each with distinct trade-offs:

On-Premises

On-premises deployments give organisations full control over their pipeline infrastructure, audit logs, and data residency. This model is common in regulated sectors such as banking, healthcare, and government, where data sovereignty and compliance requirements restrict the use of external SaaS services.

Cloud / SaaS

Cloud-hosted CD platforms reduce infrastructure overhead and accelerate onboarding. Managed services handle scaling, upgrades, and high availability, making this model attractive for startups and enterprises undergoing cloud migration. Hybrid approaches—where the control plane is cloud-hosted but agents run on-premises—are increasingly common.

Industry Verticals Adopting Continuous Delivery

CD adoption is no longer confined to software product companies. The following verticals are increasingly standardising on automated release pipelines:

• Banking, Financial Services, and Insurance (BFSI) – Driven by digital banking initiatives and regulatory pressure to audit every change, BFSI organisations invest heavily in release governance and automated compliance checks within CD pipelines.
• Telecommunications – Network function virtualisation (NFV) and 5G rollouts require rapid, reliable software updates across distributed infrastructure.
• Media and Entertainment – Streaming platforms and content delivery services rely on frequent deployments to add features and address performance issues without service interruption.
• Retail and eCommerce – Seasonal traffic peaks and competitive pressure demand the ability to release pricing, recommendation, and checkout changes multiple times per day.
• Healthcare – Electronic health record systems and patient-facing applications must balance rapid iteration with strict validation and regulatory requirements (e.g., FDA software guidance).
• Manufacturing – Industrial IoT and smart factory initiatives introduce software update requirements for embedded systems and edge devices.
• Education – EdTech platforms adopt CD to iterate quickly on learning management systems and student-facing applications.
• Government, Transport and Logistics, Energy and Utilities – These sectors are earlier in their CD adoption curve but are accelerating due to digital transformation mandates and operational efficiency goals.

Market Drivers

Several technology and business forces are accelerating investment in CD tooling:

• DevOps cultural adoption – As organisations break down silos between development and operations, CD becomes the operational backbone of the DevOps model.
• Microservices and containerisation – Kubernetes-based architectures multiply the number of independently deployable components, making manual release coordination infeasible and CD automation essential.
• Feature flag and progressive delivery practices – Decoupling deployment from release using feature flags reduces risk and increases deployment frequency, both of which require mature CD infrastructure.
• Security and compliance requirements – Shifting security left and embedding policy-as-code gates into pipelines turns CD platforms into compliance enforcement points.
• Cloud-native development – GitOps patterns and tools like Argo CD and Flux bring declarative, audit-friendly delivery directly into Kubernetes clusters.

Market Restraints and Challenges

Despite strong growth, several factors limit or slow CD adoption:

• Organisational and cultural resistance – Moving to automated releases requires process changes and trust in automated testing that many teams are not yet ready for.
• Legacy system integration – Mainframes, monolithic applications, and long-lived release trains are difficult to fit into CD models without significant re-architecting.
• Test automation maturity – CD depends on a comprehensive automated test suite. Organisations with low test coverage cannot safely increase deployment frequency without incurring higher production defect rates.
• Toolchain fragmentation – The breadth of CD-adjacent tooling (source control, artifact management, secrets management, observability) creates integration complexity and increases total cost of ownership.

Evaluating a CD Platform: What to Look For

When selecting a CD platform or suite, engineering teams should assess the following dimensions:

1. Pipeline-as-code support – Can pipelines be version-controlled alongside application code (e.g., Jenkinsfile, YAML-based DSLs)?
2. Integration breadth – Does the platform integrate natively with your existing source control, ticketing, artifact registry, and cloud provider?
3. Approval and governance gates – Does it support manual approval steps, environment-specific policies, and audit trails required for regulated industries?
4. Observability and feedback loops – Can deployment events be correlated with monitoring and alerting data to support automated rollback decisions?
5. Scalability – Can the platform handle the number of pipelines, parallel jobs, and deployment targets your organisation requires without becoming a bottleneck?
6. Security model – Does it support role-based access control, secrets management integration, and signed artifact verification?

Summary

The Continuous Delivery market is a mature but still-evolving segment of the DevOps toolchain ecosystem. Enterprise demand is being shaped by cloud-native architectures, compliance requirements, and the competitive pressure to ship software faster with fewer defects. Vendors range from broad DevOps platform providers like Microsoft and Atlassian to specialised release orchestration tools targeting regulated industries. Understanding your deployment model requirements, existing toolchain, and organisational maturity is the essential first step before evaluating specific platforms.

Puppet and its enterprise customers are in the same boat, afloat through the early phases of support for Docker containers.

Puppet introduced products and updates this week, which include new support for containers to help enterprise customers advance to the new technology.

For sophisticated IT shops where containers are already in use, configuration management can be seen as passé. In such bleeding-edge environments, container infrastructures are immutable — destroyed and recreated continually — rather than updated with tools such as Puppet or Chef.

But configuration management tools remain relevant to environments where infrastructure is patched and updated while it mostly remains in place over time, which is still the norm among large enterprises.

“There’s still a huge opportunity for Puppet to go into existing customers and help them get DevOps in place,” said Fintan Ryan, analyst with RedMonk, based in Portland, Maine. “The whole space is still just a bit messy.”

Still, the Puppet tools remain a work in progress with the first release. For example, DevOps shops tend to insist on tools that offer APIs and plug in to broader application management frameworks. Puppet has an API for its new container inspection product in the works, but it won’t be available in the first release this month.

Puppet IT automation embarks on a container journey

Puppet will add support for Linux package inspection within Docker containers with the first release of a tool, called Lumogon, due out in May.

Most of Puppet’s large enterprise customers have just started to experiment with containers and still wrestle with laying the groundwork with an automated VM infrastructure first.

“Configuration management isn’t going away — you have to run containers somewhere, and those systems have to be managed,” said Keiran Sweet, a consultant with Sourced Group, a Sydney-based managed services firm that works with large enterprises in Australia and Canada. Puppet’s Docker Image Builder may be used by customers to convert server images to container images, he added.

As clients get comfortable with containers, Puppet is in a similar phase. Lumogon is a “minimum viable product” in this month’s release, said Omri Gazitt, the chief product officer at Puppet, based in Portland, Ore.

The first release will use a command-line interface (CLI), and the data Lumogon collects will be fed into the monitoring tool of the customer’s choice. A query interface is planned for subsequent releases, and the Puppet roadmap for Lumogon also includes data collection from container networks and container orchestration tools, such as Docker Swarm, Kubernetes and Apache Mesos.

Puppet has no time to waste — these are features a crop of startups already offer to enterprises. Other configuration management tools, such as Chef and Ansible, have also established more appeal thus far in enterprise DevOps shops, analysts said.

Chef’s Automate product and Ansible’s new integrations with popular Red Hat tools, such as CloudForms, make them formidable opponents for Puppet in shops where people want to use established configuration management tools for containers, said Rob Stroud, an analyst at Forrester Research.

Puppet IT automation puts a new face on orchestration workflow

Puppet Enterprise 2017.2, also available from Puppet this week, includes a new visual interface. It’s a welcome addition for mainstream companies that already use Puppet, and it reflects a recent trend of GUIs for open source software automation tools.

Puppet Application Orchestration, now integrated with the Puppet Enterprise GUI, was accessed through a CLI when it was first introduced in 2015. Now, enterprises can manage orchestration features with visual tools, such as drop-down menus and filters.

“This gives you visibility into things that are running, things that have been successful and things that have failed,” Sweet said. “That will make [application orchestration] adoption easier.”

Linux package inspection for known security vulnerabilities, another new feature available in Puppet Enterprise 2017.2, is of interest for enterprises, as well. Separate tools such as those from Black Duck Software in Burlington, Mass., can scan open source software packages, but some users prefer to have this feature natively available.

“If I’m going to do a package update [in response to a vulnerability], I’m going to use Puppet to do it,” said Rob Nelson, a Puppet user at a large enterprise that he asked to not be named. “It’s nice to be able to do both in the same spot.”

Nelson has experience with Puppet’s CLI, but he said the GUI will be a useful visual record of what’s been changed recently in the environment.

Later this month, Puppet will also introduce a visualization software-as-a-service offering, Puppet Cloud Discovery, which offers a view into Amazon Web Services Elastic Compute Cloud instance inventories. The company said it plans to add support for more public cloud providers in future releases.