Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

CI runner VPS

Canadian VPS hosting for CI runners

Run build jobs on your own Linux VPS. Choose CPU, memory and disk space for the jobs, and keep build secrets out of untrusted workloads.

Hosting options

Compare the services for your project.

Your requirements

What does your project need?

01

Runtime and processes

Check a self-hosted CI runner whose jobs can consume CPU, RAM, disk, network, secrets, and untrusted build inputs, so isolation and cleanup need deliberate limits.

02

Data to protect

Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.

03

Network access

List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.

04

Deployment and maintenance

Check how the service starts after a reboot, where logs are stored and who applies updates. Test a deployment and rollback without changing live customer data.

Field guide

CI runners need limits, cleanup, and isolation

A CI runner executes untrusted code by design, so treat the server as disposable and isolated: no production credentials beyond scoped deploy keys, no access to internal services it does not need, and resource limits per job. Builds consume CPU in bursts and disk in layers, caches, and artifacts, which makes disk the resource that runs out first.

Concurrency is the sizing dial: each parallel job needs its own CPU share, memory for the build toolchain, and working space on disk. Cap the number of concurrent jobs to what the server can feed, set job timeouts so a hung test suite cannot hold the runner all day, and clean workspaces after every job.

01

Ephemeral job environments

Run each job in a fresh container or a cleaned workspace. Leftover state between jobs makes builds pass or fail for reasons nobody can reproduce.

02

Cache size ceiling

Put a size cap and expiry on dependency caches. An unbounded cache grows until it fills the disk and fails every job on the runner.

03

Secret scoping rules

Give the runner only the secrets its jobs require and keep fork or external builds away from them. CI logs have a long history of leaking printed environment values.

Planning

Access, backups and handover

Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.

Free guide

Canadian VPS hosting for CI runners: planning checklist

Use the detailed checklist to plan setup, access, migration and recovery with your team.

Download PDF →
Help choosing

Tell us about your project.

Send us the software you use, your storage needs and your launch or moving date.

Ask about hosting

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move