CI Runnerscirunners.org
Runner profile · Managed runner service

Bitrise Build Hub

Answer in brief

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.

By the CI Runners editors · Updated

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

AttributeDetails
CI systemsGitHub Actions
Operating systemsmacOS, Linux
Architecturesarm64, x64
DeploymentManaged runner service
IsolationJobs 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 jobYes
HardwareBitrise-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 sizesSelf-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
CachingA 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 cachingNot documented
GPUNot documented
ConcurrencyCounted 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 limitsNot documented
Static IPsYes
SSH into running jobsYes
ObservabilityThe machine pool view shows per-machine status, live stdout and stderr logs and, where enabled, CPU, memory and disk charts.
SetupCreate 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 labelbitrise-runner-my-pool
PricingPlans 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 tier14-day free trial with all Basic and Pro machine types, limited to 30 macOS vCPU and 48 Linux vCPU
ComplianceSOC 2 Type II and PCI DSS (as stated by Bitrise)
RegionsUS and EU data centres operated by Bitrise
Open sourceNo
Company headquartersNot 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

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
Bitrise Build HubGitHub ActionsmacOS, Linux, arm64, x64Vendor-hostedVirtual machine$0.00625/min16 vCPU / 64 GBNot documentedNot documentedNoNot documented
GitHub-hosted runnersGitHub ActionsLinux, macOS, Windows, x64, arm64Platform-hostedFresh VM$0.006/min96 vCPU / 384 GBNot documentedYesNoUnited States
GetMacGitHub Actions, GitLab CI, BuildkitemacOS, arm64Vendor-hostedmacOS VM$0.012/min (macOS M4, Developer plan)Not documentedNot documentedNot documentedNoLithuania
OrkaGitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines, TeamCitymacOS, arm64Your cloud or hardwaremacOS VMFrom $109/mo per hosted Mac mini (Orka by quote)Set by your infrastructureNot documentedNot documentedNoUnited States
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
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
BlacksmithGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedFirecracker microVM$0.004/min32 vCPU / 128 GBYesNot documentedNoUnited States

Head-to-head: Bitrise Build Hub vs GetMac · Bitrise Build Hub vs Orka

See all Bitrise Build Hub alternatives →

Frequently asked questions

What is 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.
Which CI systems does Bitrise Build Hub work with?
Bitrise Build Hub runs jobs for GitHub Actions, on macOS, Linux, arm64 and x64.
How does Bitrise Build Hub isolate jobs?
Bitrise Build Hub documents its isolation as: 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. Each job gets a fresh environment that is discarded afterwards.
Is Bitrise Build Hub open source?
No, Bitrise Build Hub is not open source.
How much does Bitrise Build Hub cost?
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. Check the official pricing page for current rates.
How do I switch from GitHub-hosted runners to Bitrise Build Hub?
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. An example label is bitrise-runner-my-pool.
How fast is Bitrise Build Hub?
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). Speed figures are the provider’s own and depend on the workload.
Does Bitrise Build Hub have a free tier?
14-day free trial with all Basic and Pro machine types, limited to 30 macOS vCPU and 48 Linux vCPU.
Does Bitrise Build Hub support ARM64 runners?
Yes, Bitrise Build Hub documents arm64 runners (macOS and Linux).
Does Bitrise Build Hub offer macOS runners?
Yes, Bitrise Build Hub documents macOS runners alongside Linux.
How many jobs can run at once on Bitrise Build Hub?
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.
Where do Bitrise Build Hub runners run?
US and EU data centres operated by Bitrise.
What compliance certifications does Bitrise Build Hub have?
SOC 2 Type II and PCI DSS (as stated by Bitrise).
What are the alternatives to Bitrise Build Hub?

Sources

  1. bitrise.io/platform/build-hub
  2. bitrise.io/pricing
  3. docs.bitrise.io/en/bitrise-build-hub
  4. docs.bitrise.io/en/bitrise-build-hub/build-hub-for-github-actions/build-hub-for-github-actions-overview
  5. docs.bitrise.io/en/bitrise-build-hub/build-hub-for-github-actions/creating-machine-pools-for-github-actions
  6. docs.bitrise.io/en/bitrise-build-hub/build-hub-for-github-actions/configuring-your-github-actions-workflow
  7. docs.bitrise.io/en/bitrise-build-hub/build-hub-for-github-actions/monitoring-machine-pools-for-github-actions
  8. docs.bitrise.io/en/bitrise-build-hub/infrastructure/build-machine-types
  9. docs.bitrise.io/en/bitrise-build-hub/infrastructure/ip-addresses-for-the-build-machines
  10. docs.bitrise.io/en/bitrise-build-hub/changelog
  11. bitrise.io/platform/devops/security
  12. bitrise.io/about
  13. bitrise.io/blog/post/m5-pro-runners-for-github-actions-coming-to-bitrise-build-hub
  14. 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/