Orka vs Tart
Orka suits teams that want a dedicated, orchestrated fleet of Macs for ephemeral macOS CI across several CI systems. Tart suits teams that run their own Apple silicon Macs and want scriptable, image-based macOS VMs for GitLab CI or Buildkite jobs. Orka is a product that runs runners in your own cloud account or on your own hardware for GitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines and TeamCity, priced at From $109/mo per hosted Mac mini (Orka by quote); Tart is a product that runs runners in your own cloud account or on your own hardware for GitLab CI, Buildkite and GitHub Actions.
Key differences between Orka and Tart
- CI systems: Only Orka documents Jenkins, Azure Pipelines and TeamCity.
- Operating systems: Only Tart documents Linux.
- Isolation: Orka: macOS VM. Tart: Apple Virtualization VM.
What they have in common
- Both companies are based in the United States.
- Both are products that run runners in your own cloud account or on your own hardware.
- Both run GitHub Actions, GitLab CI and Buildkite jobs.
- Both document macOS runners.
- Both document arm64 runners.
- Both use a virtual machine per runner.
- Neither is open source.
- Both can be self-hosted.
Orka vs Tart at a glance
| Attribute | Orka | Tart |
|---|---|---|
| What it is | Kubernetes-based orchestration of macOS VMs on Apple silicon, run in MacStadium data centers, on AWS EC2 Mac or on your own Macs. | Virtualization toolset for macOS and Linux VMs on Apple silicon, with OCI-registry images and the Orchard orchestrator for clusters of Macs. |
| Type | Runs in your cloud or on your hardware | Runs in your cloud or on your hardware |
| CI systems | GitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines, TeamCity | GitLab CI, Buildkite, GitHub Actions |
| Operating systems | macOS | macOS, Linux |
| Architectures | arm64 | arm64 |
| Isolation | Jobs run in macOS virtual machines on Apple silicon Mac nodes; the GitHub runner creates a VM per job and tears it down afterwards, while the GitLab, Buildkite and Jenkins integrations offer both permanent and per-job (ephemeral) agents | Jobs run in macOS or Linux virtual machines created with Apple’s Virtualization.Framework; the documented GitLab executor and Buildkite plugin run each job in an isolated ephemeral VM cloned from an image |
| Fresh environment per job | Not documented | Yes |
| Hardware | MacStadium lists hosted Mac mini (M2, M2 Pro, M4, M4 Pro) and Mac Studio (M1 Max, M2 Ultra) configurations; Orka 4.0 runs on Apple silicon nodes only. | Runs on Apple silicon Macs with macOS 13.0 (Ventura) or later; Orchard workers run on macOS and the Orchard controller can also run on Linux or Kubernetes. |
| Performance (vendor claim) | Not documented | The Tart README says Apple’s Virtualization.Framework gives near-native performance (project claim) |
| Runner sizes | CPU and memory are set per VM config; listed hosted Macs range from an M2 Mac mini (8 cores, 8 GB) to an M2 Ultra Mac Studio (24 cores, 128 GB) | Not documented |
| Caching | Orka images are OCI images pulled from a registry, and the docs describe pre-caching images on nodes. For GitLab, cache restoration needs the gitlab-runner binary inside the VM image. | VM images are pushed to and pulled from OCI-compatible container registries. The GitLab executor example sets builds and cache directories inside the VM. |
| Docker layer caching | Not documented | Not documented |
| GPU | Not documented | Not documented |
| Concurrency | Bounded by the Mac nodes in the cluster; the GitHub runner reports up to MAX_RUNNERS (default 9000) and GitLab concurrency is set in config.toml | The Orchard announcement says a single host allows a maximum of two virtual machines at a time; Orchard schedules VMs across a cluster of hosts |
| Static IPs | Not documented | Not documented |
| SSH into running jobs | Yes | Yes |
| Pricing | Orka for DevOps pricing is not published (contact sales; Orka is also sold through AWS Marketplace). Individual hosted Macs are listed monthly, from $109 (M2 Mac mini, 8 GB) and $149 (M4 Mac mini, 16 GB) to $449 (M2 Ultra Mac Studio, 128 GB). | No licence fees: Cirrus Labs said on April 7, 2026 that it had stopped charging licensing fees for Tart, Vetu and Orchard. You supply and pay for the Mac hardware. |
| Free tier | No free trial on individual hosted Macs; MacStadium says a proof of concept may be possible for large migrations | Free to use under FSL-1.1-ALv2; the earlier paid tiers no longer apply, per tart.run |
| Open source | No | No (FSL-1.1-ALv2) |
| Self-host / your cloud | Yes / Yes | Yes / Yes |
| Compliance | ISO 27001, 27017 and 27018; SOC 1 and SOC 2 Type 2 (as stated by MacStadium) | Not documented |
| Regions | MacStadium data centers in Atlanta, Las Vegas and Dublin; or your own AWS account or premises | Wherever your Apple silicon hosts run |
| Company headquarters | Atlanta, Georgia, United States | San Francisco, California, United States |
| Good fit for | Teams that want a dedicated, orchestrated fleet of Macs for ephemeral macOS CI across several CI systems | Teams that run their own Apple silicon Macs and want scriptable, image-based macOS VMs for GitLab CI or Buildkite jobs |
Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose Orka
- You want per-job macOS VMs on Macs dedicated to your team rather than a shared runner pool
- You use more than one CI system: MacStadium documents GitHub Actions, GitLab, Buildkite, Jenkins, TeamCity and Azure Pipelines
- You need the same platform in a vendor data center, in your AWS account or on-premises
- You want Android emulators next to macOS VMs on the same Mac fleet (Orka 4.0)
Reasons to choose Tart
- You already own or rent Apple silicon Macs and want to run CI jobs in disposable VMs on them
- You want VM images versioned and distributed through an OCI container registry
- You use GitLab CI or Buildkite, for which Tart documents an executor and a plugin
- You need to schedule VMs across many Macs: Orchard provides a controller, workers and a REST API
Trade-offs to check first
- Orka: Orka for DevOps pricing is not published; MacStadium directs buyers to sales
- Orka: MacStadium states it does not offer free trials on individual hosted Macs
- Tart: FSL-1.1-ALv2 is a source-available licence that excludes Competing Use; each version becomes Apache-2.0 on the second anniversary of its release
- Tart: A single host allows a maximum of two virtual machines at a time, per the Orchard announcement
Run your slowest workflow on both before deciding. See the full Orka profile and Tart profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Orka or Tart better?
What is the difference between Orka and Tart?
Which is open source, Orka or Tart?
How do Orka and Tart isolate jobs?
How does Orka pricing compare with Tart?
Is Orka or Tart faster?
Where do Orka and Tart runners run?
Sources
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 22, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
CI Runners. (2026). Orka vs Tart. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/macstadium-orka-vs-tart/