Resources for a growing factory
Choose from 6–24 GB RAM and 2–8 vCPU. We recommend starting with 8–16 GB RAM and 4–6 vCPU, then checking resource use as your factory and automation expand.
Game server hosting
Give your group a dedicated Satisfactory server, so everyone can return to the same factory without relying on one player to host. Choose resources for your build, then manage settings, saves, and branches as the factory expands.

Choose from 6–24 GB RAM and 2–8 vCPU. We recommend starting with 8–16 GB RAM and 4–6 vCPU, then checking resource use as your factory and automation expand.
MaximusHost routes Satisfactory game traffic on port 7777 and its server API on port 8888. A dedicated IP gives these ports an address for your server so they can be routed without conflicts. It is for network connections, not server performance.
Check status and logs, adjust server options, choose a game branch, and work with saves from your Satisfactory dashboard.
Owners can use Satisfactory Mod Manager with MaximusHost server file access. Keep the game, branch, mod, and client versions compatible.
See a Standard-account estimate in credits based on RAM, CPU, storage, and expected running time. If your game needs a dedicated IP, its estimated charge is included too. Stopped-server charges can vary by account, including whether a dedicated IP remains assigned. Review Billing and Credits for details. Setup also shows the one-time 50-credit server creation fee.
Choose a game to apply its recommended resources.
Custom estimate: choose whether a dedicated IP is required.
Standard account estimate
0 credits/month$0.00/month
Storage is charged only during estimated stopped time. Membership/reservation behavior can alter stopped-server dedicated-IP charges.
Production lines, automation, vehicles, explored areas, and active players all affect resource use. Start with the recommended range, then review live readings during a typical session.
After creating your server, choose Public or Experimental in its management settings. Everyone joining needs a compatible branch and game build, especially after updates.
Make a manual save before major settings, branch, or mod changes. Test the change with your group before building on the new setup.
We recommend 8–16 GB RAM and 4–6 vCPU, within a setup range of 6–24 GB RAM and 2–8 vCPU. Factory size, automation, and player activity all shape demand, so check live usage as your build grows.
MaximusHost uses port 7777 for Satisfactory game traffic and port 8888 for the server API. A dedicated IP gives your server its own address for those port connections. It is for networking rather than server performance.
Your estimate includes an IP charge when it applies. Whether that address remains billable while the server is stopped depends on your account and whether the allocation stays assigned; see Billing and Credits for details.
After creation, choose Public for players on the regular release or Experimental when everyone uses a compatible Experimental build. Change the branch in your Satisfactory server management settings; players and server need matching branches and versions.
Yes. Review RAM and CPU use during a normal factory session, then adjust resources from your server controls if the workload calls for it.
Satisfactory has an Auto pause when empty setting. When it is enabled, the game pauses factory simulation after players disconnect; when it is off, simulation can continue while the server is running. MaximusHost scheduling can start or stop the server separately. Check both settings before planning unattended production.
You can make manual saves before major changes, and server owners can use Satisfactory Mod Manager with server file access. Match game, branch, mod, and client versions before inviting the group back.
Choose your resources and get your game server ready.
Create an account to get started