Depot github actions runners are ephemeral, single-tenant EC2 instances that Depot launches from a standby pool when GitHub sends it a webhook, runs one job on GitHub's own runner image, and terminates. You adopt them by changing runs-on to a depot- label; what changes underneath is the hardware, a cache that is shared across branches, and a billing model that tracks by the second and multiplies by machine size.
Depot bills elapsed minutes multiplied by a size multiplier, so a plan allowance is spent at the size of the machine. Multipliers and rates read from depot.dev on 20 September 2026.
Depot sells build acceleration in four shapes: remote container builds, these GitHub Actions runners, its own CI sandboxes, and the cache and registry underneath them. The runners are the part that needs no new mental model, because the orchestration, the logs and the actions are still GitHub Actions.
Everything here was read from depot.dev on 20 September 2026 and is dated on the page.…