CI Runnerscirunners.org
Status notice

BuildJet for GitHub Actions (discontinued)

Answer in brief

BuildJet announced on 6 February 2026 that BuildJet for GitHub Actions was shutting down: new signups stopped that day and the service stopped running jobs after 31 March 2026. Its website now states that the service has been shut down. Closest alternatives: GitHub-hosted runners, Blacksmith, Ubicloud Runners.

By the CI Runners editors · Updated

Status: BuildJet announced on 6 February 2026 that BuildJet for GitHub Actions was shutting down: new signups stopped that day and the service stopped running jobs after 31 March 2026. Its website now states that the service has been shut down.

Overview

BuildJet for GitHub Actions was a managed runner service: teams authorised its GitHub OAuth app and changed runs-on to a label such as buildjet-4vcpu-ubuntu-2204. Jobs ran in KVM virtual machines on what BuildJet called custom dedicated bare-metal infrastructure, and the VM was wiped after each job. It offered Ubuntu runners on x64 and arm64 from 2 to 32 vCPU, billed per minute, plus a cache action compatible with actions/cache.

BuildJet announced on 6 February 2026 that the service was shutting down. New signups stopped that day and the service stopped running jobs after 31 March 2026. The announcement says GitHub Actions has gained faster hardware, larger runners and native ARM runners since BuildJet launched, and that the company decided to focus elsewhere. It recommends moving workflows to GitHub-hosted runners and replacing buildjet/cache with actions/cache. This record is kept for reference.

Notable

  • On 6 February 2026 BuildJet announced that BuildJet for GitHub Actions was shutting down and stopped accepting new signups.
  • The announcement set 31 March 2026 as the date after which BuildJet stops running jobs.
  • From 6 February 2026 concurrency subscriptions were made free while pay-as-you-go billing continued, according to the announcement.

How BuildJet for GitHub Actions compares

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
BuildJet for GitHub ActionsGitHub ActionsLinux, x64, arm64Vendor-hostedKVM VMNot documented32 vCPU / 64 GBNot documentedNot documentedNoEstonia
GitHub-hosted runnersGitHub ActionsLinux, macOS, Windows, x64, arm64Platform-hostedFresh VM$0.006/min96 vCPU / 384 GBNot documentedYesNoUnited States
BlacksmithGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedFirecracker microVM$0.004/min32 vCPU / 128 GBYesNot documentedNoUnited States
Ubicloud RunnersGitHub ActionsLinux, x64, arm64Vendor-hostedKVM VM$0.00125/min30 vCPU / 120 GBYesNot documentedYesUnited States
WarpBuildGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedEphemeral VM$0.004/min32 vCPU / 128 GBYesNot documentedNoNot documented
Depot GitHub Actions RunnersGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedSingle-tenant EC2 instance$0.006/min64 vCPU / 256 GBYesYesNoNot documented
NamespaceGitHub Actions, BuildkiteLinux, macOS, Windows, x64, arm64Vendor-hostedVirtual machine$0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB)64 vCPU / 512 GBYesNot documentedNoNot documented

See all BuildJet for GitHub Actions alternatives →

Frequently asked questions

What is BuildJet for GitHub Actions?
Managed GitHub Actions runners on dedicated bare metal; shut down in 2026 and no longer running jobs. A discontinued managed runner service for GitHub Actions that stopped running jobs after 31 March 2026; listed for reference only.
Which CI systems does BuildJet for GitHub Actions work with?
BuildJet for GitHub Actions runs jobs for GitHub Actions, on Linux, x64 and arm64.
How does BuildJet for GitHub Actions isolate jobs?
BuildJet for GitHub Actions documents its isolation as: Each job ran in a KVM virtual machine that was wiped after the job. Each job gets a fresh environment that is discarded afterwards.
Is BuildJet for GitHub Actions open source?
No, BuildJet for GitHub Actions is not open source.
How much does BuildJet for GitHub Actions cost?
Rates still shown in the docs, although the service no longer runs jobs: $0.004/min (2 vCPU), $0.008 (4 vCPU), $0.016 (8 vCPU), $0.032 (16 vCPU) and $0.048 (32 vCPU) on x64; arm64 was priced the same except $0.064/min at 32 vCPU. Check the official pricing page for current rates.
What are the alternatives to BuildJet for GitHub Actions?

Sources

  1. buildjet.com/for-github-actions/blog/we-are-shutting-down
  2. buildjet.com/for-github-actions
  3. buildjet.com/for-github-actions/docs
  4. buildjet.com/for-github-actions/docs/about/pricing
  5. buildjet.com/for-github-actions/docs/about/security
  6. buildjet.com/for-github-actions/docs/runners/hardware
  7. buildjet.com/for-github-actions/docs/getting-started/run-your-first-workflow
  8. buildjet.com/for-github-actions/docs/about/terms-of-service
  9. buildjet.com/for-github-actions/docs/about/privacy-policy

Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 22, 2026. Confirm anything that matters in the provider’s own documentation.

Cite this page

CI Runners. (2026). BuildJet for GitHub Actions (discontinued). cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/buildjet/