When considering self-hosting CI/CD runners, teams should weigh their options carefully due to the potential complexity and hidden costs involved. While self-hosting can appear to offer cost savings on compute, it often overlooks the operational overhead such as infrastructure management, Kubernetes expertise, and ongoing maintenance. Teams might consider self-hosting due to budget scrutiny, customization needs, performance bottlenecks, security constraints, or existing infrastructure challenges. However, the decision involves understanding the full scope, including scaling challenges, operational burdens, and whether the team has the necessary expertise and resources. Self-hosting tends to make sense for teams with significant scale and capabilities, whereas optimizing existing cloud setups often delivers faster results with less risk. A hybrid approach, using both cloud and self-hosted runners, can sometimes offer the best balance of control and complexity.