iOS and Android, side by side.
No more waiting on one platform before the other starts.
QA builds for their own devices.
Testers trigger and download builds. Only your build team can change a pipeline.
For mobile studios on Unreal Engine
iOS and Android. One build run. Nobody babysitting a Mac.
Unreal on mobile is hard. Shipping it shouldn't be. SpeedrunCI builds, signs and packages your game for iOS and Android in one run, then sends it to the App Store and Google Play.
iOSAndroidApp StoreGoogle Play
main · release/1.4 · example runiOS + Android in parallel
iOSGame.ipa · signed on mac-runner-02
queuedAndroidGame.aab + asset packs · signed
queuedApp Storeupload to App Store Connect
queuedGoogle Playupload to Play Console
queuedTriggered by QA from the browserPinged in #builds
The mobile tax
Every mobile team pays it. Nobody budgets for it.
Each one is small. Together they eat the week before every release.
- TaxHandled
The Mac mini that signs every iOS build, and the one person whose keychain has the certificates.
Signing runs on a registered Mac runner, in a temporary keychain wiped after every build. - TaxHandled
The Android build is over the store size limit again, and the asset packs need rebuilding by hand.
Switch on App Bundle output and every run produces a signed AAB with Play Asset Delivery packs. - TaxHandled
Two platforms, two cooks, one queue. Android waits while iOS signs.
iOS and Android build at the same time. - TaxHandled
CI went green. The build still won't install on a real device.
Success means a signed package you can install, not a passing step. - TaxHandled
QA asks an engineer for a build. The engineer is in the middle of something.
QA presses build themselves. They can't touch the pipeline.
Every target
One run. Everything the stores ask for.
Signed without anyone at a Mac.
iOS builds route to a registered Mac runner. Certificates load into a temporary keychain that's wiped the moment the build finishes.
Out: signed .ipaStore-ready bundles.
Switch on App Bundle output for a signed Android App Bundle with Play Asset Delivery packs, so size limits stop being a release-week problem.
Out: signed .aab + asset packsStraight to the stores.
Signed builds go up to App Store Connect and Google Play. Nobody downloads a build just to upload it again.
Out: store uploads for both platformsOn testers' phones the same day.
QA triggers a build, downloads it and installs it on their test devices. Your build team keeps control of the pipeline.
Out: a ping in your team chat when it’s readyDelivers toApp StoreGoogle Play
Real phones.Real players.Same morning.
Yesterday's change, signed and on the team's phones before the morning playtest.
Signed buildsiOS + AndroidSame day
How mobile teams use it
Built for how your team already works.
Bring the Macs you have.
Register a Mac as a runner with the SpeedrunCI agent. It handles iOS signing from then on.
Pings where you already talk.
Build status lands in Slack, Discord or Microsoft Teams.
Build from inside Unreal.
Trigger and download builds from the editor toolbar with the free plugin on Fab.
Keep your current CI. Add capacity when you need it.
Your machines build first. Ours take the overflow in release week. Or run the whole platform inside your own AWS or Azure account.
From a pilot studio
“I see this as the tool that finally lets artists and designers test their own assets and builds, instead of waiting on an engineer every time.”
Technical DirectorPilot Studio
Case studyFree pilot
Try it on your next release. Free.
We set it up on your real project. You judge it on builds that install on real phones.
No commitment. Your current setup keeps running.
- 1
30 minutes on your release
Devices, stores, release dates and how you sign today.
- 2
We connect one project
Hybrid or fully managed. Your existing pipeline keeps working.
- 3
Builds on real phones
Signed for iOS and Android. Then you decide.
Questions
What mobile leads ask first.
Do we need our own Macs for iOS?
No. iOS builds can run on Macs in our cloud, or on a Mac you already have, registered with the SpeedrunCI agent. Either way, certificates load into a temporary keychain that's wiped after every build.
Does it handle Play Asset Delivery?
Yes. Switch on App Bundle output and each Android run produces a signed App Bundle with Play Asset Delivery packs.
Can we keep our current CI?
Yes. With hybrid, your machines build first and ours take the overflow. Nothing you have needs to change.
What does it cost?
The pilot is free. After it, you get a number based on your team and how you deploy.
Ship to every phone.
Start with one project and your next release.