Bitrise Build Hub
Bitrise-managed macOS and Linux runners for GitHub Actions on Bitrise-owned Apple silicon and AMD EPYC machines, sold as monthly compute budgets. Bitrise Build Hub is a managed runner service for GitHub Actions from a mobile CI vendor, suited to teams that want Bitrise’s Mac hardware and mobile stacks without leaving GitHub Actions.
Overview
Bitrise Build Hub runs GitHub Actions jobs on machines that Bitrise, the mobile CI vendor, owns and operates. A team creates a machine pool in a Bitrise workspace, connects it through the Bitrise - Build Hub GitHub App, and points runs-on at the pool’s labels; workflow files otherwise stay as they are. Pools use Apple silicon Mac minis or AMD EPYC Linux machines with Bitrise’s mobile build stacks.
Build Hub is sold separately from Bitrise CI, as monthly compute budgets shared between macOS and Linux and drawn down at per-minute machine rates. It works with GitHub Cloud and GitHub Enterprise Server. Pools can send GitHub Actions cache requests to Bitrise’s co-located cache, run a warmup script, and expose SSH or VNC access to a running machine. Bitrise says new Xcode versions are available within 24 hours of release.
Notable
- August 25, 2026: Bitrise announced that M5 Pro and M6 Mac mini runners would be added to Build Hub
- June 1, 2026: a Bitrise blog post described three Bitrise-operated data centres (two in the US, one in the EU)
- September 22, 2026: docs changelog notes that Build Hub runners authenticate to the Bitrise Build Cache without a token
Bitrise Build Hub specifications
| Attribute | Details |
|---|---|
| CI systems | GitHub Actions |
| Operating systems | macOS, Linux |
| Architectures | arm64, x64 |
| Deployment | Managed runner service |
| Isolation | Jobs run on virtual machines from pre-warmed pools; with GitHub App authentication a machine is provisioned when a workflow starts and shut down when the build ends, while with a personal access token the requested number of machines is kept running |
| Fresh environment per job | Yes |
| Hardware | Bitrise-owned Mac minis (M4 and M4 Pro, with M5 Pro and M6 listed on the Enterprise plan) and AMD EPYC Zen 4/Zen 5 Linux machines in data centres that Bitrise operates. |
| Performance (vendor claim) | Bitrise publishes its own benchmark of 2m 27s on a Build Hub M5 Pro machine against 8m 43s on a GitHub-hosted M2 runner for the DuckDuckGo iOS app (vendor claim) |
| Runner sizes | Self-serve plans: macOS M4 Large (5 vCPU, 14 GB) and M4 X Large (10 vCPU, 28 GB); Linux from 2Small (2 vCPU, 8 GB) to X Large (16 vCPU, 64 GB). Enterprise lists M4 Pro, M5 Pro and M6 and Linux up to 192 vCPU |
| Caching | A machine pool can route GitHub Actions cache requests to Bitrise infrastructure instead of GitHub’s cache backend. The separately priced Bitrise Build Cache (Gradle, Bazel, Xcode, React Native) needs no token on Build Hub machines. |
| Docker layer caching | Not documented |
| GPU | Not documented |
| Concurrency | Counted in vCPU: Basic up to 35 macOS and 136 Linux vCPU, Pro up to 90 macOS and 640 Linux vCPU, depending on tier; the trial allows 30 macOS and 48 Linux vCPU |
| Job limits | Not documented |
| Static IPs | Yes |
| SSH into running jobs | Yes |
| Observability | The machine pool view shows per-machine status, live stdout and stderr logs and, where enabled, CPU, memory and disk charts. |
| Setup | Create a machine pool in a Bitrise workspace, install the Bitrise - Build Hub GitHub App (or use a personal access token on Enterprise), then target the pool’s labels in runs-on. |
| Example label | bitrise-runner-my-pool |
| Pricing | Plans are monthly compute budgets: Basic from $15/month ($13.50 billed annually), Pro from $210/month ($189 billed annually), Enterprise by quote. Machine rates per minute: macOS M4 Large $0.03, M4 XLarge $0.06; Linux 2Small (2 vCPU) $0.00625, Medium (4 vCPU) $0.0125, Large (8 vCPU) $0.025, XLarge (16 vCPU) $0.05. Pay-As-You-Go rates are listed at 2x these. |
| Free tier | 14-day free trial with all Basic and Pro machine types, limited to 30 macOS vCPU and 48 Linux vCPU |
| Compliance | SOC 2 Type II and PCI DSS (as stated by Bitrise) |
| Regions | US and EU data centres operated by Bitrise |
| Open source | No |
| Company headquarters | Not documented |
Facts from Bitrise Build Hub’s public documentation, verified November 22, 2026. Performance figures are vendor claims.
Strengths and trade-offs
Reasons to choose it
- You build iOS and Android apps on GitHub Actions and want macOS and Linux runners from one vendor
- You want stacks with Xcode, Android SDK, Flutter and React Native tooling preinstalled
- You need SSH or VNC access to a running machine for debugging
- You need a choice of US or EU data centres for data residency
- You run GitHub Enterprise Server as well as GitHub Cloud
Trade-offs
- Pay-As-You-Go is off by default, so jobs do not run on Build Hub once the monthly budget is used up
- Pay-As-You-Go per-minute rates are twice the standard machine rates
- Personal access token authentication is available only on Enterprise plans
- M4 Pro, M5 Pro and M6 machines and Linux above 16 vCPU are listed only on the Enterprise plan
Good fit for: Mobile teams on GitHub Actions that want managed Apple silicon and Linux runners with iOS and Android toolchains preinstalled.
Use cases Bitrise Build Hub fits
- Faster builds: Bitrise publishes its own benchmarks against GitHub-hosted runners and offers a co-located cache (vendor claims).
- macOS and iOS builds: Build Hub runs GitHub Actions jobs on Apple silicon Mac minis with Xcode stacks that Bitrise says are updated within 24 hours of a release.
- Security and compliance: Bitrise states SOC 2 Type II and PCI DSS compliance and offers US and EU data centre locations.
How Bitrise Build Hub compares
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| Bitrise Build Hub | GitHub Actions | macOS, Linux, arm64, x64 | Vendor-hosted | Virtual machine | $0.00625/min | 16 vCPU / 64 GB | Not documented | Not documented | No | Not documented |
| GitHub-hosted runners | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Fresh VM | $0.006/min | 96 vCPU / 384 GB | Not documented | Yes | No | United States |
| GetMac | GitHub Actions, GitLab CI, Buildkite | macOS, arm64 | Vendor-hosted | macOS VM | $0.012/min (macOS M4, Developer plan) | Not documented | Not documented | Not documented | No | Lithuania |
| Orka | GitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines, TeamCity | macOS, arm64 | Your cloud or hardware | macOS VM | From $109/mo per hosted Mac mini (Orka by quote) | Set by your infrastructure | Not documented | Not documented | No | United States |
| Namespace | GitHub Actions, Buildkite | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Virtual machine | $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB) | 64 vCPU / 512 GB | Yes | Not documented | No | Not documented |
| WarpBuild | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Ephemeral VM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | Not documented |
| Depot GitHub Actions Runners | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Single-tenant EC2 instance | $0.006/min | 64 vCPU / 256 GB | Yes | Yes | No | Not documented |
| Blacksmith | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Firecracker microVM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | United States |
Head-to-head: Bitrise Build Hub vs GetMac · Bitrise Build Hub vs Orka
Frequently asked questions
What is Bitrise Build Hub?
Which CI systems does Bitrise Build Hub work with?
How does Bitrise Build Hub isolate jobs?
Is Bitrise Build Hub open source?
How much does Bitrise Build Hub cost?
How do I switch from GitHub-hosted runners to Bitrise Build Hub?
bitrise-runner-my-pool.How fast is Bitrise Build Hub?
Does Bitrise Build Hub have a free tier?
Does Bitrise Build Hub support ARM64 runners?
Does Bitrise Build Hub offer macOS runners?
How many jobs can run at once on Bitrise Build Hub?
Where do Bitrise Build Hub runners run?
What compliance certifications does Bitrise Build Hub have?
What are the alternatives to Bitrise Build Hub?
Sources
- bitrise.io/platform/build-hub
- bitrise.io/pricing
- docs.bitrise.io/en/bitrise-build-hub
- docs.bitrise.io/en/bitrise-build-hub/build-hub-for-github-actions/build-hub-for-github-actions-overview
- docs.bitrise.io/en/bitrise-build-hub/build-hub-for-github-actions/creating-machine-pools-for-github-actions
- docs.bitrise.io/en/bitrise-build-hub/build-hub-for-github-actions/configuring-your-github-actions-workflow
- docs.bitrise.io/en/bitrise-build-hub/build-hub-for-github-actions/monitoring-machine-pools-for-github-actions
- docs.bitrise.io/en/bitrise-build-hub/infrastructure/build-machine-types
- docs.bitrise.io/en/bitrise-build-hub/infrastructure/ip-addresses-for-the-build-machines
- docs.bitrise.io/en/bitrise-build-hub/changelog
- bitrise.io/platform/devops/security
- bitrise.io/about
- bitrise.io/blog/post/m5-pro-runners-for-github-actions-coming-to-bitrise-build-hub
- bitrise.io/blog/post/ship-ios-and-android-builds-twice-as-fast-on-github-actions
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). Bitrise Build Hub. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/bitrise-runners/