Production game node
| Host CPU model | AMD Ryzen 9 9950X 16-Core Processor |
|---|---|
| CPU visible to node | 8 vCPU threads |
| Memory visible to node | 47 GiB (48 GB class) |
| Server volume | 300 GB non-rotational virtual disk |
| Operating system | Debian 12 (Bookworm) |
| Region / test endpoint | Germany / 94.103.173.70 |
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.
Compare stated CPU, memory and storage limits before checkout.