Plans

A plan is what you sell to a customer: the server's resources, pinned settings (e.g. the slot count) and limits on mods, backups, schedules and databases. Each plan belongs to one game. Plans are created under Plans.

A plan is optional. Without one a server gets the default resources from the game's settings, or, if none are set there, 2 GB of memory, 1 CPU core and no disk quota.

Create a plan

Plans → New plan. The form has several steps.

1. Basics

Name — customers see it when creating a server, e.g. "Minecraft · 20 slots".
Game — can't be changed on an existing plan.
Description — optional.
Label — shared by a group of plans, e.g. premium. Database host rules can refer to the label instead of each plan. See Databases.

2. Resources

Container limits: memory, CPU and disk quota. An empty field means the default from the game's settings.

3. Pinned settings

Game settings from the catalog. A filled-in value is pinned by the plan and the customer can't change it — this is how the slot count is set, for example. An empty field stays as in the game's settings.

4. Ports and IP

The plan's port ranges replace the node's, location's and default range. There can be several; they're tried in order.
IP pools — the plan's servers are placed only on node addresses from these pools, e.g. dedicated IPs (premium). Pools are set on addresses on the node's page, see Managing nodes. Empty — the shared pool.
Prefer standard game ports — try the game's own ports (27015, 25565…) on every IP of the node first, and only then the range.

5–9. Limits

An empty field means no limit or the panel-wide setting. Limits don't apply to admins.

Maps and mods — Disallow maps and mods; Max installed per server, dependencies included; Own uploads, MB — total per owner, 0 turns own uploads off (the panel default is 1024 MB); Maximum per file, MB (default 200 MB); External sources — Steam Workshop, Modrinth, Thunderstore, uMod, GameBanana, Factorio Mod Portal. The panel's catalog and own uploads are always allowed. See Maps and mods.
Backups — Disallow backups; Max kept per server; Total size, MB per server. Failed backups don't count. Existing backups can be downloaded, restored and deleted even with backups disallowed.
Schedules — Disallow schedules; Max per server (up to 20); Min interval, min — how often a schedule may fire (once every 5 minutes by default).
Databases — Disallow databases; Max per server.
SFTP — Disable SFTP. The panel's file manager works either way.

What applies at once and what by hand

A server records the resources and pinned settings when it's created. So:

resources, pinned settings, ports and IP from an edited plan apply only to new servers. To apply them to an existing server, open its Settings tab and click Reapply in the Plan row. The container is recreated and the server's files are kept. Ports already assigned don't change;
limits (maps and mods, backups, schedules, databases, SFTP) apply to all of the plan's servers at once. What's already installed, stored or created stays; the new limits are checked on the next action.

Change a server's plan

Server's Settings tab → Plan row:

pick another plan of the same game and confirm — the resources and pinned settings are replaced and the container is recreated with the data kept;
No plan — unlink the server from its plan. The current resources and settings stay as they are.

A billing system does the same on its own: the WHMCS module moves the server to the new product's plan on Upgrade/Downgrade, see WHMCS.

Delete a plan

Actions → Delete… While any server uses the plan, the panel refuses — move those servers to another plan or unlink them first.