Last reviewed: 2026-04-30
VPS for CI Runners
Self-hosted CI runners are useful when public hosted minutes are too expensive, builds need private network access, or the pipeline needs a controlled machine shape. The workload can be bursty: one job may barely touch the server while another compiles, downloads containers, and fills disk with build artifacts. Pick a plan with enough CPU and RAM for peak jobs, clean workspaces aggressively, and isolate runners from secrets they do not need.
Recommended plans
Performance
4 vCPU, 8 GB RAM, 40 GB NVMe SSD, 10 TB transfer
Balanced production tier for busier apps, game servers, and build jobs.
Pro
8 vCPU, 16 GB RAM, 60 GB NVMe SSD, 10 TB transfer
Higher CPU and memory for heavier users, larger communities, or parallel workloads.
Scale
16 vCPU, 64 GB RAM, 200 GB NVMe SSD, 30 TB transfer
Large RAM and disk profile for demanding builds, big game worlds, and heavier caches.
Software
Common software
- GitHub Actions Runner
- GitLab Runner
- Buildkite Agent
- Docker
- Podman
Sizing
Traffic and storage
- Bandwidth
- 1-10 TB/month depending on container pulls, artifact uploads, and package caches
- Storage
- 40-200 GB for workspaces, caches, container layers, and artifacts
- Planning note
- Use Pro or Scale when jobs compile large projects, run multiple workers, or keep heavy caches locally.
Setup
Setup approach
- Deploy: choose a plan, region, and OS image.
- Install: add only the packages your workload needs.
- Configure: set firewall rules, updates, backups, and monitoring.