Rust server hosting
Wipe cycles, plugins and a full roster. Sized for a community server rather than a duo.
What you get
- Oxide and Carbon plugin frameworks
- Scheduled map wipes and seed control
- Console access for live moderation
- A free 10-slot Mumble voice server to go with it (one per account)
No ports, no router settings
The server runs on our machines, not yours. It gets a port of its own on our address, so there is nothing to forward on your router, nothing to leave open overnight, and your home connection is never handed out to players. Your upload speed stops being the thing that decides how many people can join.
Never run a server before? Read the beginner guide to see every step, from joining to mods.
Rust server sizes and prices
Every size includes the same features. We suggest 8–12 GB for Rust; you can move up or down later.
| Plan | Memory | Per month |
|---|---|---|
| Scout | 2 GB | $5 |
| Squad | 4 GB | $10 |
| WarbandRecommended | 8 GB | $18 |
| Legion | 12 GB | $26 |
| Empire | 16 GB | $34 |
About our Rust servers
A Rust server needs memory for its map and players and a schedule for its wipes. Ours installs and starts by itself, generates your map on the first start, and lets you set the server name, description, map size, seed and player limit in the panel.
Choose Oxide or Carbon in the Startup tab for plugins, then upload them yourself. Set wipes to run weekly, every two weeks or monthly at the day and hour you pick, and the server clears the map and starts fresh on its own. Moderate live from the console.
Rust server questions
- How do I schedule wipes on my Rust server?
- In the Startup tab, set the wipe schedule to weekly, every two weeks or monthly, and choose the day and hour. The server wipes and restarts on a fresh map by itself.
- How do I add Oxide or Carbon plugins?
- Set Modding Framework in the Startup tab to oxide or carbon and restart, then upload plugin .cs files to the plugins folder.
- How do I make myself the owner?
- In the panel console, type ownerid followed by your SteamID64 and name, then server.writecfg, and reconnect.

