A Satisfactory dedicated server gives a group one shared factory without requiring a particular player to host the session from their own computer. It is useful when players join at different times or when you want server settings, saves, and administration to live in one place.
This guide covers the choices to make before creation, how to prepare the first session, and what to check when a player cannot join.
Decide what the server needs
Decide which game branch your group will use, which region is convenient for most players, and how demanding the factory may become. MaximusHost recommends 8–16 GB RAM and 4–6 vCPU. The create form offers 6–24 GB RAM and 2–8 vCPU.
Treat this as a place to begin. A distributed factory with active automation, logistics, and exploration can use more resources than a new save. The Satisfactory RAM and CPU guide explains how to size from your own usage.
Satisfactory requires a dedicated IP for its network ports. The create form shows the requirement and estimate for your account.
Create the server in MaximusHost
Open My Account, choose My Servers, then open Create New Server and select Create Satisfactory. Enter a server name and location, then choose RAM and CPU cores. Review the available options, one-time creation charge, and running estimate before submitting.
Review the resource estimate and any one-time creation charge before submitting. Dedicated-IP billing depends on the allocation assigned to your account; see Billing and Credits for details.
After submitting, return to My Servers and wait for the server to show it is ready. Then open its management page. The Create a Satisfactory server guide walks through the form.
Use a compatible game branch
In the Satisfactory management controls, choose the Public or Experimental branch. Players need a compatible branch and game build to connect. Before changing branches for a group:
- Tell every player which branch the server will use.
- Make a manual save before changing a consequential setting.
- Verify the selected branch after the update completes.
- Test with a small group before treating the new branch as the group’s normal world.
Experimental can receive changes before Public. Your players need a compatible branch and game build, and mods or existing saves may also depend on a particular version. Make a save before switching and have everyone update to the same branch.
Join your Satisfactory server
Once the server is ready, use Satisfactory’s in-game server manager and the connection details shown for your server. Keep the manager’s server name and password available, and make sure your game is on the same branch as the server.
If a player cannot join, first check that the server is started, the address and any configured password are correct, the player is on a compatible branch/build, and the server is not already at its configured player limit. Avoid changing multiple settings while diagnosing one connection problem.
The Satisfactory management overview describes the management tabs. Use the console and logs guide to check server messages when troubleshooting a connection.
Configure the server deliberately
From the server manager, review status, saves, server options, and advanced settings. The Satisfactory tab includes the game’s server settings and API access. The owner manages the API token; shared users need the relevant permission for settings. Make a manual save before major changes and check whether the game requires a restart for them to apply.
Use a server name your group can recognize, keep client and admin credentials private, and avoid treating a shared dashboard link as the same thing as server ownership. If you share access, use the platform’s supported sharing controls and grant only the permissions the other person needs.
Protect a factory before major changes
Before changing branch, game options, or mods, create a manual save from the Satisfactory management area. Keep the save and note the previous branch and mod versions while you test the change.
Keep track of what changed and when. A short note containing the prior branch, relevant mod versions, and the last known-good save makes troubleshooting more practical than relying on memory after a major update.
Solve common connection problems
If the server is not visible or a player cannot connect, work through a short checklist:
- Confirm the server is started and the player is using the displayed connection information.
- Confirm the player and server use compatible Public or Experimental branches and game builds.
- Confirm the player has the right password if the server requires one.
- Check the configured player limit and supported server settings.
- Review logs in the manager before changing resources or reinstalling content.
If a problem started after a mod or game update, pause further changes, use the save you created before the update as a reference point, and test compatibility methodically. More RAM or CPU will not repair a branch or content mismatch.
Next step
Review Satisfactory hosting for the dedicated-IP estimate, then use the creation guide when you are ready to set up the server.
