← Games

Survival · Staging · client validation pending

Host a Rust Server in Staging (Staging)

Staging · client validation pending Staging: awaiting manual game-client validation. Player connections are not yet verified. Evaluate this server before inviting players.

Run your own Rust server and manage worlds, backups, and player access from a browser.

Rust artwork

Hardware and runtime

What you’ll need

Check my hardware →
CPU
4+ cores
Memory
12 GiB minimum
Player traffic
UDP
Backup coverage
1 saved data location

Allow more capacity for larger worlds, more players, or mods.

Setup and runtime

Start with 4 CPU cores and 12 GiB memory, plus fast storage for the game, world, logs, and backups. Large maps and player counts need more memory. Facepunch's server guide recommends 12 GB free RAM and an SSD or NVMe drive.

    Launching the server

    The startup log should reach Server startup complete. A running container alone does not confirm players can join. Rust+ companion access is unavailable in this staging setup.

    • Open the launch menu and choose Rust from Staging.
    • Select a host with enough available CPU, memory, and disk.
    • Set the server name, player limit, world size, and seed.
    • Keep Save identity unchanged after first launch; it selects the world directory.
    • Leave the private management credential blank on a new deployment to generate a unique value.
    • Launch and watch the logs. First boot downloads the game and generates the world; allow several minutes.
    How players connect

    For later client evaluation, use the player address and game port shown on the Swarm Server page. In Rust, press F1 and enter connect <player-address>:<game-port>. The query port is separate from the player port. When a relay is active, use its displayed public endpoint. Server-browser listing and Rust+ are separate from this direct join check.

      Technical overview

      Rust runs a Linux dedicated server with separate UDP game and query ports. The vanilla runtime stores server files and worlds in persistent storage. Read Staging games for the evaluation limits.

      Read the full Rust guide →

      Game management tools

      Manage your Rust server

      Available tools depend on the game, server status, and your permissions. The game guide explains any setup needed for Server Actions.

      Use the settings, files, backups, logs, and server controls available for this game. The complete guide documents any game-specific action prerequisites.

      Mods & Content status

      Mods and custom content

      Oxide/uMod and Carbon are executable plugin frameworks, not trusted artifact providers. This vanilla runtime does not install or manage either framework or their plugins.

      This is a vanilla runtime. Oxide/uMod and Carbon are executable plugin frameworks; Swarm Hosts does not install, verify, update, or roll back them or their plugins. See Facepunch's modded-server listing guidance before evaluating a modified server.

      Know before launch

      Before you launch

      • Awaiting manual game-client validation. Fresh image startup, five-minute server stability, and saved configuration and world files surviving restart were tested locally on 2026-10-09. Manual client connection and public network validation remain pending.
      • Host on Windows 10/11 or Linux with Docker Desktop in Linux-container mode on Windows, or Docker Engine or rootful Podman on Linux.
      • Managed shared relay when the game, host, and current relay path support it.

      Windows 10/11 + Linux

      Ready to host Rust?

      Connect the Windows or Linux computer you already own, then follow the game-specific launch path.