Cloud servers with dedicated vCPU — 2 to 48 cores, 8 to 192 GB RAM, local disk. You pick the size, the region and the operating system at checkout, and you administer the machine yourself.
Your vCPU allocation is dedicated, not shared. Sizes run from 2 to 48 cores.
Disk is local to the machine, not network-attached. Capacity is fixed per size, from 80 GB to 960 GB.
Choose your region at checkout: Germany, Finland, US East, US West or Singapore. DDoS scrubbing at the network edge.
AlmaLinux, Rocky, Debian, Ubuntu or CentOS Stream, chosen at checkout and installed for you.
Unmanaged by default — the machine is yours. Ongoing management is a separate engagement we quote per case.
Imunify360 runs on our shared hosting node today. Bringing it to Dedicated CPU servers is on the roadmap — it is not something we sell yet.
A cloud server whose vCPU allocation is dedicated to you rather than shared with other tenants. You get the whole machine instance, administer it yourself, and it has a fixed published spec. It is not bare metal — we do not sell physical servers.
Workloads that suffer when CPU is contended — busy databases, CI runners, application servers. If your load is light or bursty, a VPS is cheaper and enough.
You get root and the machine is yours to configure. The console lets you pause and resume the server; reboots, rebuilds and everything else are done over SSH or by asking us.
Not meaningfully. Dedicated vCPU is about consistent performance, not a stronger security boundary. Both lines are virtual machines you administer yourself, and either one is as secure as you configure it.
Yes, but not in place. There is no resize button — you order the size you want and move your data across. Talk to us first and we will plan it with you.
Tell us the CPU and RAM you need, the OS and which region. We will point you at the right size.
