VServer
A VServer is a virtual machine you get root on. One public IPv4 address, an IPv6 block, an operating system image you choose at order time, and nothing else between you and the machine. Everything above the virtual hardware is yours: you install it, you patch it, you secure it, you back your data up.
Plans
| Plan | vCPU | RAM | Disk |
|---|---|---|---|
| VServer S | 2 | 4 GB | 60 GB NVMe |
| VServer M | 4 | 8 GB | 120 GB NVMe |
| VServer L | 8 | 16 GB | 240 GB NVMe |
| VServer XL | 12 | 32 GB | 360 GB NVMe |
Current prices are on the VServer product page. Billing is hourly with a monthly cap, which is not the same thing as a monthly plan, so read Billing before you order more than one.
You can move between plans later, with one restriction that is easy to walk into: the disk can only grow. See Changing the plan.
Operating system images
| Image | Version |
|---|---|
| Debian | 13 |
| Ubuntu LTS | 24.04 |
| Rocky Linux | 10 |
| Fedora | 43 |
| Alpine Linux | 3.24 |
| Arch Linux | rolling |
| openSUSE Leap | 15.6 |
| Flatcar Container Linux | stable |
These are cloud images. They boot once, take the hostname, the network configuration and your SSH key, and after that the machine is yours. Picking a different image later means a reinstall, which erases the disk.
You cannot upload your own ISO.
What every plan includes
- One public IPv4 address and an IPv6
/112block, see Networking - Up to 3 snapshots, see Snapshots
- A browser console that works even when the network inside the server does not
- CPU, memory, disk and network graphs for the last hour, day, week or month
- Email alerts when the server goes down unexpectedly or a filesystem fills up
- Traffic is not metered and not billed
What a VServer is not
- Not managed. Nobody patches the operating system, rotates your logs or watches your services. If that is what you want, a Kubernetes namespace puts the platform in charge of the runtime instead.
- Not highly available. Your server runs on one machine. If that machine fails, your server is down until it is back. There is no automatic failover and no live migration to hide it from you.
- Not backed up in a way you can restore yourself. Snapshots are yours to take and roll back. The off-site backups behind them are a support request, not a button. See Backups.
- Not extensible with more IPv4 addresses. One address per server, and no way to order a second one.
What's next
- Ordering and first access to get a server and log in
- Billing for what hourly-with-a-cap actually costs