Renting is the better default for most small Core Keeper groups because the world remains online when the owner’s computer is off, while the provider handles the always-on machine, data-center connection and much of the administration. Self-hosting is the better value when someone already has a suitable computer that can stay powered on, understands basic server maintenance and wants to avoid a recurring bill. Core Keeper’s dedicated-server application is free; you are paying a host for convenience, availability, support and infrastructure rather than for the game server software itself.
The right choice depends on six practical questions: whether the world must be reachable while the owner is away, what hardware and internet connection you already have, how much technical work your group accepts, how much control you want over files and launch arguments, where players are located and whether a predictable monthly cost is preferable to using existing equipment.
What is the better choice for a Core Keeper server?
Choose self-hosting if you already own an always-on desktop, NAS or mini PC, someone will take responsibility for updates and backups, and your group values direct control of the world files. Choose renting if players need reliable access while the owner is offline, the home connection is uncertain, or nobody wants to monitor a server and recover it after crashes.
| Decision factor | Self-hosting | Renting |
|---|---|---|
| Availability | Online only while your chosen machine and connection are running | Designed to remain online in a provider data center |
| Software cost | Dedicated-server application is free | Dedicated-server application is free; you pay the host’s recurring fee |
| Hardware | You supply and maintain it | Included in the hosting service |
| Networking | You choose relay or direct IP/port settings and manage your home network | Provider supplies the server connection; exact networking controls depend on its panel |
| Backups and recovery | Your responsibility | Check what the provider includes; keep your own copy when possible |
| Control | Full access to files, launch arguments and operating system | Full file access is advertised by the checked example, but operating-system access and controls vary |
| Monthly cost | No hosting bill, but electricity and hardware have an opportunity cost | Published plans in the checked US example cost US$5.99–US$15.99 per month for 1–8 players |
Pugstorm’s dedicated-server announcement describes worlds that can be accessed “at any time without requiring a host to be in the game.” That is the central advantage of both a correctly configured self-hosted dedicated server and a rented one; the difference is who supplies and maintains the always-on computer.
What does self-hosting a Core Keeper server involve?
Self-hosting means installing the official dedicated-server application on a computer you control, keeping its process running and protecting the world data. The software is free, but the machine, electricity, internet connection and operator time are not.
Hardware and connection requirements
IONOS lists an indicative planning baseline of two CPU cores running at 2.4 GHz or faster, 2 GB of RAM for one to four players, at least 4 GB for larger files or groups, and 10–20 GB of storage. These are third-party planning figures from 2023, not a formal Pugstorm specification, so leave headroom for the operating system, updates and other services.
- The computer must stay powered on whenever players may want to enter the world.
- A wired connection is generally easier to keep stable than an unreliable wireless link, although the available data does not establish a required connection type.
- Do not treat a gaming desktop that is frequently shut down as an always-available server unless your group accepts that schedule.
- If the machine also runs file sharing, media services or other games, reserve enough memory and CPU capacity for all of them.
Installing the official server
Pugstorm distributes the dedicated-server application through the Steam Library’s Tools section. The community setup guide also documents SteamCMD installation using application ID 1963720, which is useful for a headless machine or an installation that should not depend on the normal Steam client.
- On a computer that will remain available, install the dedicated-server tool from Steam’s Library > Tools section, or install it with SteamCMD using app ID 1963720.
- Start the server from Windows PowerShell as described by the setup guide. The PowerShell process must remain running; closing that window stops the server.
- Allow the first startup to complete and create its data files. The guide notes that the dedicated-server
worldsfolder may not appear until a player joins and the first save is written. - Locate the world and configuration folders identified by the guide and record their locations before making changes.
- Share the game connection details with your players only after confirming that the intended world loads.
Relay versus direct connections
The current launch-argument reference supports two connection approaches. A Game ID relay path avoids opening a port on your home router. A direct IP-and-port path can be used when you want direct connections; setting a port enables that mode and exposes controls related to direct connections and cross-play.
For a small group behind restrictive or changing home networks, start with the relay path if it meets your latency and cross-play needs. Consider direct IP/port only when you understand router configuration, firewall rules and the security implications of exposing a service. The available reference confirms the two paths, but it does not prescribe one universally superior setting.
Backups, updates and monitoring
Backups are the self-hosting task most likely to be postponed until after a problem. The setup guide specifically warns users to back up before sharing a game code publicly. Keep at least one copy of the world and configuration data outside the live server directory, and make a fresh backup before updates or major configuration changes.
- Stop or safely pause the server before copying live world data when possible.
- Use dated backup folders so you can identify the last known-good save.
- Test that a backup can be opened or restored rather than assuming that a copied file is usable.
- Keep a written note of launch arguments, world identity and any firewall or router changes.
- Use the optional auto-restart script documented by the community guide if you are comfortable running scripts, and pair it with a way to notice repeated crashes.
Updates should be deliberate. Install the new server version, confirm that the world still loads, and only then invite the group back. If the server crashes repeatedly after an update, stop restarting it blindly; restore the last known-good backup and check the changed version or launch arguments.
How much does renting a Core Keeper server cost?
A checked US hosting page lists player-limited plans from US$5.99 to US$15.99 per month. These prices were displayed on October 27, 2026, and are one provider’s terms rather than a market-wide guarantee.
| Published player tier | Monthly price | Published details | Approximate annual cost at the same monthly rate |
|---|---|---|---|
| 1 player | US$5.99 | Uncapped RAM; player count is the limit | US$71.88 |
| 2 players | US$6.99 | Uncapped RAM; player count is the limit | US$83.88 |
| 4 players | US$9.99 | Uncapped RAM; player count is the limit | US$119.88 |
| 6 players | US$12.99 | Uncapped RAM; player count is the limit | US$155.88 |
| 8 players | US$15.99 | Uncapped RAM; player count is the limit | US$191.88 |
The same page displays a two-day free trial, North American and European regions plus Asia choices, instant setup, full file access, support and a seven-day refund policy. Verify the current terms, taxes, renewal conditions and region availability before paying; promotional offers and plan limits can change.
What are you actually paying for when you rent?
Rental fees buy infrastructure and reduced administration rather than a special version of Core Keeper. A provider supplies an always-on machine and data-center connection, then usually exposes setup and file controls through a panel.
- Availability: the world can remain reachable while the owner’s home computer is shut down.
- Convenience: instant setup can remove operating-system installation, router configuration and some routine maintenance.
- Support: the checked example advertises support, which can be valuable when the server process or panel behaves unexpectedly.
- Location: choosing a region near most players can reduce the distance traffic travels. A region far from the group can undermine the reason for renting.
- Control: full file access is advertised in the checked example, but confirm whether you can change launch arguments, download backups and select the exact server version you need.
Renting does not remove every responsibility. You still need to protect access credentials, make independent backups and verify that updates do not affect your world or mods, if you use any. The provider controls the underlying machine, so you also accept its outage procedures and acceptable-use rules.
How do self-hosting and renting compare over a year?
At the published rates, renting costs US$71.88 per year for the one-player tier, US$119.88 for four players and US$191.88 for eight players if the monthly price remains unchanged. Self-hosting avoids those invoices, but it is not automatically free: electricity, replacement hardware, storage and the value of the administrator’s time all count.
If you already own a low-power computer that runs other services, the additional cost of hosting Core Keeper may be small. Buying a new machine solely for this game changes the calculation; compare its purchase price and electricity use with several months of hosting. The available evidence does not establish a universal electricity rate or a break-even date, so calculate using your local power price and the hardware you actually own.
Which option is better for different groups?
The best answer changes with your group’s schedule, equipment and tolerance for maintenance.
Choose self-hosting when
- A spare desktop, NAS or mini PC can stay on whenever the world may be used.
- One person accepts responsibility for installation, updates, backups and recovery.
- Your group plays often enough to benefit from avoiding a monthly fee.
- You want direct access to world files, configuration and launch arguments.
- You are comfortable deciding between relay and direct IP/port connectivity.
Choose renting when
- Players need to enter while the usual host is away or offline.
- No one wants to leave a home computer running continuously.
- Your home connection is unstable, bandwidth-limited or difficult to configure.
- You prefer a predictable bill and a provider’s support channel.
- The group wants a quick setup and a region selected near its players.
Reconsider self-hosting when
Do not buy a dedicated machine merely to avoid a small monthly fee unless someone is genuinely willing to maintain it. A server that is powered off, loses its connection or has no current backup is cheaper on paper but worse for the group’s actual play schedule.
Reconsider renting when
If you play only occasionally, already have suitable hardware and can manage it safely, a rental may provide little value between sessions. Likewise, a capable home machine running several services may make self-hosting practical, provided Core Keeper receives enough resources and the operator can isolate failures.
How do you set up a self-hosted world safely?
Use this sequence to reduce the most common avoidable failures.
- Choose the host machine. Confirm that it meets the indicative two-core, 2.4 GHz-or-faster baseline, has at least 2 GB of RAM for a one-to-four-player group and 10–20 GB of available storage, with additional headroom for the operating system and other services.
- Install the server. Use Steam’s Library > Tools entry or SteamCMD app ID 1963720.
- Start it in PowerShell. Leave the documented process running and configure the computer not to sleep while players may be connected.
- Identify data locations. Find the worlds and configuration folders documented by the setup guide. If
worldsis absent, let a player join and create the first save before diagnosing the installation. - Select connectivity. Use the Game ID relay path when you do not want an open port. Use the direct IP/port path only after checking firewall, router and cross-play requirements.
- Create a recovery copy. Back up the world and configuration before sharing the game code and before every version change.
- Test with one player. Join from another account, load the intended world, confirm that progress saves, then test a restart.
- Document the routine. Record the launch arguments, backup location, restart method and the person responsible for updates.
- Add resilience. Use the documented optional auto-restart script if appropriate, and arrange a notification or manual check so a crash does not remain unnoticed.
How should you evaluate a rental before committing?
A short trial is useful only if you test the things that matter to your group, not just whether a control panel opens.
- Select a region close to most players and note whether movement and world interaction feel consistent during a busy session.
- Confirm the advertised player limit for the plan you are considering.
- Start a fresh world, invite every expected player and verify that the save persists after a stop and restart.
- Download or otherwise verify access to the world and configuration files before investing time in the world.
- Check whether launch arguments, version selection and restart controls are available at the level your group needs.
- Read the renewal, refund, trial and support terms, including any limits that are not shown in the headline monthly price.
The checked example displays a two-day trial and seven-day refund policy, but those terms belong to that provider and may change. Treat the trial as a technical acceptance test, not proof that every future update or outage will be handled identically.
What can go wrong, and how do you recover?
The world is offline when nobody expected it
For self-hosting, check that the computer is powered on, awake, connected and still running the PowerShell process. For a rental, check the provider panel for a stopped process, maintenance notice or resource error, then contact support with the server time and error message.
The worlds folder is missing
The setup guide notes that this folder may not appear until a player joins and the first save is created. Connect once, exit normally, then inspect the documented server data location again.
Players cannot connect through a direct address
Verify that a port was actually configured, the operating-system firewall allows the server, the router forwards the same port and the address is reachable from outside the home network. If you do not need direct connectivity, switch back to the Game ID relay path rather than exposing a port unnecessarily.
An update appears to have damaged the world
Stop further update attempts, preserve the current files for diagnosis and restore the last known-good backup. Confirm the server version and launch arguments before trying the updated installation again.
Performance degrades as the group grows
Compare current resource use with the indicative IONOS figures, close competing services and check whether the home connection is saturated. On a rental, ask support whether the plan’s player cap, region or host-node load is involved; “uncapped RAM” in the published example does not mean unlimited CPU, network capacity or player slots.
What is the final decision rule?
Rent when uninterrupted access and low administration are worth roughly US$6–US$16 per month for your group size. Self-host when you already have suitable always-on hardware, can maintain backups and updates, and value control more than convenience. In both cases, test a join, a save and a restart before building a world your group cannot easily replace.
Frequently Asked Questions
Can I run the server on the same PC I use to play Core Keeper?
It can be viable if that computer meets the indicative resource baseline and remains powered on while other players need access. Running the game client and server together leaves less headroom, so watch memory, CPU and connection stability during a full-group session.
Does using the relay path eliminate every networking problem?
No. Relay connectivity avoids the need for an open inbound port, but players can still encounter account, firewall, version or service-availability problems. Test the actual accounts and locations your group will use rather than assuming the path guarantees a connection.
Is a host’s advertised RAM enough to compare plans?
Not by itself. The checked plans describe uncapped RAM while limiting player count, but CPU capacity, storage performance, region, backups and support can matter just as much. Ask what happens when the server reaches its player limit and how files can be recovered.
Should I publish the game code publicly?
Treat the code as access information for your intended players, not as a public invitation. The setup guide specifically recommends backing up before sharing a game code; keep a known-good copy first and rotate access or change the sharing method if unwanted players appear.
What should I record before handing server duties to someone else?
Write down the installation method, application ID, launch arguments, world and configuration locations, backup schedule, restart procedure and the person responsible for updates. This documentation prevents a single operator’s absence from becoming an unrecoverable outage.