Home›Read›Tools desk›Latchkey offers $0.0025 per minute GitHub Actions runners post-BuildJet shutdown
Tools·Nov 15, 2026

Latchkey offers $0.0025 per minute GitHub Actions runners post-BuildJet shutdown

Evaluating Latchkey as a low-cost, x86_64 alternative to GitHub-hosted runners following BuildJet's shutdown, analyzing its 100GB disk allowance, missing arm64 support, and subscription pricing…

Evaluating Latchkey as a low-cost, x86_64 alternative to GitHub-hosted runners following BuildJet's shutdown, analyzing its 100GB disk allowance, missing arm64 support, and subscription pricing model.

For engineering teams migrating off sunsetted third-party runners like BuildJet, Latchkey provides an aggressive price floor for x86_64 Linux workloads. At $0.0025 per minute for a 2 vCPU, 8 GB RAM instance with a 100 GB disk, it undercuts GitHub-hosted runners ($0.006 per minute with 14 GB disk) by over 58%.

Skip Latchkey if your CI/CD pipelines depend on arm64, Windows, or macOS compute, or if you refuse to pay base platform subscription fees on top of per-minute compute costs.

Methodology

This v0 review evaluates Latchkey using vendor documentation and public pricing tables captured on 20 September 2026, following the shutdown of BuildJet for GitHub Actions on 31 March 2026 (announced 6 February 2026). The primary signal source is the comparative analysis published at https://dev.to/kalemi/latchkey-vs-buildjet-after-the-buildjet-shutdown-2a25.

Our analysis covers documented instance specifications, storage allocations, per-minute billing rates, and platform subscription tiers against standard GitHub-hosted rates. This review does not include independent latency measurements, cold-start telemetry, transient error recovery rates in production, or long-term dependency cache hit ratios.

v0 review caveat: This review draws on published vendor specs at https://dev.to/kalemi/latchkey-vs-buildjet-after-the-buildjet-shutdown-2a25; independent performance benchmarks are pending. Update cadence: re-tested when claims diverge from observed behavior.

What it does

Drop-in x86_64 Linux compute

Latchkey provides managed runner infrastructure designed to replace standard GitHub-hosted execution environments. Its fleet is strictly limited to Ubuntu 24.04 running on x86_64 architecture across four fixed configurations: 2 vCPU (8 GB RAM), 4 vCPU (16 GB RAM), 8 vCPU, and 16 vCPU. Unlike BuildJet, which provided arm64 variants across all instance tiers, Latchkey does not support arm64, Windows, or macOS environments.

Expanded local storage allocation

Every Latchkey runner instance ships with 100 GB of local disk space across all vCPU tiers. By comparison, standard 2 vCPU GitHub-hosted runners offer 14 GB of SSD storage on private repositories. This expanded disk capacity accommodates larger Docker builds, multi-gigabyte build artifacts, and extensive local cache directories without requiring custom disk mounting scripts.

Dependency caching and transient repair

To replace native caching mechanisms and deprecated third-party actions like buildjet/cache, Latchkey supplies a custom dependency cache step structured into separate restore and save phases. Additionally, the service incorporates automated transient failure recovery directly on the runner level, aimed at reducing unhandled job failures caused by network drops or socket timeouts during build steps.

What's interesting vs what's missing

Storage margin is the differentiator

The headline $0.0025 per minute rate for 2 vCPU compute is compelling against GitHub's $0.006 per minute rate, but the 100 GB disk allocation is the operational upgrade. Teams running heavy node_modules, Rust targets, or container image builds routinely exhaust GitHub's 14 GB limit. Latchkey solves this disk bottleneck at a lower compute rate.

Subscriptions alter net savings

While compute minutes are cheap, Latchkey requires a monthly plan ($5 to $49) after a 30-day trial. For teams running 10,000 2 vCPU Linux minutes monthly, Latchkey compute costs $25, but total monthly expenditure rises to $30 to $74 depending on the selected plan level. GitHub-hosted runners for the same 10,000 minutes cost $60 without a base fee (assuming zero free tier offset). Smaller teams with low build volume may find Latchkey's base platform subscription negates per-minute savings.

Lack of multi-architecture support

BuildJet's main value proposition was combining competitive pricing with drop-in arm64 compute. Latchkey fails to fill this gap. Teams compiling binaries for arm64 targets must maintain secondary runner pools on GitHub-hosted runners or alternative providers, reintroducing workflow routing complexity.

Pricing

Snapshot date: 20 September 2026

  • Compute Rates (x86_64 Ubuntu 24.04, per minute):
    • 2 vCPU / 8 GB RAM / 100 GB disk: $0.0025
    • 4 vCPU / 16 GB RAM / 100 GB disk: $0.005
    • 8 vCPU & 16 vCPU: Available (pricing scaled linearly per vCPU)
  • Subscription Tiers (after 30-day trial):
    • Developer ($5/mo): Includes 2,000 minutes/month.
    • Launch ($19/mo): Includes 4,000 minutes/month.
    • Scale ($49/mo): Includes 6,000 minutes/month.
  • Free Tier Limits: 30-day trial offered. Standard GitHub free allocations ($12 to $300/month equivalent) do not apply to Latchkey compute.

Verdict

Latchkey is a viable cost-reduction option for engineering teams running high-volume, x86_64 Linux CI pipelines that hit storage bottlenecks on GitHub-hosted runners. The $0.0025 per minute rate and 100 GB disk allocation offer clear unit-economic benefits for pure x86 workloads exceeding several thousand minutes monthly.

However, Latchkey is not a full BuildJet replacement. The complete absence of arm64, macOS, and Windows runners forces heterogeneous build systems into split-runner configurations. If your build matrix requires non-x86 architectures, stay on GitHub-hosted runners or evaluate dedicated multi-arch providers.

What we'd test next

In our upcoming v2 benchmark suite, we intend to measure:

  1. Cold-start latency comparison between Latchkey runners and GitHub-hosted Ubuntu 24.04 instances.
  2. I/O throughput on Latchkey's 100 GB disk under sustained heavy writes (such as unpackaged Docker layer extraction).
  3. Network throughput and restoration speed of Latchkey's dependency cache against standard actions/cache.
  4. Automated transient failure recovery success rate during simulated socket drops.

The investor read

The third-party CI/CD runner category has reached a clear pivot point following BuildJet's shutdown in March 2026. Latchkey demonstrates that pure price competition on standard Linux x86_64 compute ($0.0025/min vs GitHub's $0.006/min) is insufficient to capture defensive market share without architectural coverage (arm64, macOS). As GitHub lowers native runner costs and expands native caching, standalone runner utility playbooks face compressed margins and high churn risk. Latchkey remains a niche efficiency play unless it adds multi-architecture support and enterprise security compliance.

Pull quote: “For engineering teams migrating off sunsetted third-party runners like BuildJet, Latchkey provides an aggressive price floor for x86_64 Linux workloads.”

Sources · how we verified
  1. Latchkey vs BuildJet after the BuildJet shutdown ↗

Every claim ties to a primary source. See our methodology.

Reported by the Riley desk on Founderr Pulse’s Tools beat. Every factual claim is tied to a primary source and linked; anything that can’t be stood up doesn’t run. Founderr (RIKHATH LLC) is the accountable publisher and corrects in place. How we work · About · File a correction.
R
Riley

The Riley desk covers tools — what founders are building with, switching to, and abandoning. Every claim is sourced and linked. Operated by Founderr (RIKHATH LLC) See the desk →

Founderr Pulse — free & independent. The desk for people who build & back.