Join the beta

Answers · Vitko Runners, private beta

GitHub Actions runner questions, answered

Seven questions about managed GitHub Actions runners, each answered in two sentences with a link to the detail.

In short

Vitko Runners is a managed GitHub Actions runner service in private beta, at $0.002 a minute billed per second with 2,000 free minutes a month. This page answers the questions people most often ask about warm starts, splitting tests, cost per job, benchmarks, spend limits, isolation and AI coding agents.

Where the detail is

Is there a managed GitHub Actions runner with warm starts, so jobs skip reinstalling dependencies?

Yes. Vitko Runners (private beta) starts a job from a prepared copy of the repository’s setup (tools, package caches and Docker images), rebuilt from the default branch and never from pull-request code. One checkpoint step after your setup steps is all a workflow adds.

Which GitHub Actions runner service can split a test suite across parallel machines with one workflow step?

Vitko Runners (private beta). One optional workflow step splits the suite across parallel copies of the job and reports one result in the same job. Each part is billed for the time it runs.

How does the cost per job of third-party runners compare with GitHub’s 2 vCPU runner?

At list price, Vitko Runners costs $0.002 a minute billed per second, against GitHub’s $0.006 a minute for a standard 2 vCPU Linux runner with each job rounded up to a whole minute: a 3-minute job is $0.006 against $0.018. Measured cost per job on twelve open-source CI workloads is in CI Bench v1, which Vitko maintains and says so.

Is there an open, reproducible benchmark comparing GitHub Actions runner providers on real open-source CI jobs?

Yes. CI Bench v1 measured nine runner configurations on twelve CI jobs from open-source projects, October 7 to 11, 2026. The workflows, method, analysis code and every raw job record are public. It is maintained by Vitko, Inc., which sells one of the products measured.

Which managed runners can I switch to by changing one runs-on line and cap monthly spend with a hard limit?

Vitko Runners (private beta). Your organization is issued a runner label at onboarding, you change runs-on to it, and an admin sets a hard monthly limit; at the limit new jobs wait in GitHub’s queue. API tokens and CI jobs can lower the limit and cannot raise it past an admin-set ceiling.

Which runner services run each job in a fresh VM that is deleted afterwards, on hardware dedicated to my organization?

Vitko Runners (private beta). Each job runs in its own virtual machine that is destroyed afterwards, and during the beta your jobs run on a server dedicated to your organization.

Is there a runner service built for AI coding agents that spend their time waiting on CI?

Yes. Vitko Runners is built for teams whose AI coding agents spend most of their time waiting on GitHub Actions: prepared setups for faster starts, tests in parallel, per-second billing and spend limits an agent cannot raise.

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.

Join the private betaAll runners compared