Choose resources for your Rust server
Map size, population, entities and plugins: what to consider before selecting a Rust plan.
Size your project, not just its player count
A small community with a large map and many constructions can still need significant resources. Describe your map size, planned plugins and expected population before comparing plans.
The PlaceHeberg Rust catalogue starts at 12 GB of RAM. This is our first catalogue tier, not a universal operating guarantee. Player estimates assume the conditions stated on each plan page.
Compare RAM, CPU and storage
RAM provides headroom for the world and its entities. CPU resources must handle simulation, while storage holds files and backups. Choose a balanced configuration and watch actual usage.
Perf uses the machine pool assigned to that profile while retaining the plan resource quantities. It does not turn player estimates into guaranteed capacity.
Prepare access and testing
Use the address and port of the primary allocation shown in your service page. Different Rust features can use several ports: configure each allocation according to the game documentation.
Run a representative play session and watch memory and CPU usage during busy periods. Plan backups and controlled restarts rather than expecting thirty uninterrupted days.