Satisfactory Server Self Hosting: When to Stop and What to Check

A dedicated Satisfactory server is for PC players on Steam or Epic; PlayStation and Xbox players cannot join it or cross-play with PC. If you searched for Satisfactory server self hosting after several evenings of setup, the decision is whether someone can own the remaining network, save and update work. For a compatible PC group that wants less of that work at home, Game Hosting’s Satisfactory server is claimed for its owner and saves before stops, restarts and updates. That moves the server machine and its reachability out of your home; it does not remove the recurring fee or make console saves compatible.

Check whether your home network can accept players#

When friends cannot connect, first separate the home router from the server computer. The current dedicated-server ports are 7777 over TCP and UDP, plus 8888 over TCP for Reliable Messaging. A port-forward on the router sends traffic toward the computer; a firewall rule on the computer allows it through that last layer. Both can be right while the connection still fails upstream.

The port list and protocol details are in our current Satisfactory port guide; the full self-hosting path covers the installation and network setup. If the router’s WAN address is not the public address your connection presents, ask your ISP whether it can provide a reachable address. Repeating firewall changes will not remove an upstream CGNAT limit. If the ISP cannot offer a workable inbound path, count that as a real boundary of home hosting rather than another evening of trial and error.

Be cautious with older setup posts and search summaries: some still recommend UDP ports 15000 and 15777, which are no longer used. Follow the current port list for this game build instead of opening extra rules from a pre-1.0 guide.

Protect an unclaimed server before sharing its address#

A new Satisfactory dedicated server starts unclaimed. The first person who reaches it through Server Manager can claim it as the administrator, so do not publish the address while you are still deciding who owns the server. The admin password controls management; a separate player password can limit who joins. Those are different credentials.

For a home server, agree on the owner before the first connection and keep the admin password somewhere the owner can recover it. Avoid asking every player to claim it or sharing the admin credential as if it were a join password. If the server has already been claimed by the wrong person, stop and preserve its saves and settings before using a recovery procedure.

Our guide to claiming a Satisfactory server safely covers the exact claim and recovery flow. This is a checkpoint, not a reason by itself to rent: once a trusted person has claimed the server and kept the admin password, the remaining question is whether your group wants to own the routine maintenance.

Save the factory before a planned stop#

A graceful stop does not automatically save the active factory. By default, the dedicated server autosaves every 300 seconds and keeps 3 rotating autosaves, but that interval can leave recent work outside the last save. Before planned maintenance, use the server console to request a save and wait for its confirmation:

server.SaveGame <session-name>

The name must be the active session’s name. If you are about to update the server, change branches or remove a content mod, also keep a separate copy of the save before making the change. Do not treat a scheduled autosave as a tested backup or assume an update can be reversed by reinstalling the old server files.

If you plan to move the world, upload a copy through Server Manager → Manage Saves and verify that the new server loads the intended session while the original save remains untouched. That is a safe check to make before stopping the old route for good; it is not evidence that a particular migration has been tested here. The complete dedicated-server guide explains the self-host save workflow, and our save-file location reference distinguishes server saves from other PC files.

Compare factory load with the memory you have#

The official dedicated-server guidance starts at 8 GB of RAM and suggests 16 GB for a large save or more than four players. Treat those as starting points, not a promise that every factory fits. In Satisfactory, memory use follows the factory as it grows; player count alone will not tell you how much your current save needs.

On a home machine, compare the server process’s memory use after the factory is loaded with the memory the operating system and other applications also need. Leave room for the PC you use to play if it shares the workload. There is no universal tier or fixed amount of memory growth that fits every factory, and this guide does not claim a measured performance result for your save. If the machine cannot keep a stable margin, someone needs to reduce other workloads, add resources or move the server to a machine with an appropriate allocation.

Match the server build before a patch or mod change#

Steam and Epic update their clients independently. The server and everyone joining need compatible branches and builds. As checked on October 18, the official patch notes, wiki and current-version template list Stable and Experimental as 1.2.4.1 (CL 513885, released October 12). Check the build actually installed on your server and clients before troubleshooting a version error.

A save written by a newer build may not load on an older one. Keep a separate save copy before changing branches or starting a patch, then let the server catch up to the clients’ compatible build. Do not switch a world between Stable and Experimental as a casual fix.

Mods add another compatibility check. The server runs Linux, so a mod needs a Linux server target and a release compatible with the selected game version; a Windows-only client download is not a substitute. Check the mod page and the Satisfactory Mod Loader release for the same game branch. Clients generally need the matching mod versions too, with client-only and server-only exceptions described by each mod. Back up the save before a content-mod change and confirm you can recover it before removing anything. SMM and SML are tools from the Satisfactory Modding project; each mod’s own author is listed on its ficsit.app page. Do not assume a mod will work just because it runs on one player’s PC.

Decide who owns the next evening of maintenance#

Self-hosting remains a reasonable choice when one person is willing to own a reachable connection, a powered machine, planned saves and the next update check. A firewall rule that has not been tested from outside the home, an unclaimed server or a missing game update may be fixable. The decision changes when the blocker is structural or no one can take responsibility for it.

A server process staying online also does not guarantee the factory keeps producing while it is empty. Satisfactory’s Auto Pause setting can pause the simulation when nobody is connected, so check it against what your group expects; our server-settings reference explains the option. Uptime and simulation progress are separate decisions.

There is no honest universal number of evenings or dollar amount that makes the choice for every group. If the recurring work has become the problem, revisit the rent, home PC or VPS comparison. A managed service adds a recurring bill and gives up some direct control, while shifting the server machine and network upkeep away from your home. Check the same PC-only boundary first: a rented dedicated server still cannot bring PlayStation or Xbox players into a PC world.