CI, app builds and device tests on the Mac you already own.
One app runs your GitHub Actions workflows, builds your iOS and Android apps and tests them on simulators, emulators and real phones. You watch it from anywhere.
Failed at “Tap Pay”. Watch the video of the run.
Illustration of the dashboard, with sample data.
GIT AI is free and the Mac is yours. Hosted Mac minutes cost $0.062 to $0.24.
It runs your run steps and the common actions: checkout, cache, artifacts, setup. No new pipeline language.
Secrets and signing keys are never sent to our service.
What one Mac mini did for us last month.
We build GIT AI and our other projects on one Mac mini. These are its numbers, recounted at every release.
At the GitHub-hosted macOS rate, $0.062 a minute, that time is up to $702. Our Linux jobs would have cost less.
533 of 578 cache and Turbo lookups. The Mac keeps its caches between runs, so most steps start warm.
Test executions that ended green, out of 16,696 different tests.
Counted on the Mac itself, 19 October to 18 November 2026. Totals only: GIT AI sends no usage data from your Mac, so we have no numbers about anyone else.
Why teams with a Mac choose it.
Nothing per minute
Hosted Mac runners bill every build minute. Your own Mac is already paid for, and it is faster with a warm cache.
Secrets and signing keys stay on the Mac
Your code is checked out and built on your machine. Secrets and signing keys are never sent to our service.
Set up in minutes
Install one app. No agents to host, no new pipeline language.
Built for mobile
Simulators and emulators kept ready, real devices, app flows with video, signing, and upload to App Store Connect and Google Play.
The Mac decides who opens it
Signing in is not enough. Each Mac asks on its own screen before anyone can open it from the web.
Works without the cloud
Runs start and finish on the Mac. If our service is down, your builds and tests keep going.
Your Macs work as one CI.
Add a second Mac and the jobs spread out by themselves. Your code, keys and signing stay on your Macs.
Several Macs, one queue
- Add a Mac with a one-time code. The Macs talk to each other over mutual TLS.
- Each job goes to a Mac that can run it: its labels, Xcode version and attached devices first, then free capacity and a warm cache.
- Device tests are split across the simulators and emulators of every Mac.
- Helper Macs open no port: they fetch work from the main Mac. On different networks, the service relays traffic it cannot read.
- Signing and store uploads always run on the main Mac.
Security
- Linux jobs run in a container that is removed afterwards. Pull requests from forks run in a macOS VM, with no secrets.
- Signing identities and secrets never leave your Mac, and secrets are masked in logs.
- A change asked for from the web (a project, a key, a secret) waits until someone presses Allow on the Mac.
- Keys have scopes, expire in 7 to 90 days and are stored only as hashes. Every remote action goes into the Mac’s own log.
- Sign-in with Google or GitHub plus a passkey or a code. The Mac trusts only pinned certificates, and updates are signature-checked.
Runs what your workflow already runs
Your GitHub Actions files, as they are. A few need small edits.
From a push to a build you can ship
Gates read what your run produced and report on the pull request. You choose which of them block a merge.
| Stage | What happens | When |
|---|---|---|
| 1. CI | Your own workflow: format, lint, build, tests. With the affected step, only what the change touches. | On a push or a pull request |
| 2. QA gate | Judges the tests that ran: every job ran, none failed, no new flaky tests, no test quietly dropped. | As results arrive |
| 3. Build gate | Every build succeeded, each file has a checksum, the signature checks out, the version is higher than the last. | Before delivery |
| Security gate coming | Secrets, dependencies, workflow rules. | With the QA gate |
| Documentation gate coming | Release notes, API document, links. | With the QA gate |
What a Mac build minute costs.
| Where it runs | Per minute | Source, date read |
|---|---|---|
| GIT AI on your Mac | Nothing. GIT AI is free and the Mac is yours | — |
| GitHub-hosted macOS runner | $0.062 | docs.github.com, 17 November 2026 |
| Codemagic, Mac mini M2 | $0.095 | codemagic.io/pricing, 17 November 2026 |
| Buildkite, hosted Mac | $0.12 to $0.24 | buildkite.com/pricing, 12 November 2026 |
Next to hosted CI.
| GIT AI on your Mac | Hosted CI with Mac machines | |
|---|---|---|
| Where the code is built | On your machine | On the provider's machines, or on agents you host and maintain |
| Secrets | Stay on the Mac | Stored with the provider |
| Real phones and your own simulators | Yes, the ones on your desk | Simulators on a fresh machine each time |
| Setting it up | Install an app | Write pipelines, manage agents or minutes |
What hosted CI does better
Any number of machines at once, and nothing of yours to keep running. GIT AI is for a team that has a Mac and wants it to do the work.
Three steps.
Install the app on a Mac
It finds Xcode, Android tools and your projects, and says what this Mac can build.
Push, or press Run
Your workflows run on the Mac. The result goes back to the pull request as a check.
Watch from anywhere
Sign in with Google or GitHub and open the Mac's dashboard from a phone. An AI assistant can run your checks too.
Shipped lately.
0.4.32 · 17 November 2026
Add a Browser… is in the menu: one click opens this Mac's page in your browser and pairs it.
0.4.31 · 16 November 2026
Add a project from the web: pick the repository and the Mac it runs on.
0.4.30 · 16 November 2026
Linux builds in a container are fast and no longer killed.
Before you install.
What does it cost?
GIT AI is free, forever. The Mac is yours, so there is nothing per minute either.
What does it need?
A Mac, Apple silicon or Intel. A Mac mini without a monitor works: it can be set up from a phone.
What do you see of my code?
Nothing. The code is checked out and built on your Mac. Our service signs you in and carries the dashboard to your browser.
Does it run every GitHub Action?
It runs your run steps and the common actions: checkout, cache, artifacts, setup. A step it cannot run on the Mac is named in the log.