XenoCIGitHub Actions runners
Same commit, two runners.
XenoCI's log finished first
Real logs of the same build on 2 vCPU each. GitHub Actions had its cache on
Public repositories run free on Linux 2 vCPU, one job at a time per organization
WHYIsn't the GitHub Actions free tier enough?
The free minutes are there.
The waiting is the problem
GitHub Actions is free for public repositories, and private ones get $12 of minutes a month. Teams still switch, for three reasons
01
Time spent waiting on builds
The same build takes 2m 16s on GitHub Actions and 39s on XenoCI. At 20 builds a day, that is 32m 20s back
3.5xfaster
02
A cache that barely helps
Turning on the GitHub Actions cache took the build from 2m 22s to 2m 16s, 6 seconds saved. On XenoCI it drops from 1m 10s to 39s
31ssaved by the cache
03
Mac minutes run out fast
At $0.062 a minute for macOS, the free $12 lasts 193 minutes. That is 96 iOS builds a month
2.70xfaster iOS builds on the M4
SPEEDSpeed
Measured 2026-11-03Change only runs-on,
and the same build runs over 2x faster
We ran the same workflow side by side on GitHub Actions standard runners and on XenoCI
iOS build
xcodebuild2.70x
Docker build
docker build2.39x
Swift build
swift build1.93x
CACHECache and sticky disks
From the second build on,
3x to 6x faster
Builds run on AMD Ryzen 9 9950X3D-class CPUs, with the previous build attached
One runs-on lineNo cache settings needed
Ryzen 9 9950X3D-class CPUFaster at the same 2 vCPU
104 MB cache in 0.8 s6.8 s on GitHub Actions
0 Swift files recompiled3,274 every time on GitHub Actions
DOGFOODWe use it ourselves
We build XenoCI
on XenoCI runners
Every change to the XenoCI runner code is built on XenoCI runners. A project with 132 npm packages and a 1.5 GB Docker image finishes in under 30 seconds
xenoci-4vcpu-ubuntu-240428.8s- Source
- 7,468 files92MB
- npm packages
- 132node_modules 398 MB, 16,274 files
- npm cache
- 104MBattached in 0.9 s
- Next build output
- 317MB
- Docker image
- 1.51GB11 layers
- Attached Docker disk
- 24.7GBincl. 19.6 GB build cache
STICKY & CACHESticky disks and cache
Any size attaches in 0.7 s,
with no storage fee
A sticky disk is attached whole, not downloaded and unpacked, so the attach time stays flat as your project grows
Download and untarGitHub Actions-style cache, 1 GB25.2s
XenoCI sticky disk1GB0.7s
XenoCI sticky disk5GB0.7s
100 GB per organizationCache and sticky disks combined
Least recently used goes firstWhat you use stays, the rest is cleaned up
Cleared after 7 idle daysNothing to switch on or off
Builds never stallShort on space, that one job skips saving
RUNNERSMac and Linux runners
M4 Macs, Linux up to 16 cores,
picked with one runs-on line
Mac runs on Mac mini M4, Linux on Ubuntu 24.04. Public repositories run free on Linux 2 vCPU, one job at a time per organization. Paid usage is currently available for Korean organizations
Mac mini M4
5 vCPU, 7 GB memory, Xcode 27.0 and 26.6, iOS Simulator
runs-on: xenoci-standardGitHub Actions macos-latest: $0.062 per minute
Mac mini M6
6 vCPU, 7 GB memory
runs-on label at launchDetails at launch
2 vCPU
8 GB memory, 80 GB disk
Freepublic repositories
xenoci-2vcpu-ubuntu-24044 vCPU
16 GB memory, 80 GB disk
PaidKorean organizations
xenoci-4vcpu-ubuntu-24048 vCPU
32 GB memory, 160 GB disk
PaidKorean organizations
xenoci-8vcpu-ubuntu-240416 vCPU
64 GB memory, 750 GB disk
PaidKorean organizations
xenoci-16vcpu-ubuntu-2404SELF-HOSTEDIf you run self-hosted runners
Spend runner upkeep time
on your product
On your own Mac minis or servers, hardware, updates, disks and security are all your team’s job. Move to XenoCI and that work goes away
No hardware to buy
No Mac minis to buy or replace. Runners exist only while you build
No updates to run
We keep macOS and Xcode current. Right now: Xcode 27.0 and 26.6
No full disks
We attach caches and sticky disks, and clear them after 7 idle days
Nothing leaks between jobs
Every job gets a clean machine that is wiped afterwards. No files or secrets carry over
Faster chips
M4 with 5 vCPU for Mac, up to 16 vCPU for Linux
One line to switch
No runner registration, tokens or labels. One runs-on line, and the console opens the PR
What your team does when self-hosting
- Buying, replacing and fixing hardware
- macOS, Xcode and runtime updates
- Disk cleanup and cache management
- Runner registration, tokens, labels, restarts
- Clearing files and secrets left between jobs
On XenoCI
- Public repositories run free on Linux 2 vCPU
- XenoCI handles updates, disks and cache
- A clean machine for every job, wiped afterwards
- Job logs and usage right in the console
- Paid usage is currently available for Korean organizations
STARTGet started
Switching takes
one PR
Default cache folders for npm, pip and Gradle, plus Docker layers, attach with no setup. Cache steps already in your workflow can stay; the XenoCI cache serves them
- 1Sign in with GitHub
Sign in at runner.xenoci.com with your GitHub account
- 2Install the app on your organization
Public repositories run free on Linux 2 vCPU right away
- 3Pick the jobs to move
Choose a repository and its jobs; a recommended runner size is preselected
- 4Merge the PR
The console opens a PR that changes runs-on. Merge it and the next build runs on XenoCI
jobs: build: - runs-on: ubuntu-latest+ runs-on: xenoci-2vcpu-ubuntu-2404 steps: - uses: actions/checkout@v4 - run: npm test
Public repositories
Free
Your next build
runs faster
Paid usage is currently available for Korean organizations
Start with GitHub