Ready-to-run Linux machines for mobile CI/CD
Our fully managed Linux machines are optimized for mobile and cross-platform CI/CD workflows.
Faster builds
Our Linux portfolio is faster than ever, powering your builds with 4th gen AMD EPYC Zen 5 and Zen 4 processors.
Ready-to-go build environments
Pre-configured environments include the latest versions of Java, Kotlin, Flutter, React Native, plus package managers (lnpm, yarn), testing frameworks, and more.
Stability at scale
Our fully managed infrastructure automatically scales with your needs and maintains 99.9% uptime.
Machine types
Granular Linux machine sizing lets you right size your build machines to your compute needs and budget.
Machine type | vCPU | RAM | Average build time | Regions |
|---|---|---|---|---|
M | 4 vCPU @3.7 GHz | 16 GB | 575s | EU |
2M | 6 vCPU @3.7 GHz | 24 GB | 441s | EU |
L | 8 vCPU @3.7 GHz | 32 GB | 373s | EU |
4L | 14 vCPU @3.7 GHz | 56 GB | 294s | EU |
XL | 16 vCPU @3.7 GHz | 64 GB | 352s | EU |
3XL | 24 vCPU @3.7 GHz | 96 GB | 324s | EU |
5XL | 32 vCPU @3.7 GHz | 128 GB | 312s | EU |
7XL | 48 vCPU @3.7 GHz | 192 GB | 295s | EU |
Benchmarks compiled using Thunderbird Android, Gradle assemble.
Machine type | vCPU | RAM | Average build time | Regions |
|---|---|---|---|---|
M | 4 vCPU @3.7 GHz | 16 GB | 679s | US |
2M | 6 vCPU @3.7 GHz | 24 GB | 516s | US |
L | 8 vCPU @3.7 GHz | 32 GB | 436s | US |
4L | 14 vCPU @3.7 GHz | 56 GB | 340s | US |
XL | 16 vCPU @3.7 GHz | 64 GB | 396s | US |
3XL | 24 vCPU @3.7 GHz | 96 GB | 352s | US |
5XL | 32 vCPU @3.7 GHz | 128 GB | 347s | US |
7XL | 48 vCPU @3.7 GHz | 192 GB | 336s | US |
Benchmarks compiled using Thunderbird Android, Gradle assemble.
Standardized on GitHub Actions?
Get mobile-optimized infrastructure without changing your CI. Run GitHub Actions workflows on high-performance build machines, with same-day Xcode updates, zero maintenance, and unmatched speed and reliability.
Discover Build Hub
Ideal for Android teams
Complete Android toolchain
Get native Docker support and pre-installed toolchains including Android SDK, Gradle, fastlane, and more.
Smart caching
Cut build times up to 90% for apps built on Gradle and Bazel with our unique co-located Build Cache.
Device testing
Run UI tests on a full range of physical devices with Firebase Test Lab on Bitrise (no need to buy your own licence).
Release management
Easily distribute beta builds OTA via public and private links and automate staged production rollouts.
Ready to accelerate mobile development?
Talk to an expert about how you can transition your team to Bitrise and speed up your mobile pipelines today.
Contact salesFrequently Asked Questions
Are your x86 Linux virtual machines or bare metal servers?
Our Linux offering consists of virtual build machines running in the Bitrise cloud.
How do I get access to Linux machines?
Our Linux machines are available to all paying Bitrise customers. Users on our Starter plan get access to Medium size machines, and Pro and Enterprise customers get access to Large and XL sizes respectively.
What kind of applications can I run on my Linux build environment with Bitrise?
Linux in the cloud enables you to build, execute, test, sign, and deploy Android apps and cross-platform projects. For a full list of supported applications, check out our stack reports.
Can I use a private network?
Yes, we support all kinds of hosting and deployment requirements for enterprise customers. For more info, check out our Build Platform options.
How many builds can I run on Linux machines?
The number of builds you can run depends on your Bitrise plan. We cater to everyone from hobbyists to global enterprises. Our Starter plan allows unlimited usage with up to 3 concurrent builds. For more info, check out pricing.
Why does Bitrise Build Hub offer non-standard Linux machine sizes?
Most providers only offer standard doubling increments (2, 4, 8, 16, 32). Build Hub is the only provider with granular Linux sizing: 4, 6, 8, 14, 16, 24, 32, and 48 vCPU on AMD EPYC Zen4/Zen5 processors, with custom configurations up to 96 vCPU. This matters because more cores do not always mean faster builds. In benchmarks, a 14-core Build Hub machine completed an Android build 31% faster than a 16-core GitHub hosted runner because the vCPU count matched the actual Gradle dependency graph, avoiding performance degradation from administrative overhead. Granular sizing means you pick the machine that fits your workload instead of overpaying for the next size up. Your Android builds on 6 vCPU do not pay for 8.