CryptoServers

Dev sandbox / CI runners in Switzerland

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

No KYC DMCA ignored Crypto only 60-second deploy
1 Tbps
DDoS absorption
41s
Median deploy
Zürich (CH-ZRH)
Datacenter
$54.99
Entry plan / month
Why Switzerland

The Switzerland case for Dev sandbox / CI runners

Switzerland is the strongest privacy-law jurisdiction we operate. The Federal Act on Data Protection (FADP, revised 2023) puts the onus on the data controller, not the host. Swiss court orders are required to compel any disclosure; foreign DMCA notices have no statutory effect at all. Network is Tier-1 with direct peering to Frankfurt, Milan, and Paris. Zürich is the comfortable pick for workloads where the legal posture matters as much as the throughput: mail servers, financial nodes, journalist infrastructure.

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 Switzerland

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.
Sysadmin FAQ

Dev sandbox / CI runners in Switzerland — 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.

Deploy Dev sandbox / CI runners in Switzerland

From $54.99/month, paid in crypto, no email or ID required.