Latchkey vs WarpBuild: GitHub Actions Runner Costs
Résumé
Pixel’s announcement compares Latchkey and WarpBuild for GitHub Actions, including managed runner rates of $0.0025 and $0.004 per minute and WarpBuild’s $0.002 BYOC orchestration fee. It also covers cloud-provider costs, supported platforms, caching, and runner features to help teams weigh savings against managing their own cloud accounts.
DEV Community
Latchkey vs WarpBuild for GitHub Actions runners
On managed runners Latchkey is $0.0025 a minute at 2 vCPU against WarpBuild at $0.004, but that is not the comparison most WarpBuild users are making: its bring-your-own-cloud mode runs in your own AWS, GCP or Azure account at $0.002 a minute, which is cheaper than both. The question is whether you want to own the cloud account the jobs run in. One month of 10,000 Linux minutes at 2 vCPU on a private repository at each published rate. The BYOC bar is the WarpBuild orchestration charge only; the instances are billed by your own cloud provider on top. Rates read 20 September 2026. WarpBuild sells managed GitHub Actions runners at $0.004 a minute for 2 vCPU and 8 GB, adopted by installing its bot from the WarpBuild dashboard rather than the GitHub marketplace and setting runs-on to a runner ID such as warp-ubuntu-latest-x64-4x. It also sells a bring-your-own-cloud mode at $0.002 a minute where the machines run in your own cloud account, publishes arm64 at $0.003, and ships Windows and macOS runners. Its cache is metered separately at $0.20 per GB-month plus a charge per write or restore. Latchkey sells managed runners only, at $0.0025 a minute for 2 vCPU and 8 GB, in its own AWS estate, with a self-healing agent that repairs transient failures inside the run. There is no BYOC mode, no arm64, no Windows and no macOS, and the cache is not metered separately. Every cell below was read from the vendor's own public pricing or documentation page on 20 September 2026. Where a vendor does not publish a number, the cell says "not published" instead of carrying a guess. Comparison WarpBuild Latchkey Price per minute, 2 vCPU Linux x64 $0.004 (2 vCPU, 8 GB RAM) $0.0025 (2 vCPU, 8 GB RAM, 100 GB disk) Price per minute, 4 vCPU Linux x64 $0.008 (4 vCPU, 16 GB RAM) $0.005 (4 vCPU, 16 GB RAM, 100 GB disk) Bring your own cloud $0.002/min running in your own AWS, GCP or Azure account Not offered Free tier Not published. Sign-up needs no card until you reach a usage or credit limit 30-day trial, then 2,000 included minutes a month on Developer, 4,000 on Launch, 6,000 on Scale Billing granularity Per minute, in its own words: "CI runners are billed on a per-minute basis" Per minute Runner sizes and OS 2 to 32 vCPU on Linux x64 and arm64; Windows from 4 to 32 vCPU; macOS M4 Pro at 6 and 12 vCPU; Linux on Apple silicon at 6 and 12 vCPU 2, 4, 8 and 16 vCPU, Ubuntu 24.04 on x86_64 only. arm64, Windows and macOS are not offered Cache: type, limit, persistence Metered: $0.20 per GB-month of storage plus $0.0001 per write or restore; snapshot restore $0.04 a job and $0.025 an hour of snapshot storage Size not published. latchkey-dev/cache-action@v1 replaces actions/cache with a restore step and a save step, keeping path and key (no restore-keys); entries are isolated per organization, versioned by OS, kept 14 days; a failed restore warns rather than failing the job Docker build acceleration Remote BuildKit builders on their own meter, 16 vCPU at $0.06/min to 192 vCPU at $0.88, driven by Warpbuilds/build-push-action@v7; the shared cache is eventually consistent with a 10-day TTL latchkey-dev/docker-cache-action@v1, layers held in a Latchkey-managed private registry per organization Concurrency limits Advertised as unlimited job concurrency; the no-queue guarantee and an SLA behind it are Enterprise features Developer 20, Launch 40, Scale 80 busy runners per workspace; idle warm runners do not count Where jobs run WarpBuild's own cloud, or your AWS, GCP or Azure account under BYOC Latchkey's own AWS estate on m6a-class hosts, one job per runner, no inbound access, destroyed after the job Self-healing or retries Not offered Built in: transient failures are diagnosed and retried inside the run Setup change required Sign up, install the WarpBuild bot from its dashboard rather than the GitHub marketplace, then set runs-on to a runner ID such as warp-ubuntu-latest-x64-4x A runs-on label change. GitHub organization accounts only The BYOC rate is the real compar...
Powered by Readybot.io
