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.
CI runner VPS
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
Self-managed virtual servers with administrator access, NVMe disks, shared vCPU, dedicated IPv4 and IPv6. RAM uses ballooning. Backups are sold separately.
See VPS hosting →02Canadian SFTP storage for your backup software. Check physical separation from your source server before treating a copy as off-site.
See Backup storage →03Register or transfer a domain and manage DNS. Registration and renewal prices depend on the extension.
See Domains →04Tell us what you need to host and when it needs to be ready.
See Ask about your project →Your requirements
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.
Identify databases, uploads, volumes, configuration and secrets that cannot be rebuilt from the application code. Back them up and test a restore.
List the ports that must be public and those that should remain private. Configure authentication, TLS and firewall rules before accepting traffic.
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
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.
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.
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.
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
Confirm the current product specifications and service responsibilities. Record who can approve a change and how to recover the service if it goes wrong.
Use the detailed checklist to plan setup, access, migration and recovery with your team.
Download PDF →Send us the software you use, your storage needs and your launch or moving date.
Ask about hostingYour 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.