Meltwater, facing challenges with its Jenkins-based Continuous Integration (CI) system, transitioned to Harness CI to support its Kubernetes migration and improve developer adoption, which increased threefold to 222 developers. The switch to Harness CI resulted in a rise in repo automation from 60% to 75% and significantly reduced cloud infrastructure costs through autoscaling. The simplicity and flexibility of Harness CI, allowing for both simple and complex pipeline creation, contributed to its acceptance as the standard for CI best practices within the organization. The transition addressed security concerns associated with externally exposed APIs in tools like Travis CI and CircleCI, while the open community support for Harness CI provided timely solutions for issues such as Docker's new rate limits.