Rust server hosting
Rust server hosting with CFTools Architect runs the dedicated server on a VPS or machine you control. The usual Rust job is a seed, a world size, a wipe calendar, and a backup taken before Facepunch ships a forced wipe. Architect installs the server, applies updates, edits configuration, restarts, recovers from crashes, and automates wipe cycles. One agent is one machine and can run more than one Rust server on it. The Rust RCon admin tool in Cloud is still planned and is not part of hosting.
Runs on a Windows or Linux machine you control.
Hosting highlights
A Rust box you control
Install the agent on the Windows or Linux host that should run the map. Players connect to that machine. Architect does not sell Rust slots or shared game hosting.
Wipe cycles and force wipes
Schedule wipe automation around your own map cycle, and be ready when Facepunch forces a monthly wipe. The map seed and world size stay in the server config Architect manages.
Updates without a midnight SSH
Rust patches land on a schedule communities do not pick. Architect can update the dedicated server and bring it back so Thursday night is a restart, not a manual install.
Hostname, seed, and world size
Edit the Rust server configuration from Manager. Hostname, seed, world size, and the rest of the startup settings stay with the server record instead of a script only one person remembers.
Save backups before a wipe
Back up the Rust save before a map wipe or a risky update. If the new branch fails, the previous save is still on the machine Architect is managing.
Metrics while the server fills
Hardware metrics and game-server metrics show whether the box is the reason players rubber-band after a wipe. Crash recovery restarts Rust if the process dies.
How to self-host Rust
Provide a machine with enough RAM for your player cap and map size. Install Architect Agent, deploy Rust, set the wipe plan, and open the game port. Webhooks can tell Discord that the server came back after an update. RBAC lets a second person restart the server without full access to the host.
Rust caveats
Architect mod management is not part of the Rust feature set. Communities that add a plugin loader keep that loader beside the dedicated server Architect installs. Cloud RCon for Rust is coming soon and cannot be connected yet. Queue priority and BattlEye admin flows from DayZ do not apply.
Wipes are the hosting job
A Rust host is judged on wipe day. Automatic wipes, backups, and a clean update path are the Architect features that match that week. Player bans and live chat tools wait on the planned Rust RCon admin tool.
What you need to host Rust
You bring a computer that can hold the map. Architect automates the dedicated server on it.
- A Windows or Linux VPS or dedicated machine
- RAM and disk sized for the map and player count
- Architect Agent installed on that machine
- The Rust game port reachable by players
- A backup before the next forced wipe
CFTools Architect features for Rust
- Automated server deployment
- Automatic updates
- Configuration management
- Automatic restarts
- Backup automation
- Detect and recover from crashes
- Automate server wipe cycles
- WebHooks for every server state and event
- RBAC - Grant others easily limited or full access
- All servers easily visible on one unified dashboard
- Hardware metrics
- Game server metrics