
macOS
Apple Silicon · ARM64Kiri
Select Kiri when connecting a Mac to your worker pool.
Run multiple jobs on one machine.
Each gets the CPU and memory it needs.
Example allocation. 2 vCPU and 4 GiB are reserved for the host.
Job metrics & provisioning
Use each job’s run history to size its next CPU and memory request. Existing jobs keep their allocation until they finish.
northstar/storefrontILLUSTRATIVE DATA| Run | Time (s) | Peak vCPU | Peak GiB | Request vCPU | Request GiB |
|---|---|---|---|---|---|
| #485 | 0.5500 | 1.23 | 2.43 | 4 | 8 |
| #486 | 1.5075 | 1.30 | 2.54 | 4 | 8 |
| #487 | 2.4650 | 1.37 | 2.34 | 4 | 8 |
| #488 | 3.4225 | 1.21 | 2.45 | 4 | 8 |
| #489 | 4.3800 | 1.28 | 2.56 | 4 | 8 |
| #490 | 5.2200 | 1.35 | 2.36 | 4 | 8 |
| #491 | 6.0600 | 1.19 | 2.47 | 4 | 8 |
| #492 | 6.6300 | 1.26 | 2.58 | 4 | 8 |
| #493 | 7.4700 | 1.33 | 2.38 | 4 | 8 |
| #494 | 8.3100 | 1.40 | 2.49 | 4 | 8 |
| #495 | 8.8800 | 1.24 | 2.60 | 4 | 8 |
| #496 | 9.7200 | 1.31 | 2.40 | 4 | 8 |
| #497 | 11.1400 | 1.38 | 2.51 | 2 | 4 |
Worker runtimes
Choose a runtime for each worker. A platform team can pool Mac build machines, Windows PCs, and Linux rack servers, then route each job to the operating system and capacity it needs.

Select Kiri when connecting a Mac to your worker pool.

Run isolated Linux containers with capacity shared across concurrent jobs.

Run Windows containers with Hyper-V isolation.
Start a fresh Windows VM from a prepared checkpoint, without Docker.
Workflow routing
Choose a platform or list alternatives in your workflow. Each label sets its own CPU and memory. MARS picks one matching option for the job.
runs-on: mars-ubuntu-24-2vcpu-2gUbuntu 24 / x64 · 2 vCPU · 2 GiB RAM.
runs-on:
- mars-ubuntu-24-2vcpu-2g
- mars-windows-x64-2vcpu-2gEither platform · 2 vCPU + 2 GiB RAM on the selected pool.
runs-on:
- mars-ubuntu-24-2vcpu-4g
- mars-windows-x64-2vcpu-4g
- mars-macos-arm64-2vcpu-4gUbuntu, Windows or macOS · 2 vCPU + 4 GiB RAM on one pool.
runs-on:
- mars-ubuntu-24-1vcpu-2g
- mars-windows-x64-2vcpu-10gUbuntu: 1 vCPU / 2 GiB RAM. Or Windows: 2 vCPU / 10 GiB RAM.
runs-on: mars-any-x64-2vcpu-2gAny compatible x64 pool · 2 vCPU · 2 GiB RAM.
Each job runs once. Disk follows pool policy.
DEVELOPMENT SANDBOXES
Open the same branch in isolated Windows, Linux, and macOS workspaces. Build and test it yourself, or give an AI agent control of a sandbox to run commands, edit code, and check the results.
Explore mobile testingHosted alternatives
Each runtime needs a compatible host. macOS sandboxes run on a Mac.
Mobile testing
Build your Expo app locally with Expo CLI. With compatible workers, your team can test its Android and iOS builds on virtual devices it hosts. This gives you a self-hosted alternative to EAS Build, Expo Simulators, and other cloud device labs.
AI REVIEW
Give your pull requests a second pair of eyes. Your model can scan the codebase, diagnose CI failures, open an issue or propose a fix in a pull request.
Free plan
Connect one worker for $0 a month and run up to five jobs in parallel. Add capacity on a paid plan as your team grows.