How would you define the success of CircleCI's self-hosted runners offering?

Introduction

Defining the success of CircleCI's self-hosted runners offering requires a comprehensive approach to product success metrics. To address this challenge effectively, I'll follow a structured framework that covers core metrics, supporting indicators, and risk factors while considering all key stakeholders.

Step 1

Product Context

CircleCI's self-hosted runners offering is a feature that allows customers to run CI/CD jobs on their own infrastructure while still leveraging CircleCI's cloud-based orchestration. This product caters to organizations with specific security, compliance, or resource requirements that necessitate keeping workloads within their own environments.

Key stakeholders include:

1. Enterprise customers: Seeking enhanced control and security
2. DevOps teams: Looking for flexibility in CI/CD infrastructure
3. Security and compliance officers: Ensuring data and processes meet regulatory standards
4. CircleCI product team: Aiming to expand market share and increase customer satisfaction

User flow:

1. Setup: Customers install and configure self-hosted runners in their environment
2. Integration: Teams integrate runners with their existing CircleCI workflows
3. Execution: Jobs are dispatched to self-hosted runners as needed, with results reported back to CircleCI

This offering fits into CircleCI's broader strategy of providing flexible, scalable CI/CD solutions that cater to diverse customer needs. It competes with similar offerings from GitHub Actions and GitLab, but differentiates through CircleCI's robust cloud orchestration and extensive integrations.

Product Lifecycle Stage: Early Growth - The self-hosted runners feature has moved beyond initial launch and is gaining traction, but still has significant room for expansion and refinement.

Software-specific context:

• Platform: Compatible with major cloud providers and on-premises infrastructure
• Integration points: CircleCI cloud orchestration, version control systems, and customer CI/CD pipelines
• Deployment model: Hybrid, combining cloud-based control plane with on-premises execution