Pico KVM
The low-cost entry
This page
Small projects, test systems, bots, VPN endpoints.
- CPU
- Shared vCores (1 vCore = 1 CPU thread, shared with other instances)
- Virtualisation
- Full virtualisation with KVM (Proxmox VE): own kernel, own operating system, own ISO files. No LXC, no OpenVZ, no containers.
- Availability
- No commitment (best effort)
- Minimum term
- 1, 6 or 12 months, depending on the plan
- Traffic
- Traffic included. If traffic over the last 24 hours exceeds 1 TB, the server is temporarily limited to 100 Mbit/s.
Websites, shops, applications, game servers, development.
- CPU
- Shared vCores (1 vCore = 1 CPU thread, shared with other instances)
- Virtualisation
- Full virtualisation with KVM (Proxmox VE): own kernel, own operating system, own ISO files. No LXC, no OpenVZ, no containers.
- Availability
- 99.2 to 99.6 % annual average (committed: 99.2 %)
- Minimum term
- 1, 6, 12 or 24 months
- Traffic
- Traffic included. If traffic over the last 24 hours exceeds 2 TB, the server is temporarily limited to 200 Mbit/s.
RS Root Server
Dedicated cores
Production services, databases, container platforms.
- CPU
- Dedicated vCores (1 vCore = 1 pinned thread of an AMD EPYC 7713, 7763 or 7543, never overbooked)
- Virtualisation
- Full virtualisation with KVM (Proxmox VE): own kernel, own operating system, own ISO files. No LXC, no OpenVZ, no containers.
- Availability
- 99.5 % annual average
- Minimum term
- 1, 6, 12 or 24 months
- Traffic
- Traffic included. If traffic over the last 24 hours exceeds 3 TB, the server is temporarily limited to 300 Mbit/s.