CI Runnerscirunners.org
Head-to-head

Cilicon vs Tart

Answer in brief

Cilicon suits teams with one or a few dedicated Apple silicon Macs that want ephemeral self-hosted runners without an orchestration layer. Tart suits teams that run their own Apple silicon Macs and want scriptable, image-based macOS VMs for GitLab CI or Buildkite jobs. Cilicon is an open-source project you run yourself for GitHub Actions, GitLab CI and Buildkite; Tart is a product that runs runners in your own cloud account or on your own hardware for GitLab CI, Buildkite and GitHub Actions.

By the CI Runners editors · Updated

Key differences between Cilicon and Tart

  • Type: Cilicon is an open-source project you run yourself; Tart is a product that runs runners in your own cloud account or on your own hardware.
  • Operating systems: Only Tart documents Linux.
  • Isolation: Cilicon: macOS VM. Tart: Apple Virtualization VM.
  • Open source: Cilicon is open source (MIT); Tart is not.

What they have in common

  • Both run GitHub Actions, GitLab CI and Buildkite jobs.
  • Both document macOS runners.
  • Both document arm64 runners.
  • Both use a virtual machine per runner.
  • Both give every job a fresh environment.
  • Both can be self-hosted.

Cilicon vs Tart at a glance

AttributeCiliconTart
What it isOpen-source macOS app that runs ephemeral CI virtual machines on a single Apple silicon Mac using Apple’s Virtualization framework.Virtualization toolset for macOS and Linux VMs on Apple silicon, with OCI-registry images and the Orchard orchestrator for clusters of Macs.
TypeOpen-source projectRuns in your cloud or on your hardware
CI systemsGitHub Actions, GitLab CI, BuildkiteGitLab CI, Buildkite, GitHub Actions
Operating systemsmacOSmacOS, Linux
Architecturesarm64arm64
IsolationEach job runs in an ephemeral macOS virtual machine created with Apple’s Virtualization framework and provisioned over SSHJobs 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 jobYesYes
HardwareAn Apple silicon Mac that you supply; the README recommends a machine fully dedicated to the task.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)The README describes VM performance as near-native (project claim)The Tart README says Apple’s Virtualization.Framework gives near-native performance (project claim)
Runner sizesNot documentedNot documented
CachingNot documentedVM 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 cachingNot documentedNot documented
GPUNot documentedNot documented
ConcurrencyOne VM at a time per host; running two VMs in parallel is listed under ideas for the futureThe 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 IPsNot documentedNot documented
SSH into running jobsNot documentedYes
PricingFree and MIT-licensed; you supply the Mac.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 tierNot documentedFree to use under FSL-1.1-ALv2; the earlier paid tiers no longer apply, per tart.run
Open sourceYes (MIT)No (FSL-1.1-ALv2)
Self-host / your cloudYes / YesYes / Yes
ComplianceNot documentedNot documented
RegionsWherever your Mac runsWherever your Apple silicon hosts run
Company headquartersNot documentedSan Francisco, California, United States
Good fit forTeams with one or a few dedicated Apple silicon Macs that want ephemeral self-hosted runners without an orchestration layerTeams 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 Cilicon

  • You have a spare Apple silicon Mac and want ephemeral runners on it with one app and one config file
  • You want MIT-licensed tooling with no licence fee
  • You use GitHub Actions, GitLab or Buildkite, each of which has a built-in provisioner
  • You want to reuse prebuilt macOS and Xcode images published in the Tart format

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

  • Cilicon: Running two VMs in parallel is listed as a future idea, so a host runs one job at a time
  • Cilicon: Logging and monitoring are listed as ideas for the future
  • 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 Cilicon profile and Tart profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Cilicon or Tart better?
Neither is better for every pipeline. Cilicon suits teams with one or a few dedicated Apple silicon Macs that want ephemeral self-hosted runners without an orchestration layer. Tart suits teams that run their own Apple silicon Macs and want scriptable, image-based macOS VMs for GitLab CI or Buildkite jobs.
What is the difference between Cilicon and Tart?
Cilicon is an open-source project you run yourself; Tart is a product that runs runners in your own cloud account or on your own hardware. Only Tart documents Linux. Isolation is macOS VM on Cilicon and Apple Virtualization VM on Tart. Cilicon is open source (MIT); Tart is not.
Which is open source, Cilicon or Tart?
Cilicon is open source (MIT); Tart is not open source.
How do Cilicon and Tart isolate jobs?
Cilicon: Each job runs in an ephemeral macOS virtual machine created with Apple’s Virtualization framework and provisioned over SSH. Tart: 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.
How does Cilicon pricing compare with Tart?
Cilicon: Free and MIT-licensed; you supply the Mac. Tart: 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. Rates change, so check the Cilicon and Tart pricing pages before deciding.
Is Cilicon or Tart faster?
We have not benchmarked them, and speed depends on the workload. What each provider says: Cilicon: The README describes VM performance as near-native (project claim). Tart: The Tart README says Apple’s Virtualization.Framework gives near-native performance (project claim).
Where do Cilicon and Tart runners run?
Cilicon is an open-source project you run yourself (Bare metal). Tart is a product that runs runners in your own cloud account or on your own hardware (Bare metal).

Sources

  1. github.com/traderepublic/Cilicon
  2. github.com/traderepublic/Cilicon/blob/main/README.md
  3. github.com/traderepublic/Cilicon/releases
  4. cirruslabs.org/
  5. tart.run/
  6. tart.run/quick-start/
  7. tart.run/blog/2023/02/11/changing-tart-license/

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). Cilicon vs Tart. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/cilicon-vs-tart/