There are two ways to end up with more than one server, and they are not the same purchase. Choosing the wrong one is not expensive to fix, but it is much easier to get right the first time.
The two routes
| A second service | A splitter slot | |
|---|---|---|
| Memory | Its own, in addition to the first | A share of what the first plan already has |
| Cost | A second plan | Far less |
| Good for | A second real server for a different group | A proxy, a lobby, a test instance |
| Independent | Completely — separate billing, separate everything | Same plan, same pool of memory |
Which one you want
If you want a proxy in front of your survival server, or a small lobby, or somewhere to test an upgrade — split. Those need very little memory and taking a slice from what you already pay for is the whole point of the feature.
If you want a second full server for a different community, running its own modpack with its own players — buy a second service. Splitting an 8 GB plan into two 4 GB servers gives you two 4 GB servers, and if 8 GB was already what the first one needed, you now have two that are too small.
Managing several from one account
- Name them clearly in the panel
«Survival», «Lobby», «Test» rather than three default names. You will be looking at this list at midnight sooner or later.
- Give each one its own schedules
A restart schedule does not carry across services. A new server with no backup schedule is a new server with no backups.
- Check invoices per service
Several services means several renewal dates unless you align them. That is worth knowing before one of them surprises you.
- Add subusers per service, not globally
Access is granted per server. Someone who helps with the lobby does not automatically need the survival world, and this is the moment to decide that rather than later.
The plan's memory is divided, not multiplied. If your main server is already using most of what it has, creating a second instance takes that memory away from it and both will struggle. Check your peak usage before splitting, not after.
Somewhere to try a version upgrade, a new plugin, or a restore before it touches the live world. It costs a small slice of memory and it converts every risky change into a rehearsed one.