VPS KVM NVME

The processor, the storage and the virtualisation. The NVMe and SSD ranges run in OpenVZ containers on Xeon E5, and differ from each other only by the disk technology: NVMe for the former, SATA SSD for the latter. The KVM range runs on full virtualisation, on Xeon E5 as well. The Ryzen range also runs on KVM, on high frequency Ryzen 9, for anything that depends on single core power. The table above compares RAM, vCPU and storage line by line.

Including tax. VPS is a consumer offer, so the prices shown include VAT: the one you see is the one you pay. It is worth checking when you compare us with another host, because many of them display prices excluding tax: at 20% VAT, a price excluding tax looks 20% lower without anything changing for you. Our business offers — colocation, transit, ASN, FTTO — are shown excluding VAT, and say so in full.

It depends on the range, and the difference matters before you order. The NVMe and SSD ranges run on OpenVZ: these are containers, sharing the hardened kernel of the host machine. Docker works there, but some options are limited, precisely because the kernel is hardened and is not yours. The KVM and Ryzen ranges run on KVM, that is to say full hardware virtualisation: you have your own kernel, you load the modules you want and nothing is restricted on that side. If your application needs kernel modules, particular mounts or advanced Docker options, take the KVM or Ryzen range — and if you have any doubt about your case, ask us before ordering rather than after.

It depends on the range, just as virtualisation does. The NVMe and SSD ranges run as OpenVZ containers on a shared Linux kernel, so what goes on them is a Linux distribution — Ubuntu, Debian, AlmaLinux, Rocky Linux. Neither Windows nor pfSense is possible there, and that is not a matter of paying for an option: the first is not Linux, the second is built on FreeBSD, and neither runs on a Linux kernel that is not its own. The KVM and Ryzen ranges use hardware virtualisation: the machine really is yours, any system installs on it including pfSense, and Windows is available as a paid option. You can also start from a blank installation there and put whatever you want on it.

Baseline filtering is in place on our AS212815 network, and it runs for everybody at no extra cost. Our network can absorb large volumetric attacks — we do it every day. What a VPS does not pay for is doing that continuously and over time: the traffic is paid for in transit, and that is not what a VPS at a few euros a month covers. If you host something exposed and the attack could last, the Anti-DDoS Pro option is what you want: it is sized case by case, so tell us what you are hosting.

The bandwidth is symmetric — as much upstream as downstream — and its speed is given offer by offer in the table above. The volume transferred works on a fair use basis: we do not count gigabytes and we do not bill overage, but there is no guarantee of permanent throughput at full load either. If your project consumes transit continuously, tell us before ordering and we will point you to the right offer.

Yes, on your own from your client area: you move from one offer to another without going through us. If you already know your needs are going to move, the one thing to get right at the start is the virtualisation, OpenVZ or KVM: that is the part you would rather not have to change halfway.

A VPS covers the vast majority of needs: a website, an application, a business service, a development environment. There are two cases where it is not the right answer. If you need physical hardware of your own — for a licensing, compliance or disk volume constraint — colocation is what to look at, where you place your own machines in our racks. And if you are only looking to host a website without administering a server, our web hosting will cost you less and ask less work of you.