← Games

Survival · Staging · client validation pending

Host a Core Keeper 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 Core Keeper server and manage worlds, backups, and player access from a browser.

Shared capacity may require a wait. After 48 hours of play, you have 48 more hours to move your world before deletion.

Core Keeper artwork

Hardware and runtime

What you’ll need

Check my hardware →
CPU
2+ cores
Memory
2 GiB minimum
Player traffic
UDP
Backup coverage
2 saved data locations

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

Setup and runtime

Start with 2 CPU cores and 2 GiB memory for evaluation. Leave disk space for the game, worlds, logs, and backups. More players or a large explored world can need additional resources.

    Launching the server

    Check the reported game version before attempting a client join. A running server process does not confirm the Game ID or network route works for players.

    • Choose Core Keeper from Staging and select a suitable host.
    • Keep the offered launch defaults for the first test.
    • Launch and wait for game installation and server initialization in the logs.
    • Record the server's Game ID if the installed runtime uses Steam networking.
    • Stop the server before editing generated world or configuration files.
    How players connect

    For later client evaluation, use Core Keeper's Join Game flow with the server's Game ID when Steam networking is enabled. Do not substitute an IP and port for a Game ID. If a separately configured runtime uses direct networking, follow its matching client instructions and the displayed public UDP mapping. Game ID joining is specific to Steam clients. The publisher also documents direct PC client connections using IP, port, and password in the server's shipped README.txt. See the official dedicated-server announcement. Both modes still need manual validation in this staging entry.

      Technical overview

      The dedicated-server runtime keeps its world and configuration in persistent storage. See Staging games before planning a shared world.

      Read the full Core Keeper guide →

      Game management tools

      Manage your Core Keeper 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

      Track mods in one place and apply them manually through the game-specific workflow.

      The content page records desired mod identifiers only. It does not install, verify, check client compatibility, or roll back mods. Evaluate vanilla first; apply any compatible content manually after backing up the world.

      Know before launch

      Before you launch

      • Awaiting manual game-client validation. Fresh image startup, five-minute server stability, and configuration persistence on restart were tested locally on 2026-10-09. Client joining, player progression, 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 Core Keeper?

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