Rust Server Hosting

Rust lives and dies by wipe day. The first hour after a forced wipe is when a hundred players connect together, every monument populates, and thin hardware turns into rubber-banding. Our nodes use AMD Ryzen 9 processors with DDR5 ECC memory, which is what a mostly single-threaded server binary actually wants. Plans include 3 cores from 2 to 6 GB, 4 cores at 8 GB and 5 cores from 12 GB upward.

The task scheduler covers the routine work: a restart paired with a map wipe on the first Thursday, blueprint wipes on whatever cadence your community voted for, and quiet nightly restarts in between. Automatic daily backups hold ten rolling slots of the previous map, so a mistimed wipe is recoverable.

Modded Rust means Oxide, now maintained as uMod. Use the panel installer or drop .cs files straight into oxide/plugins over SFTP and the server hot-loads them without a restart. Generated configs appear under oxide/config, where you can edit kit contents, gather rates and permission groups in the file manager. Handing out permissions with oxide.grant from the live console takes seconds.

Ports and allocations are unmetered with ten assigned by default, so a RustEdit custom map download, the Rust+ companion app port and a plugin web interface can all run beside the server without buying anything extra. Unmetered NVMe storage means a large plugin data folder is never a billing question.

Worldsize drives memory far more than population does, so decide on your map before your plan. Set server.seed and server.worldsize in the startup parameters, then regenerate whenever you want a new layout. The live console doubles as RCON, so ownerid, moderatorid and server.save all work from the browser, and SFTP gives you the raw save file if you want to archive a legendary wipe.