/ BLOG
Notes from the runner.
Benchmarks, cost write-ups, and engineering posts about running GitLab CI in production. Honest data, no marketing fluff — we ship what we measure.
From autoscaling to always-on: a self-hosted GitLab CI story
A payment-gateway aggregator on self-hosted GitLab couldn't use GitLab.com shared runners. We took them from an AWS autoscaling fleet, through a Hetzner autoscaler, to five always-on boxes — which have now run their pipelines for nine months without the cold starts, cache misses, or surprise invoices.
Read post →
We benchmarked GitLab.com shared runners against our managed Hetzner runners. Here's the data.
Real wall-clock and per-job timings from a 13-job Symfony pipeline on GitLab.com shared vs Runsetters managed runners (from €17/mo billed annually). One small box loses on wall-clock; two boxes reach parity. Plus the cost math that decides which you should be on — and what we found when we tested dedicated hardware.
Read post →