Depot Runner Labels Reference: All runs-on Names
A quick reference to Depot's documented runs-on label families across Intel, ARM, Windows, and macOS, so you can pick the right one for a job.
Depot runners are selected entirely by the runs-on label, so getting the label right is most of the setup. This page collects the documented label families from depot.dev/docs/github-actions/runner-types. Always confirm exact labels and sizes there, since product details change.
How to read the labels
The base label picks OS and architecture; the numeric suffix picks CPU count (up to 64 on Linux and Windows). Per Depot's docs, Intel runners use 4th Gen AMD EPYC Genoa CPUs and ARM runners use AWS Graviton4. macOS labels are fixed size (8 CPUs, 24 GB). Use a single label, not an array.
GPU labels are configured, not fixed
Per Depot's blog, GPU runs-on labels map to GPU resource classes you configure in your AWS account via Depot Managed, and GPU is a Business-plan feature. So GPU label names are specific to your setup rather than a fixed public list.
When the real problem is flaky failures, not setup
If your Depot jobs are picked up and fast but still fail intermittently on out-of-memory kills, disk-full errors, or registry timeouts, no runner-speed tuning removes that class of failure. Latchkey is also a drop-in managed runner reached by a runs-on label swap, but it is built around self-healing CI: it detects, diagnoses, fixes, and retries transient and mechanical failures automatically, and lists up to 58% lower per-minute cost than GitHub Actions. If troubleshooting keeps landing on flaky re-runs, it is worth piloting one workflow on Latchkey next to Depot and comparing.