Before you start
Prepare the edition, version, server software, plugin or mod list and world size. Describe exploration, generation, machines, entities and accompanying services. Record measurements if you already run a server. Establish renewal budget, billing period and how to recover files when changing providers.
Choose Java or Bedrock before sizing
Java and Bedrock are distinct products with different software and protocols. Check your community’s devices and game versions. Crossplay requires a compatible gateway and suitable configuration; it is not an automatic property of every Minecraft plan.
For Java, choose software to match extensions: Paper or another plugin server, Fabric, Forge or NeoForge according to the modpack. Plugins and mods are not interchangeable. Check dependencies and published versions before buying resources for a combination that cannot start.
Match CPU and memory to server work
Simulation, extensions and terrain generation consume CPU time. A vCPU count does not necessarily reserve that many physical cores. Ask for the actual processor model or family, sharing rules and allocated resources. An advertised frequency is not a permanent clock-speed guarantee for each instance.
Memory needs depend on the engine, mods, entities and world. Leave room for the system and maintenance. Start with suitable view and simulation distances, then measure. RAM does not guarantee a fixed player count, and additional memory does not fix a blocking plugin.
Include worlds, updates and backups
Storage must cover installations, worlds, extensions, logs and retained copies. Explored worlds grow, and restores can need extra space. SSD capacity alone does not describe disk performance; establish conditions if your workload depends heavily on writes.
Check how backups are created, downloaded and restored, including quotas and retention. A copy stored only on the main node does not cover losing that node. Test restoration on a copy before major migrations or world-version changes.
Verify tools that are actually available
Look for files, logs, configuration and versions suited to your engine. For extension catalogues, check sources, images, dependencies and incompatibility detection. An install button does not establish that a plugin for another version will work.
Ask how updates handle stopping, backup, confirmation and rollback. Worlds, scheduled tasks and shared access need clear limits and permissions. Restarting should not be repeatable without controls while another operation is active.
Define protection and connection ports
Establish protected addresses and protocols, plus game-appropriate handling. Java and Bedrock use different primary transports. HTTP web protection does not demonstrate coverage of the Minecraft protocol. Aggregate mitigation capacity is not bandwidth reserved for one server.
Use assigned ports and test from player networks. Do not confuse the provider website being online with game availability. Where a domain or proxy is involved, check that path and any exposed origin as well.
Compare total cost and test the project
Compare the amount payable over the period, renewals, limits and required options. A starting price may not represent the complete project. Verify actual availability before arranging migration; a catalogue page does not establish immediate node capacity.
When your plan and account qualify for a trial, test your engine, world and extensions under its actual conditions. Measure representative activity and keep an independent backup. For Paper, profiling during a slowdown is more useful than an abstract player estimate.
For your situation
| Situation | Next check |
|---|---|
| Java with plugins | Check software, versions and published dependencies. Measure simulation and plugin work instead of choosing solely by player count. |
| Java with a modpack | Confirm the loader, exact version, startup memory and file space. Test compatibility on a copy. |
| Bedrock or crossplay | Check clients, UDP and assigned ports. For crossplay, confirm the gateway is actually configured. |
Official sources
These documents describe the relevant protocols and software. Your service terms and configuration still need to be checked.