CI Runnerscirunners.org
Head-to-head

Buildkite hosted agents vs Orka

Answer in brief

Buildkite hosted agents suits teams on Buildkite Pipelines that want Buildkite to operate the agents, including Apple silicon macOS machines. Orka suits teams that want a dedicated, orchestrated fleet of Macs for ephemeral macOS CI across several CI systems. Buildkite hosted agents is the CI platform’s own hosted runners for Buildkite, priced at $0.008/min; Orka is a product that runs runners in your own cloud account or on your own hardware for GitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines and TeamCity, priced at From $109/mo per hosted Mac mini (Orka by quote).

By the CI Runners editors · Updated

Key differences between Buildkite hosted agents and Orka

  • Type: Buildkite hosted agents is the CI platform’s own hosted runners; Orka is a product that runs runners in your own cloud account or on your own hardware.
  • CI systems: Only Orka documents GitHub Actions, GitLab CI, Jenkins, Azure Pipelines and TeamCity.
  • Operating systems: Only Buildkite hosted agents documents Linux and Windows.
  • Architectures: Only Buildkite hosted agents documents x64.
  • Isolation: Buildkite hosted agents: Ephemeral virtualized environment. Orka: macOS VM.
  • Published price: $0.008/min (Buildkite hosted agents) versus From $109/mo per hosted Mac mini (Orka by quote) (Orka).
  • Self-hosting: Orka documents a self-hosted option; Buildkite hosted agents does not.
  • Your own cloud account: Orka documents running in your own cloud account; Buildkite hosted agents does not.

What they have in common

  • Both run Buildkite jobs.
  • Both document macOS runners.
  • Both document arm64 runners.
  • Both use a virtual machine per runner.
  • Neither is open source.

Buildkite hosted agents vs Orka at a glance

AttributeBuildkite hosted agentsOrka
What it isBuildkite’s managed agents: a single-use virtualized environment per job on Linux, macOS and Windows, billed per vCPU minute.Kubernetes-based orchestration of macOS VMs on Apple silicon, run in MacStadium data centers, on AWS EC2 Mac or on your own Macs.
TypeFirst-party hosted runnersRuns in your cloud or on your hardware
CI systemsBuildkiteGitHub Actions, GitLab CI, Buildkite, Jenkins, Azure Pipelines, TeamCity
Operating systemsLinux, macOS, WindowsmacOS
Architecturesx64, arm64arm64
IsolationEach job runs in its own virtualized environment that is destroyed with its data after the job; Buildkite describes hypervisor-level isolation between instances on hardware shared across customersJobs run in macOS virtual machines on Apple silicon Mac nodes; the GitHub runner creates a VM per job and tears it down afterwards, while the GitLab, Buildkite and Jenkins integrations offer both permanent and per-job (ephemeral) agents
Fresh environment per jobYesNot documented
HardwareBuildkite says it uses latest-generation Mac (M4) and AMD Zen-based hardware in a private cloud, with cache volumes on local NVMe-attached disksMacStadium lists hosted Mac mini (M2, M2 Pro, M4, M4 Pro) and Mac Studio (M1 Max, M2 Ultra) configurations; Orka 4.0 runs on Apple silicon nodes only.
Performance (vendor claim)Buildkite says hosted agents deliver up to 3x faster performance than equivalent sized machines from other CI/CD providers and cloud platforms (vendor claim)Not documented
Runner sizesLinux AMD64 and ARM64: 2 vCPU / 4 GB to 64 vCPU / 256 GB (16 vCPU and above on Enterprise); macOS M4: 6 vCPU / 28 GB and 12 vCPU / 56 GB; Windows AMD64: 2 vCPU / 8 GB to 16 vCPU / 64 GBCPU and memory are set per VM config; listed hosted Macs range from an M2 Mac mini (8 cores, 8 GB) to an M2 Ultra Mac Studio (24 cores, 128 GB)
CachingCache volumes and Git mirror volumes on Linux and macOS at no additional cost, retained for up to 14 days from last use, plus an internal container registry per cluster. Remote Docker builders with Docker layer caching are available on the Enterprise plan.Orka images are OCI images pulled from a registry, and the docs describe pre-caching images on nodes. For GitLab, cache restoration needs the gitlab-runner binary inside the VM image.
Docker layer cachingYesNot documented
GPUNot documentedNot documented
ConcurrencySet by plan as combined vCPUs in use: on Pro up to 256 Linux AMD64, 64 Linux ARM64, 48 M4 Mac and 64 Windows vCPU; on Free up to 20 Linux AMD64 vCPU; custom on EnterpriseBounded by the Mac nodes in the cluster; the GitHub runner reports up to MAX_RUNNERS (default 9000) and GitLab concurrency is set in config.toml
Static IPsYesNot documented
SSH into running jobsYesYes
PricingPay-as-you-go on the Pro plan ($30 per active user per month): Linux $0.004 per vCPU minute on AMD64 and ARM64 ($0.008/min for 2 vCPU, $0.016 for 4, $0.032 for 8), Mac $0.02 per vCPU minute ($0.12/min for M4 Medium, $0.24 for M4 Large), Windows $0.008 per vCPU minute. Metered to the second with no minimums; cache storage is not charged.Orka for DevOps pricing is not published (contact sales; Orka is also sold through AWS Marketplace). Individual hosted Macs are listed monthly, from $109 (M2 Mac mini, 8 GB) and $149 (M4 Mac mini, 16 GB) to $449 (M2 Ultra Mac Studio, 128 GB).
Free tierFree plan: up to 2,000 Linux vCPU minutes per month on the Small AMD64 shape. Pro includes 4,000 Linux AMD64 vCPU minutes per month. A 30-day all-access trial needs no credit cardNo free trial on individual hosted Macs; MacStadium says a proof of concept may be possible for large migrations
Open sourceNoNo
Self-host / your cloudNo / NoYes / Yes
ComplianceSOC 2 Type IIISO 27001, 27017 and 27018; SOC 1 and SOC 2 Type 2 (as stated by MacStadium)
RegionsUS East Coast data centers onlyMacStadium data centers in Atlanta, Las Vegas and Dublin; or your own AWS account or premises
Company headquartersNot documentedAtlanta, Georgia, United States
Good fit forTeams on Buildkite Pipelines that want Buildkite to operate the agents, including Apple silicon macOS machinesTeams that want a dedicated, orchestrated fleet of Macs for ephemeral macOS CI across several CI systems

Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.

Which should you choose?

Reasons to choose Buildkite hosted agents

  • You use Buildkite Pipelines and want agents that Buildkite provisions and scales
  • You need Apple silicon M4 macOS agents with terminal and browser-based desktop access
  • You want cache volumes and Git mirrors without a separate storage charge
  • You want billing by vCPU minute, metered to the second with no minimum charge

Reasons to choose Orka

  • You want per-job macOS VMs on Macs dedicated to your team rather than a shared runner pool
  • You use more than one CI system: MacStadium documents GitHub Actions, GitLab, Buildkite, Jenkins, TeamCity and Azure Pipelines
  • You need the same platform in a vendor data center, in your AWS account or on-premises
  • You want Android emulators next to macOS VMs on the same Mac fleet (Orka 4.0)

Trade-offs to check first

  • Buildkite hosted agents: Hosted exclusively in US East Coast data centers
  • Buildkite hosted agents: Signed pipeline validation is not supported for hosted agents
  • Orka: Orka for DevOps pricing is not published; MacStadium directs buyers to sales
  • Orka: MacStadium states it does not offer free trials on individual hosted Macs

Run your slowest workflow on both before deciding. See the full Buildkite hosted agents profile and Orka profile, or the complete comparison.

More comparisons

Frequently asked questions

Is Buildkite hosted agents or Orka better?
Neither is better for every pipeline. Buildkite hosted agents suits teams on Buildkite Pipelines that want Buildkite to operate the agents, including Apple silicon macOS machines. Orka suits teams that want a dedicated, orchestrated fleet of Macs for ephemeral macOS CI across several CI systems.
What is the difference between Buildkite hosted agents and Orka?
Buildkite hosted agents is the CI platform’s own hosted runners; Orka is a product that runs runners in your own cloud account or on your own hardware. Only Orka documents GitHub Actions, GitLab CI, Jenkins, Azure Pipelines and TeamCity. Only Buildkite hosted agents documents Linux and Windows. Only Buildkite hosted agents documents x64. Isolation is Ephemeral virtualized environment on Buildkite hosted agents and macOS VM on Orka.
Which is open source, Buildkite hosted agents or Orka?
Neither is open source.
How do Buildkite hosted agents and Orka isolate jobs?
Buildkite hosted agents: Each job runs in its own virtualized environment that is destroyed with its data after the job; Buildkite describes hypervisor-level isolation between instances on hardware shared across customers. Orka: Jobs run in macOS virtual machines on Apple silicon Mac nodes; the GitHub runner creates a VM per job and tears it down afterwards, while the GitLab, Buildkite and Jenkins integrations offer both permanent and per-job (ephemeral) agents.
How does Buildkite hosted agents pricing compare with Orka?
Buildkite hosted agents: Pay-as-you-go on the Pro plan ($30 per active user per month): Linux $0.004 per vCPU minute on AMD64 and ARM64 ($0.008/min for 2 vCPU, $0.016 for 4, $0.032 for 8), Mac $0.02 per vCPU minute ($0.12/min for M4 Medium, $0.24 for M4 Large), Windows $0.008 per vCPU minute. Metered to the second with no minimums; cache storage is not charged. Orka: Orka for DevOps pricing is not published (contact sales; Orka is also sold through AWS Marketplace). Individual hosted Macs are listed monthly, from $109 (M2 Mac mini, 8 GB) and $149 (M4 Mac mini, 16 GB) to $449 (M2 Ultra Mac Studio, 128 GB). Rates change, so check the Buildkite hosted agents and Orka pricing pages before deciding.
Is Buildkite hosted agents or Orka faster?
We have not benchmarked them, and speed depends on the workload. What each provider says: Buildkite hosted agents: Buildkite says hosted agents deliver up to 3x faster performance than equivalent sized machines from other CI/CD providers and cloud platforms (vendor claim). Orka: Not documented.
Do Buildkite hosted agents and Orka cache Docker layers?
Buildkite hosted agents: Cache volumes and Git mirror volumes on Linux and macOS at no additional cost, retained for up to 14 days from last use, plus an internal container registry per cluster. Remote Docker builders with Docker layer caching are available on the Enterprise plan. Orka: Docker layer caching is not documented.
Where do Buildkite hosted agents and Orka runners run?
Buildkite hosted agents is the CI platform’s own hosted runners. Orka is a product that runs runners in your own cloud account or on your own hardware (MacStadium Cloud, AWS, Kubernetes and Bare metal).

Sources

  1. buildkite.com/docs/agent/buildkite-hosted
  2. buildkite.com/docs/agent/buildkite-hosted/linux
  3. buildkite.com/docs/agent/buildkite-hosted/macos
  4. buildkite.com/docs/agent/buildkite-hosted/windows
  5. macstadium.com/orka
  6. macstadium.com/pricing
  7. macstadium.com/company
  8. macstadium.com/datacenters

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). Buildkite hosted agents vs Orka. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/buildkite-hosted-agents-vs-macstadium-orka/