<!-- Markdown mirror of https://runners.vitko.inc/docs/limits/ -->

Runners

# Limits and known issues

What Vitko Runners doesn’t do yet, and what to watch for.

## Limits

- Linux only: Ubuntu 24.04 on x64. No Arm, Windows, macOS or GPU runners.
- Up to 2 vCPU and 8 GB per job at the list price. Larger sizes on request.
- Private repositories only. Runners on public repositories would run code from anyone’s pull request.
- United States region only.
- Jobs at once: you set it, up to what your plan allows. Extra jobs wait in GitHub’s queue. See [Spend controls](https://runners.vitko.inc/docs/spend-controls/).
- No private-network or VPN access from jobs.

## Known issues

- A warm-start setup script (`.vitko/setup.sh`) can’t use Docker yet; the checkpoint step saves Docker images. Docker works normally in your jobs.
- Warm starts: steps before the checkpoint must not use secrets, or nothing is saved.
- The image isn’t a copy of GitHub’s. A tool your workflow expects may be missing; see [Image and installed tools](https://runners.vitko.inc/docs/image/).
- Test parallelization: the parts can’t reach the network, and tests that depend on order can fail when split. See [Test parallelization](https://runners.vitko.inc/docs/split-tests/#prepare).
