Build Hub self-serve is live: bring us your slowest build

“When we started using Build Hub, a huge amount of work just disappeared. Suddenly we didn’t have to worry about OS patching, Xcode image management, or hardware lifecycles. Or pray that a job won't hit an old M1 agent. We don’t have to think about any of that anymore. We’ve gone from being infrastructure maintainers to platform level engineers and enablers.” 

That's Nathan Hillyer, Director of Engineering at ForeFlight, on what happened after his team started running their GitHub Actions workflows on Bitrise Build Hub.

Until last month, trying that for yourself meant talking to sales first. That’s fine for a 300-person engineering org evaluating a CI overhaul, but it made no sense for the two-pizza team that just wants to know whether changing one line of YAML will meaningfully speed up their Xcode builds.

That's fixed. Build Hub self-serve went live at the end of August. Plans start from as little as $15 a month, and there's no sales conversation between you and build infrastructure that can actually handle heavy mobile workloads.

What $15 a month gets you

The Basic tier starts at $15/month for an M4 Mac runner (5 vCPU, 14GB) plus three Linux sizes. The tiers scale up to $180/month in increments, so you’re never paying for more capacity than you need.

Pro starts at $210/month and adds bigger machines and more concurrency. All tiers come with a fixed compute budget that lets you spend flexibly on Mac or Linux minutes depending on your team’s needs. 

Get the full breakdown on the pricing page.

The best part is that switching over is quick and simple. Just change your runs-on line to point your builds at Bitrise Build Hub and watch those build times drop. No messy migration, no workflow rewrites, no retraining required. GitHub Actions is still your CI orchestrator, you're just changing what the build actually runs on.

Bring us your slowest build (and win some swag) - open through October 9

In our own reproducible benchmarks, our machines finished an Xcode build 54% faster than GitHub's hosted Mac runners(up to 90% when you add on our co-located Build Cache), and Android builds 31% faster with fewer cores. ForeFlight numbers back that up: their engineering team measured close to 30% faster builds even on Build Hub's mid-tier Mac VMs, compared to GitHub's macOS XL GitHub-hosted runner. 

But don’t take our word for it. We’ve already got a comparison page, but your own repo running your own workflows is harder to argue with. So here's the challenge:

1. Sign up for a 14-day Build Hub free trial
2. Point your slowest GitHub Actions workflow at Build Hub (seriously, bring us your worst offenders), then
3. Email us at [email protected] with screenshots of the before-and-after of your GitHub Action completed job pages (please ensure the successful jobs’ build times are visible in both screenshots).

Can you beat the benchmark? Entries are open through October 9, and the top 3 biggest speed improvements win a Bitrise swag bag. (Yes, including a coveted BitBot or PurrRequest plushie!)