Jenkins is a popular choice for continuous integration and continuous delivery (CI/CD) due to its flexibility and vast plugin ecosystem, making it a cost-effective option for small teams with simple needs. However, as organizations scale, maintaining Jenkins becomes increasingly challenging and resource-intensive. Users often encounter issues such as unstable builds, significant time lost to server and plugin maintenance, and infrastructure costs that escalate with growth. These challenges can divert top engineers from core product work to manage Jenkins, leading to opportunity costs and potential burnout. Despite being free, Jenkins can incur hidden costs in terms of downtime, maintenance burdens, and infrastructure expenses, which may outweigh the benefits for larger teams. This has led some organizations, like Faire and Uber, to transition to alternative CI/CD platforms like Buildkite, which offer better scalability and reduced maintenance overhead.