COMPARE / UNCAGE.SH VS GITHUB-HOSTED RUNNERS
Drop-in GitHub Actions runners:
2x faster builds at a fifth of the per-minute cost.
GitHub Actions is the best CI control plane in software—you don’t need to leave it. You just shouldn’t overpay for slow, uncached GitHub-hosted runners. Swap one line (runs-on: uncage-4vcpu) and cut both build times and monthly CI spend.
TL;DR VERDICT
Keep GitHub Actions workflows, secrets, and PR checks—upgrade only the runner compute underneath.
WHERE UNCAGE.SH RUNNERS WIN
- ✓ Your builds spend minutes redownloading Docker layers, Cargo crates, or npm caches on every run
- ✓ You pay $0.016/min (4-core) or $0.032/min (8-core) on GitHub Larger Runners with full-minute rounding
- ✓ You want clean ephemeral VMs per job without operating self-hosted Kubernetes runner autoscalers
- ✓ You run integration tests that benefit from co-located, branched PostgreSQL 17 databases
WHAT GITHUB-HOSTED RUNNERS DO WELL
- • 2,000 free monthly minutes on public/small private repositories with zero setup
- • Native macOS and Windows hosted runner images for Apple/Windows-specific builds
- • Zero external token configuration when staying strictly inside GitHub’s default 2-core tier
RUNNER BENCHMARKS & RATES
Exact per-minute & caching comparison.
| Capability | uncage.sh CI Runners | GitHub-Hosted Runners |
|---|---|---|
| 2-vCPU Linux Runner Rate | $0.00156 / min ($0.0936/hr · 4 GB RAM) | $0.00800 / min (standard 2-core · 7 GB) |
| 4-vCPU Linux Runner Rate | $0.00312 / min ($0.1872/hr · 8 GB RAM) | $0.01600 / min (4-core Larger Runner) |
| 8-vCPU Linux Runner Rate | $0.00624 / min ($0.3744/hr · 16 GB RAM) | $0.03200 / min (8-core Larger Runner) |
| Billing Granularity | Exact per-active-second metering | Rounded up to nearest full minute per job |
| Persistent Docker BuildKit Cache | Built-in local regional NVMe cache across jobs | Ephemeral disk wiped every job; slow remote cache upload |
| Job Isolation | Clean single-use ephemeral microVM per job | Clean single-use VM per job |
| Migration Effort | 1-line runs-on: uncage-4vcpu swap | Already default |
| macOS / iOS Xcode Builds | Linux x86_64 workloads only | Native macOS hosted runners available |
CI SPEND BREAKDOWN
Real monthly build-minute comparisons.
Startup Monorepo (15,000 build mins/mo on 4-core runners)
4 vCPU · 8 GB · persistent NVMe cache
uncage.sh $46.80 / mo
GitHub-Hosted $240.00 / mo (GitHub 4-core Larger Runners)
Save $193/mo (80%)—and builds finish ~2x faster with NVMe cache
Growth Engineering Team (40,000 build mins/mo on 8-core runners)
8 vCPU · 16 GB · per-second billing
uncage.sh $249.60 / mo
GitHub-Hosted $1,280.00 / mo (GitHub 8-core Larger Runners)
Save over $12,000/year with zero self-hosted cluster maintenance
High-Volume Matrix Lint/Test (10,000 short 25-second jobs on 2-core)
4,167 active mins vs 10,000 rounded mins
uncage.sh $6.50 / mo
GitHub-Hosted $80.00 / mo (1-minute minimum rounding)
Per-second billing eliminates the short-job rounding tax
1-LINE MIGRATION
Upgrade your GitHub Actions runners in 3 steps.
STEP 01
Connect your GitHub repository or organization
Generate a runner integration token in the uncage.sh console or CLI and select your preferred region.
uncage projects create --name ci-fleet --region us-east STEP 02
Swap one line in .github/workflows/*.yml
Replace runs-on: ubuntu-latest with uncage-2vcpu, uncage-4vcpu, or uncage-8vcpu.
jobs:
build:
runs-on: uncage-4vcpu STEP 03
Watch Docker & dependency caches warm automatically
Keep all existing GitHub secrets, OIDC tokens, and actions/checkout steps. Every job runs in a fresh VM with regional NVMe build cache attached.
# Second run hits persistent NVMe BuildKit & package caches automatically
# Billing stops at $0.00/hr the exact second the job completes VS GITHUB ACTIONS FAQ
Common questions about drop-in uncage.sh CI runners.
01 Do I have to rewrite my GitHub Actions YAML files?
No. You only change the runs-on label (for example, runs-on: uncage-4vcpu). All GitHub Marketplace actions, workflow triggers, matrix strategies, artifacts, and repository secrets continue working identically.
02 Are uncage.sh runners safe for private repos and secrets?
Yes. Every single job boots a brand-new, hardware-isolated ephemeral microVM that is destroyed immediately after the job completes. Secrets are never shared across builds or tenants.
03 Why are builds faster even at the same core count?
Two factors: dedicated high-clock CPUs paired with local NVMe storage, plus persistent regional Docker BuildKit and language package caches so jobs skip repetitive cold downloads and rebuilds.
04 Can I keep macOS jobs on GitHub and move only Linux jobs to uncage.sh?
Yes. Because runner selection is per-job via runs-on, many teams move 100% of their Linux build, test, and Docker jobs to uncage.sh while keeping iOS/macOS jobs on GitHub-hosted macOS runners.
1-LINE CI UPGRADE
Cut your GitHub Actions bill and build times in half.
Clean ephemeral VMs, persistent NVMe Docker caching, and exact per-second billing—zero cluster ops.
✓ $10 starter credit on signup
✓ Strictly $0.00/hr compute when sleeping
✓ Sub-second boot across 4 global regions