Luxor Runners alternatives
The 6 alternatives below are grouped by kind of runner, and each says whom it suits. Start from the requirement that matters most to you: price per minute, operating systems, caching, isolation or where the runners have to run.
Luxor Runners trade-offs to weigh
A managed GitHub Actions runner service on vendor-owned bare metal, renamed from Tenki to Luxor in November 2026, that suits teams wanting simple per-vCPU pricing for Linux x64 and macOS jobs.
- No Windows runners (stated on luxor.ai); Linux arm64 runners are not documented
- Sticky disks do not support macOS runners or container jobs
- Starter plan is capped at 2 vCPU / 4 GB runners, or 4 vCPU / 8 GB with a payment method on file
- A SOC 2 report for Luxor Agent Cloud itself is still in progress
Luxor Runners alternatives, by kind
Managed runners for GitHub Actions
Third-party runners you switch to by changing the runs-on label in a workflow.
Blacksmith
Managed GitHub Actions runners in Firecracker microVMs on the vendor’s own bare-metal fleet, with caches kept next to the runners.
- Firecracker microVM
- Ephemeral
- arm64
- macOS
- Windows
- Docker layer cache
Whom it suits: Teams on GitHub Actions that want microVM-isolated runners on bare metal with built-in Docker layer caching and CI observability. A managed GitHub Actions runner service on vendor-owned bare metal with microVM isolation, suited to organizations that want faster hardware plus integrated caching and observability.
Depot GitHub Actions Runners
Managed GitHub Actions runners on single-tenant AWS EC2 instances, connected to Depot’s cache and container build service.
- Single-tenant EC2 instance
- Ephemeral
- arm64
- macOS
- Windows
- Docker layer cache
- GPU
- BYOC
Whom it suits: Teams on GitHub Actions that want single-tenant EC2 runners alongside a shared build cache and remote container builds from the same vendor. A managed GitHub Actions runner service built on single-tenant AWS instances, suited to teams that also want Depot’s cache and container build service.
Full profile →Depot GitHub Actions Runners alternativesWebsite ↗
Namespace
Managed runners for GitHub Actions and Buildkite on the vendor’s own hardware, configured through profiles with persistent cache volumes.
- Virtual machine
- Ephemeral
- arm64
- macOS
- Windows
- Docker layer cache
Whom it suits: Teams on GitHub Actions or Buildkite that want VM-isolated Linux, macOS and Windows runners with persistent cache volumes and fine-grained machine shapes. A managed runner platform for GitHub Actions and Buildkite on vendor-operated hardware, suited to teams that want per-job VMs, persistent cache volumes and all three operating systems.
Ubicloud Runners
Managed Linux runners for GitHub Actions from an open-source cloud platform that runs on leased bare metal.
- KVM VM
- Ephemeral
- arm64
- Docker layer cache
- Open source
- Self-hostable
Whom it suits: Teams on GitHub Actions that want low per-minute Linux runners in European data centers from a vendor whose cloud platform is open source. A low-priced managed Linux runner service for GitHub Actions built on an open-source cloud, suited to teams that want x64 and arm64 runners in Europe.
WarpBuild
Managed GitHub Actions runners in ephemeral VMs, also offered as a deployment in your own AWS, Google Cloud or Azure account.
- Ephemeral VM
- Ephemeral
- arm64
- macOS
- Windows
- Docker layer cache
- BYOC
Whom it suits: Teams on GitHub Actions that want managed runners now with the option to move the same setup into their own AWS, Google Cloud or Azure account. A managed GitHub Actions runner service with a bring-your-own-cloud option, suited to teams that want hosted runners with a path to running them in their own cloud account.
Runners from your CI platform or cloud
The first-party hosted runners of GitHub, GitLab, Buildkite and Azure, plus cloud-native runner services.
GitHub-hosted runners
GitHub’s own Actions runners: a new VM per job on Linux, Windows and macOS, with larger, arm64 and GPU sizes billed per minute.
- Fresh VM
- Ephemeral
- arm64
- macOS
- Windows
- GPU
Whom it suits: Teams on GitHub Actions that want runners with no setup, and public repositories that can use the free standard runners. The default runners for GitHub Actions, suited to teams that prefer zero setup and to public repositories, with larger sizes available per minute on paid plans.
Luxor Runners vs alternatives
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| Luxor Runners | GitHub Actions | Linux, macOS, x64, arm64 | Vendor-hosted | Single-use VM | $0.004/min | 16 vCPU / 32 GB | Not documented | Not documented | No | United States |
| Blacksmith | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Firecracker microVM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | United States |
| Depot GitHub Actions Runners | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Single-tenant EC2 instance | $0.006/min | 64 vCPU / 256 GB | Yes | Yes | No | Not documented |
| GitHub-hosted runners | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Fresh VM | $0.006/min | 96 vCPU / 384 GB | Not documented | Yes | No | United States |
| Namespace | GitHub Actions, Buildkite | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Virtual machine | $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB) | 64 vCPU / 512 GB | Yes | Not documented | No | Not documented |
| Ubicloud Runners | GitHub Actions | Linux, x64, arm64 | Vendor-hosted | KVM VM | $0.00125/min | 30 vCPU / 120 GB | Yes | Not documented | Yes | United States |
| WarpBuild | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Ephemeral VM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | Not documented |
Head-to-head: Blacksmith vs Luxor Runners
Frequently asked questions
What are the main alternatives to Luxor Runners?
Is there an open-source alternative to Luxor Runners?
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). Luxor Runners alternatives. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/alternatives/luxor-runners/