How to Choose a Minecraft Server Host

How to choose a Minecraft server host without overpaying or lagging: look at single-core CPU clock speed, real (not oversold) memory, an NVMe disk and DDoS protection — these four points decide whether TPS holds at 20 or your server starts freezing under load. Everything else (panel, backups, support) matters, but comes second. Below we break down each criterion with the "why" behind it and give you a checklist of red flags.

Why cheap hosting often turns out expensive

The "I'll grab the cheapest plan and move later if I have to" logic usually ends in lost evenings. The server stutters, players drift away, you're stuck in support tickets, and in the end you switch hosts anyway — only now with frayed nerves and a shrunken player count. If you're still at the build stage, check out our big guide on how to create a Minecraft server — this article is about the foundation you stand it up on.

Not sure where to get a server in the first place? We weighed the options in our Minecraft hosting comparison, and broke down free services like Aternos in a separate guide on free hosting and its alternatives.

Good hosting isn't about a pretty landing page or the number of gigabytes in the plan's name. It's about hardware that fits the Minecraft engine specifically. And Minecraft's engine is peculiar, so you have to choose for it deliberately.

CPU: single-core clock speed decides everything

The key technical quirk of Minecraft: the main game loop — the world tick — runs on one thread. The server has to finish calculating the whole world (mobs, redstone, plant growth, physics) 20 times a second — that's the coveted 20 TPS. The time for a single tick is called MSPT, and it has to fit within 50 ms. Miss that, and TPS drops and the world starts "lagging" for everyone.

What that means in practice: you want a processor with a high single-core clock speed. Modern AMD Ryzen 9 chips boosting past 5.0 GHz are practically the gold standard for Minecraft. The more plugins, mobs and complex redstone mechanics you run, the harder you lean on that one core. If a host won't say what CPU its servers run on, that alone is a reason to be wary.

Multiple cores do still help, but indirectly: network threads, chunk generation (on Paper/Purpur), background tasks and JVM garbage collection get offloaded to separate cores. So a good configuration is one strong core plus some headroom for the supporting work. But clock speed comes first.

How do you check this with a host before buying? Open the panel console and run the tick-profiling command — on Paper that's /spark tps and /spark profiler. If MSPT stays comfortably under 50 ms at a normal player count, the core is keeping up. If it creeps toward 50 and above under trivial load, the CPU is weak, and no amount of RAM will fix the lag. On virtual plans without a dedicated core, neighbors on the same physical server can "eat" your clock cycles, so wording about a dedicated CPU resource is just as important as it is for memory.

RAM: real memory vs. overselling

With memory there are two questions: how much and what kind. Let's start with "what kind", because it matters more.

What overselling is and why it's dangerous

Overselling is when a host sells more RAM in total than is physically in the server, betting that not every customer will max out their limit at the same time. While load is low, everything works. But at prime time, when many servers peak at once, there isn't enough memory to go around, and the freezes, lag spikes and crashes begin. And the problem isn't even your server — you just happened to be the neighbor who didn't get the resource.

Phrasing like "unlimited RAM" or "up to 16 GB" is almost always marketing on top of overselling. Real, dedicated DDR5 with no overselling means the gigabytes you're promised are yours and won't vanish at peak hour.

How much memory to get

In short: vanilla or Paper for 10-20 people live on 4-6 GB, mid-size modpacks ask for 8-12 GB, and heavy CurseForge and FTB packs want 16 GB and up. But "throwing RAM at it" doesn't cure lag when the bottleneck is the CPU, and it doesn't help if the memory is oversold. We worked out the exact numbers for your case in a separate piece — how much RAM a Minecraft server needs. And remember: a giant heap without proper JVM flags causes long garbage-collection pauses, so "more memory" isn't always "better".

Disk: why NVMe, not HDD

Minecraft isn't only about the CPU. The server constantly reads and writes world chunks to disk: players explore new territory, the world saves, and the auto-backup dumps gigabytes. On a regular HDD this creates a disk queue, and during a save or world generation TPS dips — that's the classic "lag when a new player joins".

The gap between an HDD and NVMe Gen4 isn't percentages — it's tens of times. For modpacks with hundreds of mods and heavy world generation, a fast disk is no less critical than the CPU: a heavy pack starts in a minute instead of five, and a large world saves with no noticeable pause. If the disk is slow even with a perfect processor, you'll find the breakdown of causes in our article on why a server lags and how to fix it.

Location and ping

The hardware can be top-tier, but if the data center is on the other side of the world, players will get high ping and that "rubber-banding" feel. Choose a location close to your core audience. For Russian-speaking and European players, Moscow, Frankfurt, Amsterdam and Helsinki are convenient — they give low ping across the CIS and the EU at the same time. See the list of points and a latency guide on the locations page.

DDoS protection — not an option, but a baseline

Minecraft servers are attacked constantly: one disgruntled player is enough to order a cheap stress test and knock the server offline. Without traffic filtering you're helpless — the server is simply unreachable while the attack runs. That's why L3-L7 DDoS protection (from volumetric attacks up to the application layer) should be included in the plan by default. If it's offered as a paid upgrade, or not mentioned at all, that's a serious minus.

Software and service: panel, backups, support

Hardware is the foundation, but you'll be managing the server every day, and convenient tools save you hours.

• Control panel. Pterodactyl is effectively the industry standard: a real-time console, one-click restart, file management, team permissions. It's far more convenient than bare SSH.
• One-click core and modpack installs. Good hosting lets you install Vanilla, Paper, Purpur, Spigot, Forge, Fabric or NeoForge and deploy a CurseForge/FTB pack without manual fuss. If you're still picking a base, read our comparison of Paper, Purpur and Vanilla and our breakdown of Forge vs. Fabric. For heavy packs, our guide to choosing a host for modpacks is especially handy.
• SFTP and MySQL. SFTP is for quickly uploading mods and configs; MySQL is for plugins that use a database (economy, regions, statistics). These should be there out of the box.
• Automatic backups. Sooner or later a buggy plugin or a griefer crew will wreck the world. Auto-backups and a fast rollback save the project — how to set this up properly is covered in our guide on server backups and rollback.
• 24/7 support. Servers don't crash on a schedule. Live support on Telegram or Discord that answers in minutes, not days, is the thing you can't see in the price but feel the very first time something breaks.
• Migration from an old host. If you're not starting from scratch, help moving your world, plugins and configs matters — so you don't reassemble everything by hand. Details are on the migration page.

The host-picking checklist

Before you pay, run through the list — if a host covers most of these points, you can trust it.

1. CPU — a modern Ryzen 9 (or equivalent) with a high single-core clock speed, 5+ GHz.
2. RAM — genuinely dedicated DDR5, an exact amount, no "up to X" or "unlimited" wording.
3. Disk — NVMe (ideally Gen4), not an HDD.
4. L3-L7 DDoS protection included in the plan by default.
5. A location near your audience and reasonable ping.
6. Pterodactyl panel, one-click core/modpack installs, SFTP and MySQL.
7. Automatic backups and an easy rollback.
8. 24/7 support that answers fast and to the point.
9. Free or easy migration from an old host.
10. Transparent plans — you can compare them and understand what you're paying for.

Red flags — when to walk on by

• "Unlimited RAM" and "up to X GB". Marketing on top of overselling. Real memory isn't sold that way.
• HDD only, or the disk isn't mentioned at all. For Minecraft, especially modded, that's guaranteed slowdowns.
• Silence about the CPU. If they won't say what processor their servers run on, there's probably nothing to brag about.
• DDoS protection only for an extra fee, or absent. One day of attack and the "cheaper" plan no longer looks like a bargain.
• Support that answers in days, or only via tickets with no live chat.
• A price well below market for "lots of gigabytes". There's no magic — they're cutting corners on the hardware you're paying for.

Room to grow and moving to a proxy

Think about the future separately. If the project takes off, you'll need either a beefier plan or a network of several servers behind one address — a lobby, minigames, survival. That's done through a BungeeCord or Velocity proxy, and the host has to support them. It's convenient when a plan upgrade happens without a manual migration and you can stand up the proxy in the same place. So look not only at the starter plan, but at whether there's room to grow within the same host.

How Elysium is built around these criteria

We built Elysium to exactly this checklist, because we've run servers ourselves and know where it usually hurts.

• CPU: AMD Ryzen 9 boosting past 5.0 GHz — a strong single core for Minecraft's main tick.
• RAM: real DDR5 with no overselling — the gigabytes you're promised are yours at any peak hour.
• Disk: NVMe Gen4 with reads around 7 GB/s — chunks and world saves don't drag TPS down.
• Protection: L3-L7 DDoS filtering on by default, plus free automatic backups.
• Software: Pterodactyl panel, core installs (Vanilla, Paper, Purpur, Spigot, Forge, Fabric, NeoForge), BungeeCord and Velocity proxies, one-click CurseForge/FTB modpacks, SFTP and MySQL.
• Locations: Moscow, Frankfurt, Amsterdam, Helsinki — low ping across the CIS and the EU.
• Service: 24/7 support on Telegram and Discord, free migration on the Vector plan and above with 48 hours of support after the move.

The plan lineup is organized by memory size — from Common (4 GB) and Pulse (6 GB) for vanilla and light packs up to Nexus (8 GB), Apex (12 GB), Titan (16 GB) and the top-tier Vector / Eclipse (20-32 GB) for heavy modpacks. Prices start from €4.99/mo and switch between ₽/€/$ on the site. The easiest way to compare everything on one page is on the pricing page.

Choosing a host is first and foremost a choice of hardware and service for the quirks of the Minecraft engine, not a race for numbers in a plan's name. Run through the checklist, watch for the red flags — and your server will hold a steady 20 TPS while you work on your project instead of fighting lag.