We don't hide the hardware

Specifications you can verify, without vague labels.

These figures are reported by the live production game node. We distinguish verified guest-visible resources from upstream physical details the VPS does not expose.

Production game node

Host CPU modelAMD Ryzen 9 9950X 16-Core Processor
CPU visible to node8 vCPU threads
Memory visible to node47 GiB (48 GB class)
Server volume300 GB non-rotational virtual disk
Operating systemDebian 12 (Bookworm)
Region / test endpointGermany / 94.103.173.70
We do not advertise this node as a 9950X3D, DDR5 or physical NVMe system because those details are not exposed to and therefore cannot be verified from the guest OS.

What a plan limit means

Pterodactyl expresses CPU as a percentage: 100% is up to one CPU thread, 200% is up to two, and 400% is up to four. Each product also states its RAM and disk allowance. These are container limits, not promises that a game will efficiently use every allocated thread.

Backups and protection

Plans can include panel-managed snapshots and schedules. The quota and configured frequency vary by product; we do not claim a universal backup interval. Public game allocations use explicit firewall rules and the node runs upload scanning and container isolation controls.

Match the plan to the workload.

Compare stated CPU, memory and storage limits before checkout.

Compare game plans