Skip to main content
Version: v4 (current)

Introduction

What Does Orchestrator Do?

Orchestrator runs Unity builds on cloud infrastructure. Start jobs from GitHub Actions, the command line, or any CI system. Orchestrator provisions a cloud environment, sends your project to be built, and streams results back.

  Your Machine / CI                  Cloud Provider
┌──────────────┐ git push ┌─────────────────┐
│ GitHub │ ─────────────────►│ AWS Fargate │
│ Actions, │ │ Kubernetes │
│ GitLab CI, │ ◄─────────────────│ Local Docker │
│ CLI, etc. │ build artifacts │ │
└──────────────┘ └─────────────────┘
│ │
│ Orchestrator handles: │
│ * Provisioning │
│ * Git sync + LFS │
│ * Caching (S3 / rclone) │
│ * Automatic cleanup │
└───────────────────────────────────┘

Orchestrator supports large projects with first-class Unity support and native cloud services like AWS Fargate and Kubernetes.

✅ Why Orchestrator?

  1. Flexible and elastic — balance speed and cost, configure CPU, memory, and disk per build
  2. Scale from zero — no idle servers, pay only while builds run
  3. Easy setup — minimal configuration to get started
  4. Extensible — run custom hooks, or bring your own provider plugin

❌ When You Don't Need It

  • Your project is under 5 GB — standard GitHub runners should work fine
  • You have dedicated build servers already running

📦 Supported Providers

Cloud ProviderDescription
AWS FargateFully managed containers on AWS. No servers to maintain.
KubernetesRun on any Kubernetes cluster.
Local DockerDocker containers on the local machine.
LocalDirect execution on the host machine.

See Providers for the full list including custom and community providers.

🖥️ Supported Platforms

PlatformDescription
GitHub ActionsFirst-class support with Checks.
GitLab CIVia the Command Line mode.
Command LineRun from any terminal or script.
Any CI systemAnything that can run shell commands.