RUNSETTERS

/ MANAGED GITLAB RUNNERS

Stop holding your GitLab runners together with duct tape.

Managed GitLab runners on Hetzner bare metal. We handle the infrastructure, you ship pipelines. Online in two minutes. Works with any GitLab instance — gitlab.com, self-hosted, on-prem behind VPN.

.gitlab-ci.yml

build:
  tags:
- - shared-runners      # slow, queued, scrape minutes
+ - runsetters-standard # always warm, fixed €78/mo

Get started → See pricing

5 plans from €39/mo. 2-minute setup. Cancel anytime.

/ WHY RUNSETTERS

Three things a DIY runner box can't give you.

Managed = one email, not 12 sysadmin hours

We provision, we monitor, we recreate when something breaks. You paste a GitLab token and get back to your pipeline.

Any GitLab instance

gitlab.com, gitlab.yourcompany.dev, on-prem behind a VPN — the runner makes an outbound connection to your GitLab. Nothing special on your side.

Bare metal, fixed monthly, always warm

AMD EPYC vCPU. Docker layer cache always on SSD. €78 is €78 — no "what did CI cost this month" surprises.

/ HOW IT WORKS

Three steps. About two minutes. Zero infra to maintain.

Pick a plan

Choose a machine size based on your CI workload. Change plans anytime from your dashboard — we handle the prorate and recreate the box on the new size.

Paste GitLab token

Open Settings → CI/CD → Runners in your GitLab, click "New runner", paste the registration token into Runsetters.

Online in 2 minutes

We provision a Hetzner CCX box, install gitlab-runner, register it with your GitLab. Status flips to live in your dashboard.

/ PRICING

Fixed monthly. No setup fee. Cancel anytime.

Every plan includes always-on Docker layer cache, monitoring, automatic runner version updates, downtime email alerts, and master SSH access for our support.

Starter

€39 /mo

vCPU: 2
RAM: 8 GB
SSD: 80 GB
Concurrent: 2

Light CI workloads, hobby projects, single repo. Includes 24-hour free trial.

Get Starter

Standard

€78 /mo

vCPU: 4
RAM: 16 GB
SSD: 160 GB
Concurrent: 4

Most popular. Multiple repos, parallel jobs, Docker builds with cache.

Get Standard

Pro

€165 /mo

vCPU: 8
RAM: 32 GB
SSD: 240 GB
Concurrent: 8

Larger teams with heavy CI. Microservices, integration test suites.

Get Pro

Heavy

€289 /mo

vCPU: 16
RAM: 64 GB
SSD: 360 GB
Concurrent: 12

Heavy parallelism, large monorepos, build-intensive jobs.

Get Heavy

Beast

€549 /mo

vCPU: 32
RAM: 128 GB
SSD: 600 GB
Concurrent: 24

Maximum throughput. ML training pipelines, big data CI, kernel-style builds.

Get Beast

Need 2+ runners, a private Docker registry mirror, or a dedicated IPv4? Email us.

/ COMPARE

Runsetters vs. running your own runner boxes.

	Runsetters	DIY self-managed	GitLab.com hosted
Any GitLab instance	[ok]	[ok]	[no]gitlab.com only
Who runs the infra	us	you	GitLab
Setup effort	paste token	scripts + sysadmin	0
Time to online	~2 min	hours/days	instant
Predictable bill	[ok]fixed mo	[ok]Hetzner direct	[no]per-min
Bare metal CPU	[ok]AMD EPYC	varies	[no]shared
Health monitoring	included	you write it	included
Auto runner version updates	[ok]	you do it	[ok]

The bottom line: this is cheaper than the DevOps engineer who'd otherwise be maintaining your runner boxes. The Standard plan is €78/mo — less than half a day of engineering time per month.

/ FAQ

Frequently asked questions.

Whose Hetzner account runs the box — yours or ours? +

Ours. You paste a GitLab token, we handle infrastructure, billing, and renewals. Our Hetzner account, our responsibility.

What happens if a runner goes down? +

Health checks every 60 seconds (GitLab API + node_exporter). If a runner is unresponsive for more than 10 minutes, you get an email and we get an admin alert. We recreate the box and email you when it is back online.

Can I SSH into the machine? +

Yes. Add your public SSH key in Advanced settings during provisioning. We keep a master key for support and emergency access.

Which regions do you support? +

Hetzner Falkenstein, Helsinki, and Nuremberg today. US locations (Hillsboro/Ashburn) when there is enough US demand.

Does it work with self-hosted GitLab behind a VPN? +

Yes. The runner makes an outbound HTTPS connection to your GitLab — nothing on your side needs to be publicly reachable. Long-poll, no inbound connections.

How does billing work? +

Paddle (Merchant of Record). VAT and sales tax are handled automatically. Monthly card billing, first charge at signup, recurring on the same date. Adding or removing a Slot mid-cycle is settled by daily proration (UTC days, partial days count as full days).

Do I need to stop my runner overnight or on weekends to save money? +

No. Slots are billed monthly flat — a runner that runs 24/7 costs the same as one that runs 8h a day. Perfect for distributed teams where pipelines fire across time zones. You only pay extra (daily proration) if you spin up a temporary Slot mid-cycle for a bursty workload, not when individual jobs idle.

Can I upgrade my plan? +

Yes. Click Upgrade in your dashboard and pick a larger plan — the prorated difference goes onto your next renewal invoice, the runner is recreated on the new machine size (~2 min downtime), and your runner identity stays the same so no GitLab token re-paste is needed. The runner IP changes, so update any firewall allowlists. Downgrades to a smaller plan are processed manually — email hello@runsetters.com.

What is your abuse policy? +

No crypto mining, port scanning, DDoS, or spam. We reserve the right to suspend without refund. See Terms for the full list.