Dev sandbox / CI runners in Netherlands

Self-hosted GitHub/GitLab runners, ephemeral preview envs, build farms — on hardware you didn't lease through a corporate billing system.

Netherlands: EU member — GDPR applies. Foreign DMCA notices declined in writing by default. Dutch court order required for takedown.

See plans from $54.99/mo About Netherlands

No KYC DMCA ignored Crypto only 60-second deploy

1 Tbps

DDoS absorption

41s

Median deploy

Amsterdam (NL-AMS)

Datacenter

$54.99

Entry plan / month

Why Netherlands

The Netherlands case for Dev sandbox / CI runners

Amsterdam is the densest internet exchange in Europe. AMS-IX peers with 800+ networks; the median RTT to London, Frankfurt and Paris is under 10 ms. The Dutch legal regime is EU-standard — GDPR applies, but takedowns require a court order and the threshold is high in practice. We pick Amsterdam when network performance matters more than legal exoticism: gaming, low-latency relays, federated services with European users.

Self-hosted CI runners (act, Earthly, Drone, GitLab Runner, GitHub Actions self-hosted) avoid the per-minute meter, the security boundary problems with cloud runners, and the slow restart times of GitHub-hosted-runner cold-starts. KVM with full root + nested virt + custom kernel modules means anything Docker-in-Docker, Kata, or microVM (Firecracker) runs without special handling. Ephemeral preview environments per pull request fit cleanly on vps-business with a Docker layer.

Workload alignment

What Dev sandbox / CI runners gets from Netherlands

Full KVM, nested virt, kernel modules. Docker-in-Docker, Kata Containers, Firecracker all work.

41-second deploy median. Spin up an ephemeral env per PR in less time than your test suite runs.

AMD EPYC 9454P on Scale tier — the same hardware that powers GitLab.com's shared runners.

No corporate AUP gotchas. Run anything from kernel fuzzing to chaos-engineering chaos.

Crypto-native billing — pay by the month, no payment-failure surprises in your CI pipeline.

Plans

Dev sandbox / CI runners — Netherlands plans

Plans below ship from Netherlands (Amsterdam (NL-AMS)) by default. Pick the cheapest that matches your projected load — hot-resize is live.

VPS

Pro

Intel Xeon Gold 6430 · Amsterdam (NL-AMS)

8 vCPU
24 GB DDR5 ECC
400 GB NVMe
5 Gbps unmetered

$54.99/mo

Deploy in Netherlands

VPS

Scale

AMD EPYC 9454P · Amsterdam (NL-AMS)

12 vCPU
32 GB DDR5 ECC
640 GB NVMe
10 Gbps unmetered

$69.00/mo

Deploy in Netherlands

Dedicated

Shield

AMD EPYC 7313P · Amsterdam (NL-AMS)

16 cores · 32 threads
64 GB DDR4 ECC
2× 1 TB NVMe
1 Gbps unmetered

$79.00/mo

Deploy in Netherlands

Sysadmin FAQ

Dev sandbox / CI runners in Netherlands — questions answered

Will Docker-in-Docker work on KVM here?

Yes — we ship CONFIG_KVM and nested virt enabled on every host. dind, sysbox, gVisor, Kata Containers and Firecracker microVMs all work without sysctl edits or kernel rebuilds.

How many concurrent CI jobs can I run on a vps-pro?

Depends on the workload. Typical Go/Node/Python builds: 6–10 concurrent on vps-pro's 8 vCPU. C++/Rust LTO builds: 2–3. Browser-based E2E with headless Chromium: 4–6. Beyond that, Scale tier or ded-shield for sustained load.

Can I run GPU workloads or just CPU?

CPU only — we don't offer GPU instances. For ML CI or rendering, a different host is the right answer. Most CI doesn't need GPU.

How do I keep the CI secrets safe on a remote host?

Same way you would on any self-hosted runner: encrypt at rest (LUKS), use ephemeral runners (re-imaged per job), keep the long-lived secrets in your CI orchestrator and let the runner pull them at job start. We don't have visibility into the runner instance — full root means full responsibility.

What if I need to scale up for a release week?

Hot-resize works on every VPS plan — vCPU and RAM are live; disk needs one reboot. Or spin a temporary scale instance for a week and destroy it after. Our crypto billing doesn't penalize partial-month usage; you pay for what you use proportionally.

Other jurisdictions