Clipper 8
- vCPU
- 4 × dedicated
- RAM
- 8 GB
- Storage
- 200 GB NVMe Gen4 SSD
- Transfer
- 20 TB
- IPv4 / IPv6
- 1 / /64 routed
Solution
Game servers are single-thread bound, so clock speed beats core count. For Minecraft with 10–20 players, 4 GB of RAM on a high-frequency core is the practical floor; CS2 and Rust want 8–16 GB. Pick the Clipper line for its 5.0 GHz turbo, and place the instance within about 60 ms of the majority of your players — latency matters far more than raw hardware.
| Resource | What you actually need |
|---|---|
| CPU | High single-thread clock. 4 dedicated cores for a 20-slot server |
| RAM | 4 GB (Minecraft vanilla) / 8 GB (modded, CS2) / 16 GB (Rust) |
| Disk | NVMe — chunk and map loading is IO-bound |
| Transfer | 10 TB covers a busy 40-slot server |
| Protection | Always-on DDoS filtering; game servers are attacked constantly |
Location is usually the decision that matters most for this workload — either because latency dominates, or because jurisdiction does.
Use the latency table on the location page; aim for under 60 ms for the majority.
Four dedicated cores and 8 GB is the sensible starting point for most games.
Pterodactyl gives you a web UI; a systemd unit is simpler if you run one server.
Minecraft 25565/tcp, CS2 27015/udp, Rust 28015/udp. Leave everything else closed.
Enable nightly encrypted backups, or rsync the world directory to a Hold instance.
Vanilla with 10 players runs comfortably in 4 GB. Add roughly 100 MB per additional player, and double the total for a heavily modded pack.
Yes for anything with real-time physics. Shared cores introduce steal time, which shows up as tick lag exactly when the server is busiest.
Yes. Checkout is crypto-only and requires nothing but an email address you control.