Free server tool / Network planning

One network. A budget for every world.

Build a memory plan for your proxy, lobby and game servers. Keep per-instance targets visible as your network grows.

Multiple server groupsVelocity proxy budgetDownload your plan

01 / Your network

Give every server its own budget.

Add your lobby and game servers. Player counts and memory targets apply to each instance in a group.

Peak players across the networkProxy instancesBackend headroom (%)Host / services reserve (GiB)Allowance for the OS and other services on a shared host. Adjust it for your actual deployment.

Server group 1

Group name

Software

InstancesPeak players per instanceView distance (chunks)Plugins per instance

Server group 2

Group name

Software

InstancesPeak players per instanceView distance (chunks)Plugins per instance

Player peaks can move

Plan for a busy lobby during restarts and for players concentrating on one game. A total network count does not describe the busiest backend.

Room around the proxy heap

Proxy sizing uses Velocity’s published starting rule, rounded up to half a GiB, with twice that amount for the container. Each proxy is budgeted to handle the full network peak.

Memory is one constraint

The combined number is a planning total. Check CPU contention, networking and storage before placing all instances on a shared host.

Proxy assumptions: Velocity tuning guide. Backend estimates use the same model as our Minecraft RAM calculator.

A little help before you launch

Plan the whole network.

What the combined budget includes, and what still needs testing.

Let’s talk it through.

Have a question of your own? Our team is here to help.

Ask our team (opens in a new tab)Or explore the guides

5 questions

01Are players counted per instance or across the network?

Backend player counts apply to each instance in a group. The separate network peak sizes each proxy. Players are not added to backend memory a second time just because they pass through a proxy.

02How is the proxy allowance calculated?

The tool uses Velocity’s published starting rule: roughly 1 GiB plus 0.5 GiB per 500 players, rounded up to a half GiB. The container allowance is twice the heap target. Every proxy is sized for the full network peak to allow for failover; test your plugins and actual load.

03Does the combined target fit on one dedicated server?

It is a memory planning total, not a placement guarantee. Tick threads, background workers, disks and networking can become bottlenecks. Check concurrent CPU demand before consolidating backends on one host.

04What does the price include?

Only the selected Minecraft backend plans, multiplied by their instance counts, in your selected display currency. Proxy hosting and the host/services reserve are not included. If any backend exceeds the listed tiers, a custom sizing message replaces the price subtotal.

05Can I copy these targets into Java startup flags?

No. Targets and plan limits are process budgets, not suggested -Xmx values. Keep memory for JVM overhead and other processes, and verify actual usage before changing allocation.

Still have a question? Talk to our team

More free server tools