Builds for every platform you ship on
Choose the platform. We handle what it requires.
Every platform has its own environment, SDK, cook settings, packaging rules, and signing requirements. You shouldn’t have to turn each one into a separate infrastructure project.
Run builds in parallel
Multi-platform runs can build several targets in parallel, with each target getting the environment and configuration it needs.
Keep console builds isolated and validated
PS5 and Xbox builds run on dedicated secured agents with SDK presence and certification checks before the build starts.
Console SDK material stays off general-purpose agents, and missing SDKs fail fast instead of breaking later in the build.
Package mobile builds correctly
Android and iOS use the cook formats and packaging steps their platforms require. Android produces a signed AAB with GooglePAD asset packs, while iOS routes to a registered Mac runner.
The platform-specific setup is part of the build, not something someone has to remember to configure.
Sign builds without manual intervention
Xbox, Android, and iOS signing credentials are securely provided when the build needs them.
iOS signs through a temporary keychain that is wiped when the build finishes, so nobody needs to sit at a Mac to get a build signed.
How it works
SpeedrunCI keeps the platform configuration, build environment, and infrastructure together so the build can determine what it needs without your team maintaining the machinery underneath it.
- 01
Choose the target
Select the platform your pipeline should build for. SpeedrunCI routes the work to the appropriate runner and environment.
- 02
Use the right environment
The platform determines the required toolchain, SDK, cook configuration, packaging steps, and other build requirements.
- 03
Produce the artifact
The build packages and signs the result using the platform’s requirements, producing the artifact your team actually needs.
- 04
Run it again, consistently
The same configuration can run again without rebuilding the machine setup or remembering which settings were used last time.
The infrastructure your builds need, already handled
SpeedrunCI keeps the machines, Unreal environments, and CI infrastructure your builds depend on ready to run.
Run without maintaining runners
Use dedicated nodes when you need persistent capacity, or provision ephemeral agents when demand spikes. They go away when the build is done.
Keep Unreal versions ready
Map engine versions to prepared images and choose the version at the project level. Different projects can build against different versions without maintaining separate farms.
Add capacity without buying hardware
Use ephemeral agents alongside warm nodes when demand changes. Scale for a busy week without keeping that hardware around for a quiet one.
Keep the build definition in one place
Your pipeline describes what the build should do. You don’t have to reproduce that logic across CI configuration, runner setup, and machine-specific scripts.
Get a usable artifact, not just a successful build
SpeedrunCI handles the platform-specific work needed to turn a successful Unreal build into an artifact you can actually use.
Produce an encrypted, signed .xvc ready to install on a devkit. Fail-fast checks catch packaging problems before you end up with a build that succeeded but can’t be deployed.
Produce a signed .aab with GooglePAD asset packs and automatic versioning. Every build gets the right versionCode, so Play Console doesn’t reject an upload because that version already exists.
Route builds to a registered Mac and sign them using a temporary keychain that’s wiped when the build finishes. Builds can run and sign without someone sitting at the machine, and credentials don’t stay behind.
