BuildJet

After serving the GitHub Actions community, we're sunsetting BuildJet for GitHub Actions on March 31st, 2026.

We're thrilled to announce buildjet/cache, a reliable, fast, and free alternative to GitHub Actions cache. It is compatible with any runner - official, self-hosted, or BuildJet, and no matter the runner used, BuildJet doubles the free storage, providing 2

Today, we're happy to release the first-ever ARM runners for GitHub Actions. This will enable many thousands of developers to finally get native support for their ARM workflows. BuildJet for GitHub Actions ARM runner makes your workflows 10x faster than w

Today, we're delighted to introduce support for hardware accelerated Android emulators on all BuildJet runners. This allows Android developers to create fast and affordable runners for their CI workloads. BuildJet for GitHub Actions runs Android Emulator

In this breakdown we will take a close look at the why GitHub Actions default runners are so slow. Firstly, we'll compare GitHub Actions runners with a MacBook Pro 2015 running the official self-hosted software. We'll then figure out what actual hardware

It is common practice for CI's to simply state the amount of vCPUs at the user's disposal. We do the same and find it generally to be a good abstraction. Cross-service comparison gets easier and the users don't need to dabble with the details.

In this performance review, we will take a close look at the cost of slow hardware. Firstly, we will compare CI runs with different codebases, on different hardware. We will then explain the different CI runs, by drilling into characteristics of the respe

As most developers know, regardless of how much you try to multitask, waiting for the CI to finish always feels like an unnecessary bottleneck. As a consequence of project complexity and developers waiting for simple PR's, we always ended up migrating to

Change 1 line, get 2x faster and cheaper builds