Luxor Runners
GitHub Actions runners on bare-metal Linux x64 and Apple Silicon macOS, one single-use VM per job; called Tenki until November 2026. 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.
Overview
Luxor Runners is the GitHub Actions runner product of Luxor Agent Cloud, the service that was called Tenki Cloud until November 16, 2026. A team installs the GitHub App on its organization and changes runs-on to a luxor-* label; older tenki-* labels keep working. Each job runs in a single-use virtual machine on bare-metal Linux x64 hosts or Apple Silicon M4 Pro Macs, and the VM is destroyed when the job ends.
Pricing is per vCPU-minute, billed by the second, with queue time not billed. The same workspace also holds Luxor Sandbox and Luxor Code Reviewer, and runner jobs share one concurrency limit and one storage pool with sandboxes. Runner traffic leaves from a fixed CIDR, dedicated egress addresses cost $100 per IP per month, and dedicated Linux labels can join a Tailscale tailnet. Pricing lists a $0 Starter plan and a Team plan.
Notable
- November 16, 2026: Tenki Cloud was renamed Luxor Agent Cloud and the company became Luxor AI; existing tenki-* runner labels and GitHub App installs keep working.
- December 8, 2025: macOS runners on Apple M4 Pro machines launched in waitlist-only early access (changelog).
- October 2026: sticky disks were enabled by default (October 2), and the 1.5x Premium Runners surcharge was removed while runner cache billing of $0.20 per GiB-month was added (October 16).
- October 30, 2026: dedicated CI jobs gained support for joining a saved Tailscale network.
Luxor Runners specifications
| Attribute | Details |
|---|---|
| CI systems | GitHub Actions |
| Operating systems | Linux, macOS |
| Architectures | x64, arm64 |
| Deployment | Managed runner service |
| Isolation | Each job runs in a single-use VM with its own kernel on bare-metal hosts and is destroyed when the job ends; the hypervisor is not named |
| Fresh environment per job | Yes |
| Hardware | Linux x64 runners on bare-metal hosts that Luxor describes as “5th Gen AMD Ryzen” and says it owns and operates, with two vCPUs mapped to one physical core; macOS runners on Apple Silicon M4 Pro. |
| Performance (vendor claim) | Luxor says its runners are up to 3x faster than GitHub-hosted runners on its own published benchmarks (vendor claim) |
| Runner sizes | Linux x64: 2 vCPU / 4 GB to 16 vCPU / 32 GB, larger on request; macOS: 2 vCPU / 4 GB to 14 vCPU / 38 GB |
| Caching | A hosted drop-in backend for the GitHub Actions cache (entries expire after 7 days, up to 10 GiB each), pull-through mirrors for npm, APT, Go modules, Cargo, Maven, CocoaPods, Swift packages and Docker Hub, and sticky disks that keep cache directories between Linux jobs. The docs say the Docker Hub mirror does not cache build layers between jobs. |
| Docker layer caching | Not documented |
| GPU | Not documented |
| Concurrency | 5 concurrent sessions on Starter and 100 on Team, shared between runner jobs and sandbox sessions; jobs above the limit queue |
| Job limits | No runner-side time limit; the docs say GitHub’s 6 hours per job applies. Starter is capped at 2 vCPU / 4 GB (4 vCPU / 8 GB with a payment method on file) and Team at 16 vCPU / 64 GB |
| Static IPs | Yes |
| SSH into running jobs | Not documented |
| Observability | Not documented |
| Setup | Connect a GitHub organization by installing the Luxor Runner GitHub App, then change runs-on by hand or let the migration wizard open a pull request. |
| Example label | luxor-ubuntu-medium-4c-8g |
| Pricing | Linux x64 is $0.002 per vCPU-minute: $0.004/min (2 vCPU / 4 GB), $0.008 (4 vCPU), $0.016 (8 vCPU), $0.032 (16 vCPU). macOS is $0.020 per vCPU-minute, from $0.040/min (2 vCPU) to $0.280/min (14 vCPU). Cache and sticky-disk storage is $0.20 per GiB-month; the Team plan is $250/month billed monthly or $200/month billed yearly. |
| Free tier | $100 in free credits once a payment method is added on the $0 Starter plan; Team includes $100 of credits per month |
| Compliance | Luxor says its parent platform has completed a SOC 2 Type 2 examination and that a SOC 2 report for Luxor Agent Cloud is in progress |
| Regions | Not documented |
| Open source | No |
| Company headquarters | Seattle, Washington, United States · More from the United States |
Facts from Luxor Runners’s public documentation, verified November 22, 2026. Performance figures are vendor claims.
Strengths and trade-offs
Reasons to choose it
- You want Linux x64 runners priced at a flat $0.002 per vCPU-minute, billed by the second with queue time not billed
- You need Apple Silicon macOS runners (M4 Pro) from the same vendor as your Linux runners
- You need runner traffic to leave from a fixed CIDR, or a dedicated egress IP at $100 per month
- You want cache directories kept between Linux jobs on sticky disks instead of archived and restored
Trade-offs
- 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
Good fit for: Teams on GitHub Actions that want per-vCPU-minute Linux x64 and Apple Silicon macOS runners with a fixed egress range.
Use cases Luxor Runners fits
- Faster builds: Luxor publishes benchmarks claiming up to 3x faster runs than GitHub-hosted runners, with sticky disks and package mirrors to cut repeat work (vendor claim).
- Lower CI cost: Linux x64 runners are listed at $0.004 per minute for 2 vCPU, billed by the second, with $100 in starting credits.
- macOS and iOS builds: macOS 15 and macOS 26 runners on Apple Silicon M4 Pro are offered from 2 to 14 vCPU at $0.020 per vCPU-minute.
How Luxor Runners compares
| 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 |
| 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 |
| 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 |
| Ubicloud Runners | GitHub Actions | Linux, x64, arm64 | Vendor-hosted | KVM VM | $0.00125/min | 30 vCPU / 120 GB | Yes | Not documented | Yes | United States |
| 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 |
Head-to-head: Blacksmith vs Luxor Runners
Frequently asked questions
What is Luxor Runners?
Which CI systems does Luxor Runners work with?
How does Luxor Runners isolate jobs?
Is Luxor Runners open source?
How much does Luxor Runners cost?
How do I switch from GitHub-hosted runners to Luxor Runners?
luxor-ubuntu-medium-4c-8g.How fast is Luxor Runners?
Does Luxor Runners have a free tier?
Does Luxor Runners support ARM64 runners?
Does Luxor Runners offer macOS runners?
How many jobs can run at once on Luxor Runners?
What compliance certifications does Luxor Runners have?
Where is Luxor Technology based?
What are the alternatives to Luxor Runners?
Sources
- luxor.ai/
- luxor.ai/docs/migrate-to-luxor.md
- luxor.ai/blog/tenki-is-now-luxor-agent-cloud
- luxor.ai/products/runners.md
- luxor.ai/docs/pricing
- luxor.ai/docs/runners/sizes.md
- luxor.ai/docs/runners/limits-and-concurrency.md
- luxor.ai/docs/runners/caching.md
- luxor.ai/docs/runners/sticky-disks.md
- luxor.ai/docs/runners/networking.md
- luxor.ai/docs/runners/quickstart.md
- luxor.ai/docs/trust/security.md
- luxor.ai/docs/changelog.md
- luxor.ai/company/about.md
- luxor.ai/docs/terms-of-service.md
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. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/luxor-runners/