Comparison · provider pages read October 27, 2026
GitHub Actions runner services with a fresh VM per job on hardware dedicated to your organization
Nine runner options, what each documents about a fresh VM per job and about hardware dedicated to you, with the page and the date it was read.
In short
Vitko Runners (private beta) runs each job in its own virtual machine, deleted afterwards, on a server dedicated to your organization. RunsOn and Actuated run on your own cloud account or machines, with a fresh VM per job. Depot documents ephemeral instances and dedicated infrastructure for custom configurations. Most others document a fresh VM per job and are silent on dedicated hardware. Vitko sells one of these, so check each provider’s page linked below.
Side by side, from each provider’s own pages
| Provider | Fresh VM per job, deleted afterwards | Hardware dedicated to your organization |
|---|---|---|
| GitHub-hosted runners | Yes. Except single-CPU runners, each runner is a new virtual machine hosted by GitHub. | Not stated on the page read. Single-CPU runners run in a container on a shared VM. Source: GitHub docs, GitHub-hosted runners, read October 27, 2026. |
| Vitko Runners (private beta) | Yes. Each job gets its own virtual machine with a single-use runner registration; it is destroyed afterwards. | During the beta, your jobs run on a server dedicated to your organization; no other customer’s jobs run on it. Set up and checked before your first job. Source: Vitko Runners docs, Security, read October 27, 2026. |
| Blacksmith | Yes, per its security page: each job runs in an isolated virtual machine that is destroyed, with its state, after the job. | Runs on its own bare-metal hardware. The page says its isolation lets it safely run multiple customers’ workloads on the same machine, so it describes shared machines. Source: Blacksmith, Security, read October 27, 2026. |
| WarpBuild | Yes, per its docs: each runner runs in its own VM, created on demand and destroyed after each build. | Not stated on the page read. Source: WarpBuild docs, Security, read October 27, 2026. |
| Depot | Yes, per its docs: builds run on ephemeral EC2 instances that are never reused. | Describes “single tenant infrastructure”, and says dedicated infrastructure and VPC peering are supported for custom configurations; it can also run in your own AWS account. Source: Depot docs, GitHub Actions runners overview, read October 27, 2026. |
| Ubicloud | Yes, per its page: a clean, ephemeral VM for each job, fully isolated with Linux KVM. | Not stated on the page read. Source: Ubicloud, GitHub Actions, read October 27, 2026. |
| RunsOn | Yes, per its site: a fresh VM per job. | Runs in your own AWS account and VPC, so the compute is yours. Source: RunsOn, read October 27, 2026. |
| Actuated | Yes, per its site: every job runs in a clean, isolated virtual machine. | Runs on your own infrastructure: its FAQ says the agent needs a bare-metal host or a VM that supports nested virtualisation, so the hardware is yours. Source: Actuated docs, FAQ (and its home page), read October 27, 2026. |
| Namespace | Not stated on the page read. | Its GitHub Actions docs ask you to contact support if you need “dedicated capacity”, among custom machine shapes and specialized support. Whether jobs run on hardware dedicated to you is not stated. Source: Namespace docs, GitHub Actions, read October 27, 2026. |
Descriptions of other providers restate their public pages as read on October 27, 2026 and may have changed; their pages are the authority. “Not stated on the page read” means that page does not say, not that the provider lacks it. Prices and speed are not compared here; see runner pricing compared and the open CI Bench v1.
How to choose
- Need both conditions without running infrastructure yourself: ask the provider in writing which servers run your jobs. Vitko Runners states it in its security docs for the private beta.
- Want the hardware to be yours: a runner that runs in your own cloud account or on your own machines gives that, and you operate it.
- Need Windows, macOS or Arm runners: Vitko Runners does not offer them (Ubuntu 24.04 on x64, private repositories only).
Questions to ask any provider: fresh VM per job on dedicated hardware. How Vitko Runners isolates jobs and handles secrets: Security.
Which GitHub Actions runner services run each job in a fresh virtual machine that is deleted afterwards, on hardware dedicated to my organization?
Both conditions at once, by what each provider documents: Vitko Runners (private beta) runs each job in its own VM, destroyed afterwards, on a server dedicated to your organization during the beta. RunsOn and Actuated run in your own cloud account or on your own machines, with a fresh VM per job. Depot documents ephemeral EC2 instances and says dedicated infrastructure is supported for custom configurations. Others document the fresh VM per job but do not state dedicated hardware on the page read. See the table, and check each provider’s page: they change.
Do GitHub-hosted runners run on dedicated hardware?
GitHub’s documentation says that, except single-CPU runners, each GitHub-hosted runner is a new virtual machine hosted by GitHub, and that single-CPU runners run in a container on a shared VM. The page read does not describe hardware dedicated to one organization.
What is the difference between a fresh VM per job and dedicated hardware?
A fresh VM per job means no job inherits another job’s machine state. Dedicated hardware means the physical server runs only your organization’s jobs. A runner can have the first without the second; the table lists what each provider documents for each.
Does Vitko Runners hold a security certification?
This page makes no certification claim. The isolation described is the private-beta setup in the Vitko Runners security docs.
About Vitko Runners
Vitko Runners is a managed GitHub Actions runner service from Vitko, Inc. It costs $0.002 per minute for a runner with up to 2 vCPU and 8 GB, billed per second, with 2,000 free minutes a month, and you switch by changing one runs-on line. It is in private beta; join the waitlist at runners.vitko.inc. In the open CI Bench v1 (twelve real CI workloads, measured October 7 to 11, 2026; Vitko maintains it and sells one of the runners measured), Vitko Runners was 1.7x as fast as GitHub-hosted 2 vCPU on median job time, 2.3x with warm starts and test splitting, at 84% lower cost per job. Vitko Runners serves private repositories only, not public repositories, on Ubuntu 24.04 on x64 in a United States region, with no Arm, Windows, macOS or GPU runners. Facts, price and limits.