Depot
  • Customers

  • Blog

  • Docs

  • Pricing

Get startedLog in

Announcing Depot Managed Agents and Sandboxes

Get Started
Get StartedManage Accounts
Using Depot
ObservabilityTroubleshootingEnvironment variablesAI and agent resourcesSecurityChangelog
Depot CI
OverviewQuickstart
Container Builds
OverviewQuickstartTroubleshootingBuild Parallelism
GitHub Actions Runners
OverviewQuickstartTroubleshootingRunner Types
Managed Agents
OverviewClaude CodeClaude Managed AgentsDevinOpenAI
Depot Sandboxes
OverviewSandbox SDK
Depot Cache
OverviewAuthentication
Depot Registry
OverviewQuickstartPull-through cache
Depot Code
OverviewQuickstart
Depot CLI
InstallationAuthentication
Depot API
OverviewAuthentication
Depot Managed
OverviewDepot Managed on AWSUsing GPUs
Edit on GitHub
Products
Depot RegistryDepot CodePricingCustomersSecurityDockerfile Explorer
Support
DocumentationHelpDiscord [118 online]System Status
Company
AboutCareersBlogNewsletterEventsChangelogMerchBrand Assets
Social Media
DiscordGitHubXYouTubeLinkedIn
Depot
Dark
Light
System
Language
© 2026 Depot Technologies Inc.Terms of ServicePrivacy PolicyCookies
    GitHub Actions

    Depot GitHub Actions runner types

    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 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:

    LabelCPUsMemoryDisk sizeDisk accelerator sizePer-minute priceMinutes multiplier
    depot-ubuntu-24.0428 GB100 GB2GB$0.0061x
    depot-ubuntu-24.04-4416 GB130 GB4GB$0.0122x
    depot-ubuntu-24.04-8832 GB150 GB8GB$0.0244x
    depot-ubuntu-24.04-161664 GB180 GB8GB$0.0488x
    depot-ubuntu-24.04-3232128 GB200 GB16GB$0.09616x
    depot-ubuntu-24.04-6464256 GB250 GB32GB$0.19232x

    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:

    LabelCPUsMemoryDisk sizeDisk accelerator sizePer-minute priceMinutes multiplier
    depot-ubuntu-24.04-arm28 GB100 GB2GB$0.0061x
    depot-ubuntu-24.04-arm-4416 GB130 GB4GB$0.0122x
    depot-ubuntu-24.04-arm-8832 GB150 GB8GB$0.0244x
    depot-ubuntu-24.04-arm-161664 GB180 GB8GB$0.0488x
    depot-ubuntu-24.04-arm-3232128 GB200 GB16GB$0.09616x
    depot-ubuntu-24.04-arm-6464256 GB250 GB32GB$0.19232x

    Ubuntu 22.04 runners

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

    The following labels are available:

    LabelCPUsMemoryDisk sizeDisk accelerator sizePer-minute priceMinutes multiplier
    depot-ubuntu-22.0428 GB100 GB2GB$0.0061x
    depot-ubuntu-22.04-4416 GB130 GB4GB$0.0122x
    depot-ubuntu-22.04-8832 GB150 GB8GB$0.0244x
    depot-ubuntu-22.04-161664 GB180 GB8GB$0.0488x
    depot-ubuntu-22.04-3232128 GB200 GB16GB$0.09616x
    depot-ubuntu-22.04-6464256 GB250 GB32GB$0.19232x
    depot-ubuntu-22.04-arm28 GB100 GB2GB$0.0061x
    depot-ubuntu-22.04-arm-4416 GB130 GB4GB$0.0122x
    depot-ubuntu-22.04-arm-8832 GB150 GB8GB$0.0244x
    depot-ubuntu-22.04-arm-161664 GB180 GB8GB$0.0488x
    depot-ubuntu-22.04-arm-3232128 GB200 GB16GB$0.09616x
    depot-ubuntu-22.04-arm-6464256 GB250 GB32GB$0.19232x

    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 Window Server 2025.

    Windows Server 2025 runners

    The following labels are available:

    LabelCPUsMemoryDisk sizePer-minute priceMinutes multiplier
    depot-windows-202528 GB100 GB$0.0082x
    depot-windows-2025-4416 GB130 GB$0.0164x
    depot-windows-2025-8832 GB150 GB$0.0328x
    depot-windows-2025-161664 GB180 GB$0.06416x
    depot-windows-2025-3232128 GB200 GB$0.12832x
    depot-windows-2025-6464256 GB250 GB$0.25664x

    Windows Server 2022 runners

    The following labels are available:

    LabelCPUsMemoryDisk sizePer-minute priceMinutes multiplier
    depot-windows-202228 GB100 GB$0.0082x
    depot-windows-2022-4416 GB130 GB$0.0164x
    depot-windows-2022-8832 GB150 GB$0.0328x
    depot-windows-2022-161664 GB180 GB$0.06416x
    depot-windows-2022-3232128 GB200 GB$0.12832x
    depot-windows-2022-6464256 GB250 GB$0.25664x

    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, than 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:

    LabelCPUsMemoryDisk sizeDisk accelerator sizePer-minute price
    depot-macos-26 (depot-macos-latest)824 GB400 GB2 GB$0.08
    depot-macos-15824 GB400 GB2 GB$0.08
    depot-macos-14824 GB400 GB2 GB$0.08

    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 multiples 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.

    Advertisement
    Advertisement