We're shutting down BuildJet for GitHub Actions

We're announcing that BuildJet for GitHub Actions is shutting down. As of March 31st, 2026, runners using the BuildJet for GitHub Actions service will no longer be available. You will need to migrate to GitHub's hosted runners before this date.

Effective today (February 6th, 2026)

• New signups are no longer accepted
• All concurrency subscriptions are now free - your concurrencylimits remain unchanged
• Pay-as-you-go usage billing continues as normal, until March 31st, 2026

March 31st, 2026

• BuildJet stops running jobs - migrate your workflows before this date

Update your workflow files to use GitHub's hosted runners:

yaml
1
jobs:
2
  build:
-
    runs-on: buildjet-2vcpu-ubuntu-2204
+
    runs-on: ubuntu-latest
5
    steps:
6
      - uses: actions/checkout@v4

For ARM workflows, GitHub now offers native ARM runners:

yaml
1
jobs:
2
  build:
-
    runs-on: buildjet-2vcpu-ubuntu-2204-arm
+
    runs-on: ubuntu-24.04-arm
5
    steps:
6
      - uses: actions/checkout@v4

For teams requiring more powerful runners, see GitHub-hosted runners for available options, or consider larger runners and self-hosted runners.

BuildJet Cache is interoperable with actions/cache. Simply swap the action:

yaml
1
steps:
2
  - uses: actions/checkout@v4
-
  - uses: buildjet/cache@v4
+
  - uses: actions/cache@v4
5
    with:
6
      path: ~/.npm
7
      key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}

When we launched BuildJet, GitHub Actions had significant performance limitations that made CI/CD painfully slow for many teams. Since then, GitHub has made substantial improvements - faster hardware, larger runner options, and native ARM runner support. The gap we set out to fill has largely closed.

We've decided to focus our efforts elsewhere. Thank you to everyone who trusted BuildJet with their builds over the years.