GitHub Actions

This page lists Depot GitHub Actions runner types and sizes. For Depot CI, see Depot CI sandboxes.

Depot offers several different types of GitHub Actions runners. You can choose the type on a per-job basis by specifying the runner label in your .github/workflows/*.yaml file:

jobs:
  build:
    runs-on: depot-ubuntu-24.04

Note: We support the depot-ubuntu-latest alias for the current Ubuntu Long-Term Support (LTS) release if you prefer to use an evergreen version.

In-memory Disk Accelerator

Depot Linux and macOS runners reserve a portion of the memory on the runner host for a disk accelerator, backed by a RAM disk. The accelerator acts as a buffer between reading and writing to the root disk, which allows Actions runs to perform incredibly fast I/O operations, much quicker than the physical disk would allow.

Intel runners

Intel runners use AMD EC2 instances. Their EBS volume is provisioned with 8000 IOPS and 250 MB/s throughput.

The following labels are available:

Arm runners

Arm runners use Graviton4 EC2 instances. Their EBS volume is provisioned with 8000 IOPS and 250 MB/s throughput.

The following labels are available:

Ubuntu 22.04 runners

These runners use the same instances as the Ubuntu 24.04 runners.

The following labels are available:

Windows runners

Windows runners use instances with Intel chips running Windows Server 2022 or Windows Server 2025.

Note: We support the depot-windows-latest if you prefer to use an evergreen version. This label is currently an alias for Windows Server 2025.

Windows Server 2025 runners

The following labels are available:

Windows Server 2022 runners

The following labels are available:

Note: Windows runners don't come equipped with Hyper-V because of an AWS limitation on EC2. Therefore, if you use things that require it like docker, then Depot Windows Runners are unlikely to work for you.

macOS runners

macOS runners use instances with M2 chips running macOS 14 or 15, or M4 chips running macOS 26. Their EBS volume is provisioned with 12000 IOPS and 1000 MB/s throughput. Like the Linux runners, the macOS runners also have a disk accelerator.

The following labels are available:

Note: due to licensing constraints from Apple, our macOS runner capacity is not fully elastic like our other runner types. We periodically update capacity to match demand, but macOS jobs can experience longer queue times during times of high demand.

Billing

Note that on your Billing summary, costs are broken down by Billed minutes and Elapsed minutes. Here are several things to know about the difference:

• Elapsed minutes is the clock time spent executing your jobs.
• Billed minutes multiplies the Minutes multiplier (from the table above) by the Elapsed minutes.
• The rate at which Billed minutes accumulates is based on the size of the Minutes multiplier.
• What you pay is the total Billed minutes minus the included minutes of your plan.

What software and tools are included?

If you'd like to see what tools and software are installed in each runner image, please see the links to the README in GitHub's repository:

• depot-ubuntu-24.04 and depot-ubuntu-latest
• depot-ubuntu-22.04
• depot-macos-26 and depot-macos-latest
• depot-macos-15
• depot-macos-14
• depot-windows-2025 and depot-windows-latest
• depot-windows-2022

Note: We do our best to keep our images in sync with GitHub's, but there may be a slight delay between when GitHub updates their images and when we update ours. If you need a specific version of a tool or software, please check the links above to see if it's available in the image you're using.

Custom runner images

If you need specific software pre-installed that isn't included in our standard runner images, custom runner AMIs are available on the Business plan. This is particularly useful for:

• Large dependencies that take significant time to install
• Proprietary software or custom configurations
• Corporate security or compliance tools

Contact us at contact@depot.dev to discuss custom runner image requirements.