The State of CI/CD in 2026: Universal Adoption, Self-Hosting Resurgence, and AI's Peripheral Role

A recent report from JetBrains, based on extensive surveys including their CI/CD Tools Adoption Survey 2026, reveals several critical insights into the current state of Continuous Integration/Continuous Delivery. The most striking finding is the near-universal adoption of CI/CD practices, with 83.4% of developers now running pipelines. This surpasses containerization (50%) and infrastructure as code (39%), indicating that CI/CD has become a fundamental, expected practice rather than a competitive advantage. This widespread adoption signifies a maturation of the DevOps landscape. For practitioners, this means that the conversation has shifted from *whether* to adopt CI/CD to *how effectively* to implement and optimize it. The report also highlights a notable trend: a resurgence in self-hosted CI/CD approaches. On-premises CI/CD has reached a five-year high at 31%, and fully managed cloud CI has seen a seven-point decrease since its 2022 peak. Nearly three-quarters of developers now self-host their primary CI/CD tool in some form. This suggests a desire for greater control, customization, and potentially cost optimization over fully managed solutions. The broader trend in cloud and DevOps has always been a balance between convenience and control. While early cloud adoption pushed for fully managed services, the increasing complexity and scale of modern software development, coupled with growing concerns around vendor lock-in and specific compliance requirements, are driving organizations to reclaim more control over their critical infrastructure. This is particularly true for CI/CD, which is at the heart of the software delivery lifecycle. The report also touches upon the role of AI, noting that while roughly half of organizations use AI for some CI/CD tasks, only 8% actually run an AI step *inside* the build process itself. This indicates that AI's impact on CI/CD is currently more about peripheral tasks, such as code analysis or predictive analytics, rather than direct automation of the build and test stages. In practice, this means organizations should prioritize optimizing their existing CI/CD pipelines for efficiency, reliability, and security, rather than focusing on initial adoption. The move towards self-hosting implies a need for robust internal expertise in managing and securing these critical systems. Furthermore, while AI offers significant promise, practitioners should be pragmatic about its current capabilities within the core CI/CD pipeline. Instead of expecting AI to revolutionize build processes overnight, focus on leveraging it for tasks where it demonstrably adds value, such as intelligent test selection or anomaly detection. Teams should also consider toolchain consolidation, as the report indicates this is a top reason for switching tools, suggesting a desire for more integrated and streamlined workflows.