Best VPS for Pterodactyl: One Command Tells You If It'll Work
Run this on any VPS before you commit to it:
systemd-detect-virt
If it returns kvm, you’re fine. Pterodactyl’s own Wings documentation is unusually direct about why:
“When your provider uses [OpenVZ] virtualization, you will most likely be unable to run Wings. Some providers have made the necessary changes for nested virtualization to support Docker. Ask your provider’s support team to make sure. KVM is guaranteed to work.”
And from the panel documentation:
“Pterodactyl does not support most OpenVZ systems due to incompatibilities with Docker.”
This is the single most important spec and it never appears in a comparison table. A cheap OpenVZ box with 16GB of RAM will not run Wings; a KVM box with 4GB will. We ran the command on our own server and it returned kvm — it takes a second and it’s definitive.
One more trap from the same docs: “some hosts install a modified kernel that does not support important docker features.” So even on KVM, check that Docker actually starts before building anything on top.
Pterodactyl is two workloads, and they want different things
This is what the brief for most Pterodactyl articles misses: you’re deploying two separate components with almost opposite requirements.
The Panel is a web application. Per Pterodactyl’s own install docs it needs:
- PHP (with additional repositories on most distributions)
- MySQL or MariaDB
- Redis
- A webserver — Apache, NGINX or Caddy
- Composer
- SSL certificates — and therefore a real domain name
It’s small. The panel is a Laravel application, and we measured a stock Laravel app at 58.7MB. Add MySQL and Redis and the panel side is a few hundred megabytes. The domain and SSL requirement is the part people forget — you cannot sensibly run the panel on a bare IP.
Wings is the opposite. It needs Docker, and it holds every game server container you run. This is where all your RAM and disk go, and where container spin-up makes disk speed matter.
So the honest architecture answer: on a small deployment, one box is fine. Once you’re running real game servers for other people, split them — the panel staying up while a node is thrashing is the entire point, and a panel that dies with its node can’t tell anyone what happened.
Sizing: sum your games, don’t guess a multiplier
We’re not going to give you a “20 small game servers on X GB” table. The brief asked for one with realistic overcommit figures, and we haven’t run Pterodactyl or measured Wings, so any multiplier we published would be invented.
Here’s the honest method instead, and it’s more useful because it uses numbers we did verify:
Start with the overhead. Panel plus MySQL plus Redis plus Wings and the Docker daemon — budget a few hundred megabytes to about a gigabyte before a single game server runs.
Then add each game at its real cost, which varies enormously:
| Game | Typical published requirement |
|---|---|
| Valheim (10 players) | 4GB+ |
| Palworld (10 players) | 6GB |
| Rust (40 players) | 8GB |
| ARK (30 players) | 10GB |
Those are hosts’ own published tiers, from our Valheim, Palworld, Rust and ARK research.
Read what that does to “five small servers”. Five Valheim worlds is 20GB+. Five Palworld worlds is 30GB. There is no meaningful “small game server” unit — the game determines everything, and a multiplier would be fiction.
On overcommit: Pterodactyl lets you allocate more memory than the host has, which works when servers are genuinely idle and fails badly when they aren’t. We have no data on safe ratios and won’t invent one. Start without overcommit and measure.
Two things that aren’t RAM:
- Disk speed matters at container spin-up, which is the moment users notice. NVMe is worth paying for here in a way it isn’t for a single game server.
- Port allocation flexibility. Every game server needs its own ports. Check your provider doesn’t firewall or restrict high port ranges by default, because that’s a support ticket you’ll hit on day one.
The hosts
Hostinger — its VPS line is literally branded KVM, which is exactly the virtualisation Pterodactyl guarantees. $11.99 renewal for 4GB, $14.99 for 8GB, root access and one-click Docker templates. The cleanest match to the requirement above, and the 8GB tier is a sensible starting node. Refund terms cover renewals if the build doesn’t work out.
ScalaHosting — actively markets Pterodactyl-oriented VPS plans, with its own SPanel instead of cPanel removing a licence cost. Confirm KVM and Docker readiness directly — we have not verified its current specifications.
UltaHost — $15.87 for 4GB with 3 vCPU, more cores per dollar than most, and its two-year rate is also its renewal rate. Cores matter here because Wings is running several game processes at once.
Hetzner — the most RAM per euro by a wide margin, which is the whole game when one box hosts many servers. We ran systemd-detect-virt on a Hetzner Cloud instance and it returned kvm — first-hand, though on one instance rather than a survey. Its dedicated CCX line is sold explicitly for “constantly high CPU usage”. Note availability limits since June and backups that exclude attached Volumes — relevant when your panel database is on one.
Cloudzy — $17.37 for 4GB billed monthly with no term, which makes it the low-risk way to test whether a provider’s virtualisation and kernel actually work before committing.
IONOS — a large European provider with competitive VPS pricing. We have not verified its virtualisation type, Docker readiness or current specifications, so run the check above on a monthly plan before committing.
What we’d buy
8GB KVM as a single-box starter, panel and Wings together, for a few servers among friends.
Split at the point you have users who aren’t you. A small box for the panel and database, a large one for Wings — and the panel survives whatever the node is doing.
And check systemd-detect-virt on day one, before you install anything.
How we checked this
The virtualisation requirements are quoted verbatim from Pterodactyl’s own documentation, read on 18 August 2026: the Wings installation page’s statement that OpenVZ providers “will most likely be unable to run Wings”, that “KVM is guaranteed to work”, the systemd-detect-virt check, and the warning that “some hosts install a modified kernel that does not support important docker features”. The panel dependency list — PHP with additional repositories, MySQL or MariaDB, Redis, a webserver, Composer and SSL certificates — and the statement that Pterodactyl “does not support most OpenVZ systems” are from its panel getting-started documentation.
We ran systemd-detect-virt ourselves and it returned kvm on our server, which is a Hetzner Cloud instance. That verifies the command works and what a correct answer looks like — it is not a survey of Hetzner’s fleet, and it says nothing about the other five providers.
The 58.7MB panel anchor is our own measurement of a stock Laravel application, not of Pterodactyl’s panel specifically. Pterodactyl is a substantial Laravel app with real models and dependencies, so it will use more — we’re using the figure to establish that the panel side is small relative to Wings, not to size it.
The per-game RAM figures are hosts’ published plan tiers gathered across this series, not measurements. They vary by player count and configuration, and they’re offered to show that games differ by several times — not as specifications.
The brief asked for a sizing table at 5, 10 and 20 game servers with realistic overcommit, and there isn’t one. We have not installed Pterodactyl, run Wings, or measured a single container, so we have no basis for a per-server figure or a safe overcommit ratio. Publishing one would be the most confidently wrong thing in this article, given how much the answer depends on which games you run.
We also did not verify any provider’s disk IOPS, port-allocation policy, or whether nested virtualisation restrictions apply — three things the brief asked us to rank on. The check we’ve given you tests the most important of them in one command, which is the best we can offer without accounts.
On ScalaHosting, Cloudzy and IONOS we have no verified current specifications; Hostinger’s and Hetzner’s details are from this series rather than re-read today.
One thing worth knowing that isn’t about hosting: a successor panel called Pelican now exists, describing itself as a free open-source Docker-based game panel with copyright dated 2024–2026. We have not verified its relationship to Pterodactyl or compared them, but if you’re choosing a panel today rather than hosting for one you already run, it’s worth looking at before you commit.
What we did not do: install Pterodactyl or Wings, run a game server through a panel, measure container memory or spin-up time, or hold an account with any provider here.
The host links above are affiliate links. The most valuable thing in this article is a free one-line command that tells you whether a server will work before you pay for it.
FAQ
What VPS do I need for Pterodactyl?
A KVM one. Pterodactyl’s documentation states OpenVZ providers most likely can’t run Wings and that “KVM is guaranteed to work”. Check with systemd-detect-virt before buying.
How do I check if a VPS supports Pterodactyl?
Run systemd-detect-virt. If it returns kvm you’re in good shape. Then confirm Docker actually starts, because some hosts ship modified kernels missing features Docker needs.
Can I run Pterodactyl on OpenVZ?
Pterodactyl’s own docs say most OpenVZ systems are unsupported due to Docker incompatibilities. Some providers enable nested virtualisation — ask support, and don’t assume.
How much RAM does Pterodactyl need?
The panel itself is small — it’s a Laravel app plus MySQL and Redis. Wings is where the memory goes, and the total depends entirely on which games you host: Valheim wants 4GB+, ARK 10GB.
Should the panel and Wings be on the same server?
Fine for a few servers among friends. Split them once other people depend on it, so the panel stays reachable when a node is under load.
Does Pterodactyl need a domain name?
Effectively yes — the panel requires SSL certificates, so plan on a real domain rather than running it on a bare IP.
What about overcommitting memory?
Pterodactyl allows it, and it works while servers are idle. We have no data on safe ratios and won’t guess — start without it and measure your own usage.
