Builds in bursts
A push, a build, then quiet. Shared cores are the better buy for work that comes and goes. CI runners, several services side by side, or a busy game server.
Build runners, staging and dev boxes, with root.
Build runners, staging copies and dev boxes with root, reinstalled from the panel whenever you need a clean one. On the AMD EPYC 4584PX at up to 5.7 GHz per core, with DDR5 memory and NVMe storage, in Mumbai, Singapore and Limburg.
One job per processor, and memory for each.2 GB per vCPU on every VPS, 4 GB per core on every VDS.
VPS Mini
2 jobs x 2 GB
VPS Growth
4 jobs x 2 GB
VPS Pro
6 jobs x 2 GB
VPS Max
10 jobs x 2 GB
VPS Titan
12 jobs x 2 GB
VDS MicroCore
2 jobs x 4 GB
VDS FusionCore
4 jobs x 4 GB
VDS OmniCore
6 jobs x 4 GB
VDS TitanCore
12 jobs x 4 GB
One tile is one parallel job, the usual starting point for a build (make -j$(nproc) starts one per processor the server reports), and the figure is the plan's memory split evenly between them. A link step or a test suite that needs more memory than that runs fewer jobs at once.
Size for how often you build. Bursts share cores well. All-day load wants more, or cores of its own.
Builds all day
A queue that never empties needs more vCPUs to spread the jobs over. Heavy compute: build servers, render queues, analytics jobs.
Services that should not wait
Staging databases, test environments that time things, or several services side by side, each on cores allocated to your server. Several production services on one machine, each with cores of its own.
47 images to start from. 9 families of Linux, BSD and Windows Server, plus a handful of other Linux distributions.
Pick one at checkout, rebuild any time
A rebuild from the panel installs a new image on a fresh disk, whenever you want a clean machine.
Images per family
Counted from the list on the operating systems page.
- Fedora8
- Ubuntu7
- FreeBSD7
- Debian4
- AlmaLinux4
- Rocky Linux3
- CentOS3
- Alpine Linux3
- Windows3
- Other Linux5
Image
- Ubuntu26.04 LTS
- Debian13
- AlmaLinux10
- Rocky Linux10
- FreeBSD15.0
- Windows2025
SSH keys1 selected
Type the server's name to confirm
growth-mumErases the whole disk. No undo.Rebuild server
Break it, then get back in. Keys at build time, a console when SSH is gone.
SSH keys, placed at build time
Add your public key to your account and it is written to a server when that server is built or rebuilt.
A console in the browser
The panel's console shows the server's screen and still works when SSH, the firewall or the network configuration is broken.
A clean rebuild when all else fails
A rebuild installs a fresh operating system and erases the disk, with no undo, so keep code in a repository and data off the server.
Outgrow a size without starting over. Nothing is reinstalled, and your data stays put.
Straight away
vCPU and traffic change while the server keeps running. Pro to Max, as an example.
At the next restart
Memory and NVMe take effect when the server boots again. Restart from the panel when it suits you.
Development and CI questions
Is there hourly billing?
No. Every plan is billed monthly, and prices exclude GST. For environments you throw away and rebuild often, keep the server and reinstall it from the panel rather than cancelling and ordering again.
Can I run Docker and containers?
Yes. Each server is a KVM virtual machine with its own kernel and Full root / Administrator access, so Docker, Podman and container runtimes install as they would on any Linux server.
Can I use it as a self-hosted CI runner?
Yes: GitHub Actions, GitLab and most other CI systems have a runner that installs on Linux or Windows Server and connects out to the service, so it needs no inbound port.
How do SSH keys work?
Add your public key to your account, and it is placed on a server when that server is built or rebuilt. Adding a key later does not reach servers that already exist; add it on the server itself.
What if I lock myself out?
Open the console from the panel. It shows the server's screen in your browser and keeps working when SSH, the firewall or the network configuration is broken.
Does a reinstall keep my files?
No. A rebuild installs a fresh operating system and erases everything on the disk, with no undo. Copy off anything you need first.
Can I take a snapshot before a risky change?
Not from the panel. Scheduled snapshots are included only where your plan says so, and support restores them on request. Keep your code in a repository and your data backed up off the server, so a rebuild costs you nothing.
Can I move to a larger plan later?
Yes. CPU and traffic change straight away; memory and disk take effect at the next restart. Nothing is reinstalled.
Start with Pro. Rebuild it as often as you like.
6 vCPU and 12 GB at up to 5.7 GHz, with 17 Tbps upstream mitigation and Prism on every plan.