Self-hosted GitHub Actions fleets waste idle runner capacity
Teams operating self-hosted GitHub Actions runners report that jobs can land on overloaded hosts, while random assignment leaves machines idle and makes it hard to favor faster runners or reuse a smaller pool. They want more control over runner priority and warm capacity, and one operator reports duplicate webhook deliveries causing duplicate runner provisioning. GitHub’s assignment behavior and runner-management tooling leave these teams relying on custom orchestration and configuration rather than the controls they are requesting.
For teams operating self-hosted GitHub Actions runners. Mentioned from Feb 2022 to Dec 2025 on GitHub.
5 different people described this problem in 3 separate discussions.
- Indie fit
- 7.0/10
- Pain
- 7.5/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- Medium
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
This severely impacts our ability to scale GitHub Runners, costing literally tends of thousands monthly
gajus on GitHub (actions/runner)Feb 2022Right now, sometimes a congested VM will still pick up the job, and then oom
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 6 more quotes from people who have this problem
- Current workarounds, existing solutions and risks