Organizations run Anka with the same building blocks: the Virtualization CLI, an optional Build Cloud Controller and Registry, and CI plugins. The constraints change. A CI provider needs isolation between tenants. A bank needs access control on a private network. A game studio needs stable Xcode build times. The pages below show how those setups differ.

Examples

Gaming

Engine and editor CI at high parallel volume. Controller and Registry on a large node pool. Typical scale: tens to low hundreds of nodes. Full example.

iOS and macOS game-client builds across several teams. Shared templates with isolation so one title does not block another. Typical scale: dozens of nodes. Full example.

CI service provider

macOS GitHub-style runners on a custom orchestrator. CLI-only Anka with export/import; no Controller or Registry. Typical scale: hundreds of concurrent VMs. Full example.

Regulated Sector

On-prem macOS build and test with Anklet, GitHub Actions, and a standalone Registry. No Controller. Typical scale: tens of nodes. Full example.

Enterprise using AWS EC2 Macs

EC2 Mac Marketplace AMI on AWS for enterprise iOS apps. Controller and Registry on Linux EC2 in the same VPC as Mac nodes; simulator tests inside VMs. Typical scale: multiple tens of instances, scaled down on weekends. Full example.

Start here

If you are new to Anka, install the CLI first, then add the Build Cloud if you need a shared node pool:

1. Getting Started (CLI)
2. Getting Started (Cloud)