Runners for GitHub Actions
Cut your CI bill
and build times
With one line of YAML. Bare-metal Linux and Apple Silicon macOS runners for GitHub Actions, billed by the second.
- 3×
- Faster than GitHub
- 50%
- Of GitHub's price
- $0.002
- Per vCPU / minute
Half GitHub's per-minute price, up to 3× faster.
PostHog/posthog docker build
3.2× faster78% cheaper
$0.0728$0.33
nodejs/node build + test
3.0× faster76% cheaper
$0.596$2.442
torvalds/linux kernel build
2.4× faster73% cheaper
$0.0469$0.176
apache/kafka build
2.3× faster69% cheaper
$0.0608$0.198
spring-projects/spring-boot build
1.8× faster59% cheaper
$0.752$1.826
kubernetes/kubernetes build + test
1.6× faster55% cheaper
$0.375$0.84
iina/iina
3.0× faster
nodejs/node
1.8× faster
microsoft/vscode
1.8× faster
hashicorp/nomad
1.3× faster
And that's before the mirrors, which sit next to the runners and keep repeat installs off the public internet.
Learn about actions cacheOne YAML line. That's it.
Larger x64 configurations are available on request. macOS runners run macOS 26 Tahoe on Apple Silicon.
Our own hardware, and the storage to match.
Run jobs inside your tailnet
Jobs on a dedicated Linux runner label join your Tailscale network before the first step runs, with no Tailscale action or secret in your workflow. You choose which repositories get access, and pull requests from forks stay out by default.
Read the Tailscale guideQueue time is never billed. Pay for what runs.
Compute is billed by the second. Rates are shown per minute to compare with GitHub.
View pricingx64 Runners
AMD Ryzen$0.002per vCPU / minute
macOS Runners
M4 Pro$0.020per vCPU / minute
Cache & Sticky Disks
Storage$0.20per GiB / month
Custom images and nodes are available with quote-based pricing.
Request a quoteEnterprise-grade security.
Every job runs in a single-use VM, destroyed when it ends.
Single-use VMs
Destroyed at job end. Nothing carries over.
We don't store your secrets
Your secrets stay in GitHub.
Isolation at the hypervisor
Your own VM on bare metal, never shared.
Fixed egress range
One fixed CIDR. No surprise rotation.
Don't believe us. Believe them.
Questions? Answered.
Have a question we haven't answered? Reach out to hello@luxor.ai
Agent Cloud runners are self-hosted-style GitHub Actions runners managed by Luxor Agent Cloud on bare-metal Linux x64 and macOS infrastructure, designed to be a drop-in alternative to GitHub-hosted runners.
You point your workflow at an Agent Cloud runner label by changing the runs-on value in your YAML, and your existing GitHub Actions jobs run unmodified on faster, cheaper hardware. There is no agent to install on your own servers and no infrastructure for your team to operate.
Change the runs-on value in your workflow YAML to an Agent Cloud runner label (for example replace ubuntu-latest with luxor-standard-small-2c-4g) and your next workflow run executes on Luxor Agent Cloud.
No other changes are required: Actions, secrets, caching, matrix strategies, reusable workflows, and container jobs all continue to work. The Runners quickstart walks through the migration wizard, which can also open the YAML pull request for you.
Yes. Every job runs in a single-tenant ephemeral virtual machine with a fresh kernel, fresh disk, and isolated network namespace, and the VM is destroyed at the end of the workflow.
Jobs cannot inspect or interfere with one another, and job-time secrets never leave the runner VM boundary. Luxor Agent Cloud operates under the SOC 2 Type II program of its parent company Luxor Technology. See the Security page for the full security program, encryption details, incident-response process, and report request flow.
Agent Cloud runners cost half GitHub's per-minute price and run the same workflows up to 3x faster than GitHub-hosted runners, with compute billed by the second.
Pricing is published on the Pricing page and new accounts get $100 in free credits. Committed-use discounts are available for teams with steady or high-volume workloads.
Luxor Agent Cloud supports Linux on x64 and macOS on Apple Silicon (M-series) hardware, covering CI workloads for both general-purpose backend/web pipelines and teams that build, test, or sign Apple platform code.
Linux runners cover the same Ubuntu image surface as standard GitHub Actions, so most workflows that target ubuntu-latest migrate without source changes. For macOS specifics (Xcode toolchains, keychain handling, and signing) see the macOS runners docs.











