SCUM Server Hosting

Build a persistent survival community with substantial memory and storage headroom for SCUM’s dedicated server and world data.

You rent a dedicated game-server instance with the plan resources shown above and manage it in the Konnect Hosting panel. This is a game-server service, rather than a whole physical machine.

The plan cards show current monthly prices and resource allowances from Product Catalog. Your billing cycle and any selected upgrades determine the total at checkout. Prices are based on resources rather than a per-player hosting charge.

Our starting configuration has 16 GB RAM and 150 GB NVMe storage, including headroom beyond a minimal installation. Choose more RAM for larger worlds, more active players or heavier custom content. Installation size and runtime demand change with updates, maps and mods; monitor actual usage rather than treating the suggested player count as a benchmark.

We do not map the plan’s suggested player count into a hosting slot cap. Player figures are estimates. The game’s own server settings and technical limits still apply, and usable capacity depends on your world, content and purchased resources.

Yes. After confirmed payment, automation selects this game’s installed egg, applies your purchased resources and assigns the reviewed port bundle on an enabled Dallas node. Checkout checks current capacity before payment, and provisioning checks it again. Downloads and first startup take time; your service page shows progress.

This configuration does not ask you for a personal Steam username or password at checkout. Players still need a compatible copy of the game and any required client mods.

Use the game address and assigned primary port on your service page or in the game panel. Follow SCUM’s supported server browser or direct-connect flow. Keep the assigned values: secondary query, synchronization or administration ports serve different purposes.

The installed egg manages SCUM/Saved/Config/WindowsServer/ServerSettings.ini. Stop the server and back up your configuration before editing. Values managed by Startup settings may be rewritten when the server starts.

The upstream SCUM egg reference describes the installer and its variables. Back up saves before changing editions, branches or server packages.

Use the browser file manager or SFTP to upload your own compatible files. Stop the server and take a backup first. Use content supported by this server implementation and game version; a hosting panel does not make incompatible mods or saves work. Contact support before changing implementations on an existing world.

Stop the server or use its supported save command before taking a backup. Preserve worlds, configuration and any custom content before updates, migrations or reinstalls. The included 10 GB backup allowance provides one backup file; higher allowances provide two files. Backup storage is separate from server disk space. Backups include server files by default; no unverified exclusions are applied.

Dallas, Texas is available for new orders when an enabled node has capacity for your configuration. Helsinki, Finland is coming soon and cannot be selected. Network latency depends on your players’ locations and routes.

Choose an available higher plan through your service’s plan-change options or contact support. Plan resources are totals: moving from 4 GB to an 8 GB plan gives 8 GB, rather than adding the old and new plans. Availability and any billing adjustment are shown before you confirm.