Hosting your continuous integration runners
Your own runners: no more billed minutes, and a cache that survives from one build to the next.
Starting at from €13.99/mo
Introduction
Continuous integration minutes get expensive as soon as builds become frequent or long. Hosting your own runners on a VDS changes the equation: a fixed monthly price whatever the number of builds, and a server you can size for what you actually compile.
The second gain is less obvious but often more noticeable: the cache persists. On a self-hosted runner, downloaded dependencies, image layers and intermediate artefacts stay put from one build to the next. Many pipelines drop from several minutes to tens of seconds on that alone.
The L plan at €26.99/month and its 8 vCore comfortably covers two or three parallel runners. Isolate them in separate VMs rather than shared containers: a build runs arbitrary code, and that is precisely what you want to keep away from the rest of the server.
What the server brings, across the whole range
Proxmox VE already installed
The server arrives with <strong>Proxmox VE</strong> in place and its web interface reachable. You create your virtual machines and LXC containers from the browser, without a support ticket or a wait. <strong>Reinstalls are unlimited</strong>: an experiment that goes wrong is redone in minutes.
RAM, because that is what runs out first
On a hypervisor it is almost never the processor that caps out first: it is <strong>memory</strong>, because every virtual machine reserves its own. The range starts at <strong>16 GB</strong> and goes up to <strong>96 GB</strong>, which leaves room to stack several VMs without starving them.
Unlimited snapshots and backups
A snapshot before an update, another before a configuration change: that is what separates a test from a gamble. Neither the count nor the frequency is billed, so nothing discourages taking one more.
Up to 16 additional IPv4 addresses
Each VM can hold its own public address, which avoids routing everything through port forwards on the host. Useful as soon as a virtual firewall, a web server and a third-party service have to coexist cleanly.
What you gain
A fixed price
Building a hundred times a day costs the same as ten. For a team that integrates often, the gap with per-minute billing widens quickly.
A cache that stays
Dependencies, image layers, artefacts: everything that used to be re-downloaded stays local. It is often the most visible gain.
Choose your machine
A project that compiles for a long time benefits from the L plan's 8 vCore. On a shared service you take the machine you are given.
Keep the code at home
The repository and artefacts never leave a server you control, in a French datacenter. For some projects that is not a detail.
Test across environments
One VM per language or distribution version, all on the same server, all resettable from a snapshot.
Frequently asked questions
VM, without hesitation. A build runs arbitrary code, sometimes from an outside contribution. A VM isolates that code from the rest of the server; a shared container much less so.
The L plan at €26.99 with 8 vCore suits two or three parallel runners. Move up if your builds are long or the team integrates continuously.
A snapshot taken on the freshly configured VM serves as reference. Restoring takes seconds and guarantees no build left residue behind.
For the execution part, yes. The interface, repository management and orchestration stay with your provider: you only move the machine that does the work.