What is Orchard in Tart Virtualization?

Updated

Orchard is the orchestration component of Tart Virtualization, used to run macOS and Linux virtual machines at scale rather than one at a time on a single host. It is the right fit when you have outgrown local tart run workflows and need a cluster of machines to schedule VM workloads across. If you only build and run VMs on one Apple Silicon Mac, you do not need Orchard.

Where Orchard sits in the toolset

Tart itself is described as a virtualization toolset to build, run and manage macOS and Linux virtual machines on Apple Silicon, with native performance and remote storage for VMs. Orchard extends that from a single machine to a cluster. The site groups it under "Orchestration" with its own documentation set, separate from the core Tart and Integrations sections.

What Orchard covers

Based on the published documentation structure, Orchard includes:

  • Quick Start — the entry path for getting an Orchard deployment running.
  • Architecture and Security — how the cluster is put together and what security properties it assumes.
  • Deploying Controller — standing up the controller component.
  • Deploying Workers — adding worker machines that actually run VM workloads.
  • Using Orchard CLI — a command-line interface for managing the cluster.
  • Managing the Cluster — day-to-day cluster operations.
  • Integrating with the API — programmatic access so Orchard can be driven by your own tooling.
  • FAQ — a dedicated troubleshooting and common-questions page.

The controller/worker split is the key mechanism: the controller coordinates, and workers supply the compute that hosts VMs. That is what allows VM capacity to grow beyond a single Mac.

How it relates to CI and automation

Tart's integration surface already lists GitHub Actions, GitLab Runner, Buildkite and Packer. Orchard is the layer that makes those integrations viable when the number of concurrent VM jobs exceeds what one machine can host — the controller and workers provide the pool, and the API plus CLI provide the control points for automation. If your CI pipeline currently queues because a single Mac can only run so many simulators or builds at once, Orchard is the part of the product aimed at that problem.

When to choose Orchard, and when not to

Situation Orchard appropriate?
Building and testing VMs on one Apple Silicon Mac No — core Tart is sufficient
CI jobs queueing because one host is saturated Yes — workers add capacity
Need programmatic control over a VM fleet Yes — API integration is documented
Need remote VM storage Not specifically — that is a Tart feature, not Orchard
Want a managed hosted service Not established by the available material

Practical starting point

Read the Orchestration Quick Start first, then Architecture and Security before deploying anything, since the controller/worker model determines your network and machine layout. Use the CLI for interactive cluster management and the API for wiring Orchard into existing automation. Keep the FAQ open during initial deployment; it is the documented place for issues that come up.

One caution: the available site material does not state pricing, licensing terms for Orchard specifically, or hardware minimums beyond the Apple Silicon requirement for Tart. Check the Support & Licensing and Legal sections of the site before committing to a deployment plan.