EneyProactive AI for Mac. Free test, 20,000 credits.
Promoted
Bitrise is the leading mobile DevOps platform, empowering over 8,500 brands worldwide including Generali, Shopify, TripAdvisor and BuzzFeed. Bitrise provides a full-stack, vertically integrated mobile DevOps solution that unites the tools, processes and testing frameworks engineering teams need to build best-in-class mobile experiences.
This is the 4th launch from Bitrise. View more
Bitrise Build Hub
Launching today
Coding agents push more code, so your CI runs more builds than ever. GitHub's runners are slow, so every extra build sits in the queue and your team waits with it. Bitrise Build Hub runs those builds on the newest Apple Silicon and high-core Linux instead: 54% faster on iOS, 31% on Android.
PRs come back in minutes, and your app ships sooner. You keep GitHub Actions. Changing one line in your workflow is all it takes to run on the best runners made for mobile.
Free Options
Launch Team / Built With
Bitrise
Maybe I should already know this 😅 but I’m actually curious about the infrastructure behind Build Hub.
Do you guys actually own and operate the physical Mac minis yourselves? And how does the Linux side work? How are you able to keep machines pre-warmed and build startup times low across both macOS and Linux?
Bitrise
@daniel_bodnar91 never too late to learn : )
We sure do, we own and operate the physical machines ourselves. The Macs are Apple silicon Mac minis (M4 and M4 Pro, with M5 Pro coming really soon) that we rack in our own data centres, our own design 'the mini orchard', 32 minis to a 6U chassis on 10 Gigabit Ethernet with NVMe storage. The Linux side is AMD EPYC (Zen4/Zen5) in the same facilities, from small runners up to 192 vCPU.
On the pre-warming, it's the same idea on both platforms: we keep pools of VMs already booted from a clean snapshot, sitting ready. When a job comes in it grabs one of those instead of cold-booting a machine, which is what keeps startup times low. Each VM is ephemeral, it runs your build and gets torn down after, and a fresh one takes its place in the pool.
On the Mac side specifically, we run our own macOS virtualization layer on top of Apple's Virtualization framework. That's what lets us turn those minis into fast, consistent VMs at scale, it's handling millions of builds a month now. Owning the whole stack, hardware, network and virtualization, is exactly why we can keep it fast and be first onto each new Apple silicon generation.
Bitrise
@daniel_bodnar91 and if you're interested in the cable management all of that takes, here's a sneak peak 😍
ProdShort
Congrats, team. What if I’m using Jenkins for running my client builds (it’s still used in bigger companies :). Can I use Build Hub instead?
Bitrise
@amraniyasser At the moment Build Hub doesn’t support Jenkins integrations, but it is on our roadmap. You can try out Bitrise CI in the meantime.
Bitrise
@amraniyasser Jenkins is on the roadmap to discuss. If there is serious interest, ping and let's chat.
Bitrise
Hey 👋 I'm Catherine, I handle product marketing for Bitrise Build Hub.
More and more teams are getting moved onto GitHub Actions, and it's rarely the team's own call, it's decided higher up. Fine in most cases, but mobile teams get overlooked even though they have the most demanding needs: fast Apple silicon, the newest Xcode, an environment set up properly for iOS and Android, which general-purpose runners aren't built for.
So, we made Build Hub. A one line swap (runs-on: macos-latest becomes runs-on: bitrise-m4-pro) and your pipeline runs on machines built for mobile CI/CD.
Our engineers decked out our data centres and built the machines and stacks themselves, tuned for mobile specifically. And it's not just a point solution, Bitrise is an established mobile DevOps platform 🧩(we first launched on Product Hunt in 2014!), so you can add our co-located Build Cache for builds up to 90% faster, and let Release Management ship them to the app stores.
Bitrise
Hola Hunters, I'm Daniel helping out the communication around Build Hub.
When I came across the tagline “Bitrise - Ship Happens” on a cap, it made me think about why shipping actually matters.
There’s an old expression: “when my ship comes in.” - Your ship coming in could literally mean your investment coming in. ( In 522 Magellan’s expedition returned with 381 sacks of cloves, and that surviving cargo was worth more than the five ships originally sent on the voyage. )
For centuries, the ability to ship was directly connected to opportunity, wealth and growth. Crazy, right?
One of the clearest examples is the Dutch.
In the 1600s, a relatively small country became one of the most influential trading powers in the world not simply because it had ships, but because it became exceptionally good at building the infrastructure around shipping.
Better ships.
Better ports.
Better shipyards.
Better warehouses.
Better navigation.
Better financing.
Better systems for coordinating everything around the movement of value.
And as that network grew, more abstract infrastructure had to grow around it.
Banks.
Insurance.
Contracts.
Stock markets.
Standards.
Protocols.
We are still shipping spices, steel, machines and containers across oceans.
But now we also ship code, builds, data, transactions and information.
Shipping never stopped being one of the most important forces in civilization.
It just became more abstract.
And the more abstract the thing you are moving becomes, the more important the infrastructure underneath it becomes.
That is what Build Hub means to me.
And if better infrastructure lets you build faster, it lets everything sitting on top of that infrastructure move faster too.
The Dutch built better infrastructure for moving physical value connecting the world.
Today, we are doing the same thing for digital value.
Different layer. Same principle. Same importance.
Shipping is evolution.
Shipping means evolution, and if you can ship faster, you evolve faster.
And if you can evolve faster, why wouldn't you try it for 14 days free?
Bitrise Build Hub - Ship happens.
Bitrise
@daniel_bodnar91 Daniel, this was so poetic 😅
That's so handy. It makes sense for developers to keep their GitHub Actions config there (if they're happy with it). Just run it on faster machines. Mobile builds need better hardware first. So that's a great start. With Bitrise pipelines, devs can go even further when they're ready.
Bitrise
@ka_4, thanks for your comment, we are are very proud of our cutting edge macOS hardware we provide.
Bitrise
Did you know that with Bitrise Build Hub, you get some extras from the Bitrise Platform? For instance, if performance is critical for you, we offer caching. It's a co-located architecture - storage and compute live in the very same datacenters as our runners, giving a near-zero latency, and no additional egress cost.
Key-Value Cache: it's included, and you get 10x more storage for free, compared to the native GitHub experience. During design and implementation, our main goal was to make the user experience as seamless as possible. The result: you can enable it with one click, and you won't have to change anything in your workflows. It works with native GHA actions. 😎
Build Cache for Bazel, Gradle, Xcode and React Native applications, cutting build times by up to 85–90%. Give it a try for free: https://bitrise.io/platform/build-cache. For development teams at high-scale, we also offer Bazel Remote Build Execution. 🚀
Bitrise
Btw 🏃♂️ we are also pushing to offer M5 Pro and M6 Mac Mini Runners soon.