Providers

A provider is the backend that Orchestrator uses to run your builds. You choose a provider by setting the providerStrategy parameter.

 ┌──────────────┐  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐
 │     aws      │  │     k8s      │  │ local-docker │  │    local     │
 │              │  │              │  │              │  │              │
 │ Fargate      │  │ Cluster      │  │ Container    │  │ Direct       │
 │ Fully        │  │ Bring your   │  │ No cloud     │  │ No container │
 │ managed      │  │ own cluster  │  │ needed       │  │ needed       │
 └──────────────┘  └──────────────┘  └──────────────┘  └──────────────┘
  Cloud scaling     Cloud scaling     Local builds      Local builds
  No servers        Flexible          Docker required    Simplest setup

Built-in Providers

These providers ship with Orchestrator and are maintained by the Game CI team.

Provider	providerStrategy	Description
AWS Fargate	aws	Runs jobs on AWS Fargate (ECS). Fully managed, no servers to maintain.
Kubernetes	k8s	Runs jobs on any Kubernetes cluster. Flexible but requires a running cluster.
Local Docker	local-docker	Runs jobs in Docker containers on the local machine.
Local (direct)	local	Runs jobs directly on the local machine without containers.

Each provider has its own page with setup instructions:

• AWS Fargate
• Kubernetes
• Local Docker
• Local

Custom Providers

Extend Orchestrator with your own provider by pointing providerStrategy at a GitHub repository, NPM package, or local file path.

See Custom Providers for the full guide.

Community Providers

Third-party providers shared by the Game CI community.

See the Community Providers page for the current list and how to submit your own.