WarpBuild LogoWarpBuild Docs

Custom Runners

Customize runners for cost and performance

Custom runners are not available for organizations created after 2025-07-01.

Choose from available CPU and disk presets to fit your price-performance preferences from the Custom Runners page.

The overall price for the selected configuration is displayed.

CPU configurations

ConfigDescriptionArchCapacity TypePrice per 1vCPU
largeHigh performance, current generation processorsx64OnDemand$0.00126
mediumHigh performance, previous generation processorsx64OnDemand$0.00108
smallBurst performance, older generation processorsx64OnDemand$0.0009
largeHigh performance, current generation processorsarm64OnDemand$0.000945
mediumHigh performance, previous generation processorsarm64OnDemand$0.00081
smallBurst performance, older generation processorsarm64OnDemand$0.000675
largeHigh performance, current generation processorsx64Spot$0.000945
mediumHigh performance, previous generation processorsx64Spot$0.00081
smallBurst performance, older generation processorsx64Spot$0.000675
largeHigh performance, current generation processorsarm64Spot$0.000506
mediumHigh performance, previous generation processorsarm64Spot$0.000608
smallBurst performance, older generation processorsarm64Spot$0.000709

Disk configurations

ConfigStorageIOPSThroughput (MB/s)Price
xlarge300GB120001000$0.009045
large300GB8000800$0.006164
medium150GB5000500$0.001695
small150GB3200250$0.000719

Disk configurations

Optimization

The specific workflow runtime depends on various factors beyond just disk and CPU performance. It's a good idea to understand whether the workflow is CPU bound or IO bound for choosing the optimal configuration for your workflow.

A general rule to note is that the network infrastructure speeds (> 900MBps) are much higher than the disk throughput (~250-1000 MBps) and is unlikely to be a bottleneck. However, it could still be the limiting factor if the source (example: dockerhub) does not support high data transfer speeds.

Boot times

Boot times for custom runners can be slower than the default runners and take 45-60s.

Running Dependabot Workflows

You can run Dependabot update workflows on WarpBuild custom runners.

Enable Dependabot workflows on self-hosted runners on GitHub and check the Allow Dependabot check box while creating the custom runner on WarpBuild:

Allow Dependabot

This setup will run all your Dependabot workflows on the WarpBuild custom runner.

For security reasons, when running Dependabot on GitHub Actions self-hosted runners, Dependabot updates will not be run on public repositories. Learn More.

Last updated on