A fresh macOS VM
Fresh every time.
Entirely for your job.
An isolated environment for every job.
When it ends, the VM and the data in it are cleaned up.
XenoCI01A fresh environment.
XenoCI02Ready for your next job.
XenoCI
Your code, unchanged.
Your build, on a fresh Mac.
macOS CI for your next build.
100 free credits every month.
my-app / build.ymlExample run screen
WORKFLOW
macOSiOS build
CheckoutSource code→BuildXcode→FinishVM cleanup
› runs-on: xenoci-macos› Apple Silicon M4 · 4 vCPU · 8 GiB› Ready for your next build.
Less time on setup.
More time building.
Connect a fresh Mac to the GitHub Actions you already use. With a one-line change, you get macOS and Xcode ready to go. The complex build environment steps back, and your ideas come forward.
XenoCI Runner
Where your code
actually runs.
macOS runners on Apple M4.
4 vCPU. 8 GiB of memory.
Run your build in a fresh VM.
XenoCImacOS runner
Fresh environment.
Every job.
Fresh every time.
GitHub Actions
The way you know.
A natural fit.
Keep your existing steps.
Just switch the Mac they run on.
runs-on:xenoci-macos
Start with one line.
Change the runner name in your current workflow.
jobs:
ios:
runs-on: xenoci-macos
steps:
- uses: actions/checkout@v4
- run: xcodebuild -scheme App buildGitHub ActionsOne-line setup
- 1
Connect GitHub.
Sign in, then install the XenoCI app on your GitHub account.
- 2
Change one runner line.
Set runs-on to xenoci-macos.
- 3
Start your next build.
Your existing build commands run on a fresh Mac.
From app builds
to package tests.
Run the build and test commands you use in GitHub Actions
in an environment with macOS and Xcode ready.
iOS appsEvery code change,
Every code change,
built and tested.
Run your existing Xcode build and test jobs on a fresh macOS runner.
CheckoutFetch the changed code
PassedXcode buildCompile the app
PassedXcode testRun tests
Passed Change passed build and tests
Use case
Verify pull request changes with builds and tests
macOS appsOn a Mac,
On a Mac,
check that your app builds.
Compile apps that need the macOS SDK and confirm the app bundle is produced.
Compile sources Create app bundle
MyApp.appmacOS application
BUILDBuild output produced on macOS
Mac app build complete
Use case
Catch compile errors in a macOS app
Swift packagesPackage changes,
Package changes,
checked by tests.
Run sources and tests together to confirm your changes keep existing behavior.
Package.swiftSources/Tests/
ParserTests Passed
ModelTests Passed
swift test Tests passedUse case
Run tests after changing a library
START SMALL. BUILD WHAT’S NEXT.
Start with free credits,
add more as you need.
Your 100 free credits each month are used first. 1 credit per M4 minute. Credits are deducted per second for the time actually run, with no minimum charge.
100free credits every month1credit per M4 minute
Extra credits are KRW 100 per credit. Purchased credits never expire.
GOOD TO KNOW
Before you start,
good to know.
For detailed setup,
see the getting started guide.
Can I use it without a Mac?
Yes. Builds run in macOS VMs on Apple Silicon Macs operated by XenoCI. You don't need to provide a Mac yourself.
How do I connect it to GitHub Actions?
Install the XenoCI app on your GitHub account, then change runs-on in your workflow to xenoci-macos. The rest of your steps can stay as they are.
Is a fresh environment created for every build?
A fresh macOS VM is created for every job. When the job ends, the VM and the code, secrets and artifacts in it are deleted.
How are free credits used?
The 100 free credits provided each month are used first. When they run out, new jobs wait; they continue on purchased credits only if you turn on extra credits.
How is usage calculated?
1 minute of M4 run time is 1 credit, deducted per second. There is no minimum charge, so even a short job counts only the time it actually ran.
XenoCI
A reason to look forward
to your next build.
Start with 100 free credits every month.
Start for free