Runners
WarpBuild runners are built to be the fastest CI/CD platform in the world. We pair the fastest processors with blazing fast SSDs and high bandwidth networking to give you the best performance possible.
WarpBuild runners are designed to be drop-in replacements for GitHub-hosted runners. They are fully compatible with GitHub Actions. Refer to the customizations section for more information. All WarpBuild runners are run on ephemeral VMs for maximum isolation and security. This means that they are freshly allocated when you need them and destroyed when the workflow is complete.
We currently support Linux on x86-64 and ARM64 architectures. We are working on adding support for MacOS with Windows support to follow.
Linux x86-64
| Runner Tag | CPU | Memory | Storage | Price | Aliases |
|---|---|---|---|---|---|
| warp-ubuntu-latest-x64-2x | 2 vCPU | 7GB | 150GB SSD | $0.004/minute | warp-ubuntu-2204-x64-2x |
| warp-ubuntu-latest-x64-4x | 4 vCPU | 16GB | 150GB SSD | $0.008/minute | warp-ubuntu-2204-x64-4x |
| warp-ubuntu-latest-x64-8x | 8 vCPU | 32GB | 150GB SSD | $0.016/minute | warp-ubuntu-2204-x64-8x |
| warp-ubuntu-latest-x64-16x | 16 vCPU | 64GB | 150GB SSD | $0.032/minute | warp-ubuntu-2204-x64-16x |
| warp-ubuntu-latest-x64-32x | 30 vCPU | 120GB | 150GB SSD | $0.064/minute | warp-ubuntu-2204-x64-32x |
NOTE: The warp-ubuntu-latest-x64-32x runner has 30 vCPU and 120GB of memory.
The Linux x86-64 runner images are based on Ubuntu 22.04 LTS and have the same tooling installed as GitHub-hosted runners. Runner storage is ephemeral and will be deleted when the runner is terminated.
Linux ARM64
| Runner Tag | CPU | Memory | Storage | Price | Aliases |
|---|---|---|---|---|---|
| warp-ubuntu-latest-arm64-2x | 2 vCPU | 7GB | 150GB SSD | $0.003/minute | warp-ubuntu-2204-arm64-2x |
| warp-ubuntu-latest-arm64-4x | 4 vCPU | 16GB | 150GB SSD | $0.006/minute | warp-ubuntu-2204-arm64-4x |
| warp-ubuntu-latest-arm64-8x | 8 vCPU | 32GB | 150GB SSD | $0.012/minute | warp-ubuntu-2204-arm64-8x |
| warp-ubuntu-latest-arm64-16x | 16 vCPU | 64GB | 150GB SSD | $0.024/minute | warp-ubuntu-2204-arm64-16x |
| warp-ubuntu-latest-arm64-32x | 32 vCPU | 128GB | 150GB SSD | $0.048/minute | warp-ubuntu-2204-arm64-32x |
The Linux ARM64 runner images are based on Ubuntu 22.04 LTS. These images are lean and it is recommended that you install the tooling you need in your workflow. Runner storage is ephemeral and will be deleted when the runner is terminated.
MacOS M2 Pro on ARM64
| Runner Tag | CPU | Memory | Storage | Price | Aliases |
|---|---|---|---|---|---|
| warp-macos-latest-arm64-6x | 6 vCPU | 14GB | 64GB SSD | $0.08/minute | warp-macos-13-arm64-6x |
| warp-macos-14-arm64-6x | 6 vCPU | 14GB | 64GB SSD | $0.08/minute |
The comparable GitHub-hosted runner is macos-latest-xlarge with 6 vCPUs (M1) and 14GB of memory. The WarpBuild runner is 25-40% faster than the GitHub-hosted runner and is 2x cheaper.
WarpBuild uniquely offers M2 Pro based MacOS runners built on ARM64 architecture. These runners are based on MacOS 13 and have the same tooling installed as GitHub-hosted runners, functioning as drop-in replacements. Compared to the Intel-based runners, the M2 Pro based runners can be up to 6x faster.
Note:
- MacOS runners are currently in beta and operate with limited concurrency. Please contact us through the in-app support widget for increasing concurrency.
macos-latestrunners from GitHub are based on Intel architecture and are significantly slower than the M2 Pro based runners. However, workflow files may need to be updated if you are using architecture-specific tooling.- MacOS runners do not support nested virtualization and cannot run docker.
macos-14runners are in beta in upstream GitHub. For this reason, WarpBuild will continue to have thelatesttag point tomacos-13runners.
Spot Instances
WarpBuild now supports spot instances for runners. Spot instances are 62.5% cheaper than GitHub actions runner instances and 25% cheaper than standard WarpBuild runners.
- Naming convention:
warp-<os>-<version>-<arch>-<cpu>x-spot. Note the-spotsuffix. - The configuration for spot instances is the same as the WarpBuild standard instances.
- The only difference is the price.
- Spot instances are ideal for short workloads that can be interrupted and restarted.
- They are not recommended for critical deploy tasks that may leave the workflow in a dirty state (for example,
tofu applysteps).
Here is the configuration and pricing table for spot instances:
| Runner Tag | CPU | Memory | Storage | Price | Aliases |
|---|---|---|---|---|---|
| warp-ubuntu-latest-x64-2x-spot | 2 vCPU | 7GB | 150GB SSD | $0.003/minute | warp-ubuntu-2204-x64-2x-spot |
| warp-ubuntu-latest-x64-4x-spot | 4 vCPU | 16GB | 150GB SSD | $0.006/minute | warp-ubuntu-2204-x64-4x-spot |
| warp-ubuntu-latest-x64-8x-spot | 8 vCPU | 32GB | 150GB SSD | $0.012/minute | warp-ubuntu-2204-x64-8x-spot |
| warp-ubuntu-latest-x64-16x-spot | 16 vCPU | 64GB | 150GB SSD | $0.024/minute | warp-ubuntu-2204-x64-16x-spot |
| warp-ubuntu-latest-x64-32x-spot | 30 vCPU | 120GB | 150GB SSD | $0.048/minute | warp-ubuntu-2204-x64-32x-spot |
| warp-ubuntu-latest-arm64-2x-spot | 2 vCPU | 7GB | 150GB SSD | $0.00225/minute | warp-ubuntu-2204-arm64-2x-spot |
| warp-ubuntu-latest-arm64-4x-spot | 4 vCPU | 16GB | 150GB SSD | $0.0045/minute | warp-ubuntu-2204-arm64-4x-spot |
| warp-ubuntu-latest-arm64-8x-spot | 8 vCPU | 32GB | 150GB SSD | $0.09/minute | warp-ubuntu-2204-arm64-8x-spot |
| warp-ubuntu-latest-arm64-16x-spot | 16 vCPU | 64GB | 150GB SSD | $0.018/minute | warp-ubuntu-2204-arm64-16x-spot |
| warp-ubuntu-latest-arm64-32x-spot | 32 vCPU | 128GB | 150GB SSD | $0.036/minute | warp-ubuntu-2204-arm64-32x-spot |
Note:
When a spot instance is reclaimed, the job is terminated and does not restart. This is for two reasons: github doesn't provide an easy way to re-trigger the job without user-side changes (like adding dispatch events). Secondly, not all CI jobs are idempotent or "safe" to be run multiple times, like deployments, IAC apply etc. We leave handling reruns up to the user.
Concurrency
The features that are Generally Available (GA) support unlimited concurrency. This means that workflows can spin up any number of jobs in parallel, and any number of workflows can run in parallel. The features that are in beta support may not support unlimited concurrency.
Caching
WarpBuild provides a blazing fast, unlimited cache for GitHub Action runners. This cache can be used to store build artifacts, dependencies, and other files that are needed across builds. The cache is designed to be fast, reliable, and secure. The cache is available on all Linux based runners and is enabled by default. More details can be found in the cache documentation.
WarpBuild Agent
The WarpBuild agent is present on the runner and is used to communicate with the WarpBuild platform for runner configuration and cleanup. The agent is open source and can be found here.
Coming soon
- Automated Buildkit caching for Docker builds which speed up builds by up to 10x.
- Windows runners
- Nested virtualization: x86-64 runners will support nested virtualization starting in Apr-May 2024.