GitHub Actions Runner Size Recommender

Stop guessing runner size. Answer three questions and get a right-sized recommendation - and the label to use.

Over-sized runners waste money; under-sized runners are slow or OOM. Tell us about your job to get a recommended size and the runs-on: label.

Workload

Parallelism (workers)

Memory-hungry?

Why right-sizing matters

You pay per minute regardless of how many cores a job actually uses. Matching size to workload is the simplest cost win - and on managed runners like Latchkey, the same size costs roughly a third of GitHub-hosted.

Related guides

GitHub Actions Cost Calculator - Estimate & Cut Your CI BillFree GitHub Actions cost calculator: enter your monthly CI minutes and runner size to see your current bill a… GitHub Actions Runner Cost Comparison by Size (2026)Per-minute and monthly cost of GitHub Actions runners by size, compared with Latchkey managed runners. See th… GitHub Larger Runners vs Managed Runners: Cost & SpeedGitHub larger runners vs third-party managed runners: per-minute cost, billing model, and speed. When bigger… CI Exit Code Lookup: What Does This Exit Code Mean?Instant lookup for CI/CD process exit codes - enter a code (137, 127, 143…) to see what it means, whether it…