VDS Start
₺899.00 / month
- 4 ayrılmış çekirdek
- 8 GB RAM
- 200 GB NVMe
- 10 TB Trafik
- 1 IPv4
Let your friends into the factory even when you are offline: run the Satisfactory dedicated server on a VDS with dedicated resources and never lose your save.
Quick answer
Satisfactory server hosting means running Coffee Stain Studios’ official dedicated server software on an always-on machine so the factory no longer depends on a host player. The server is downloaded with SteamCMD from ID 1690800, runs on 64-bit Windows and Linux and uses ports 7777 TCP/UDP and 8888 TCP. Large late-game factories can need close to 16 GB of memory. At LIONFIN you install it yourself on a VDS server or request the setup through a support ticket.
There is no ready-made package for this use yet; these servers give you full control to install it yourself, or you can request setup through a support ticket. You complete the order on our Turkish store page.
₺899.00 / month
₺1,599.00 / month
₺2,899.00 / month
| Players / stage | RAM | vCPU | Disk |
|---|---|---|---|
| 1–4 (early game) | 8 GB | 2–4 | 20 GB NVMe |
| 4–8 (mid-size factory) | 12 GB | 4 | 30 GB NVMe |
| 8–12 (large factory) | 16 GB | 4–6 | 40 GB NVMe |
| 12+ (late game, megabase) | 16–24 GB | 6 | 50 GB NVMe |
Estimates; actual needs depend on mods, plugins and settings.
The Satisfactory dedicated server is the official application that simulates the game world on a separate server instead of on a player’s PC. In normal multiplayer the session depends on the host’s computer: when the host quits, the factory stops, nobody else can join and the whole simulation load sits on one player’s CPU.
A dedicated server solves all three problems:
The server is managed from inside the game through the Server Manager screen introduced with version 1.0. On first connection you “claim” the server and set a server name and an admin password. That password limits loading saves, starting new games and changing server settings to admins only. An optional player password restricts who can join.
A Satisfactory server needs at least 8 GB of RAM; 16 GB is recommended for large saves or more than four players. This matches the hardware recommendations on the community-maintained official wiki, and the values in the table above are estimated ranges based on it.
In Satisfactory, resource needs depend more on factory size than on player count. A world with a few iron lines in the early hours runs light, while late-game saves with hundreds of buildings, long rail networks and multi-storey production blocks strain memory and CPU. Every item on every conveyor belt is data the server tracks.
On the CPU side the wiki stresses high single-core performance, since much of the simulation runs on one thread. A few fast, dedicated cores are therefore better than many slow ones; on a VDS your cores are reserved for you, which removes fluctuations caused by neighbouring workloads.
The wiki also notes that the server does not run on 32-bit x86 or ARM processors and has problems in virtual machines where the CPU model is exposed as generic kvm64. If you see a CPU-related error at start-up, open a support ticket to have the virtual CPU model checked. Disk needs are about 8 GB of install space on Linux and about 12 GB on Windows; leave extra room for saves and automatic backups. Creating a swap area on Linux reduces the risk of sudden crashes when memory runs out, but it is no substitute for enough RAM.
At LIONFIN you run a Satisfactory server on a VDS; this page shows VDS plans for the game. You can install the server yourself or open a support ticket after ordering the VDS and ask for the setup.
Because Satisfactory needs more memory than many lighter games, dedicated resources matter here in particular. The stutter seen in late-game saves on shared environments is largely eliminated on a VDS, where cores and memory belong to you alone. On a VDS you can also:
systemd service so it starts automatically after reboots,For the differences between a game package and a VDS and when each makes sense, see the game server package vs VDS comparison. Current core, memory and disk values are listed in the plan table on this page.
A common pattern in Satisfactory groups is to start small in the first weeks and run short of resources as the factory grows. On a VDS you simply move to a larger plan and run the same server with more memory. Back up the save folder before upgrading to keep your factory safe in case anything goes wrong. You can also run a second Satisfactory instance on the same VDS on different ports, for example a main world and a separate world for friends who are just starting; remember that memory needs double in that case.
The Satisfactory dedicated server officially runs on 64-bit Windows (Windows 10/11, Windows Server 2016, 2019, 2022) and on Linux distributions such as Debian and Ubuntu. For a long-running server, Linux uses less disk and memory and needs no licence; Windows suits those who prefer visual management over Remote Desktop.
A typical Linux installation goes like this:
steamcmd +force_install_dir /home/satisfactory/server +login anonymous +app_update 1690800 validate +quit./FactoryServer.sh (FactoryServer.exe on Windows). To change ports, use the -Port= and -ReliablePort= parameters.systemd service so the game starts when the VDS reboots.To use the experimental branch, add -beta experimental to the SteamCMD command; the server and all players must be on the same branch.
Current Satisfactory servers need ports 7777/TCP, 7777/UDP and 8888/TCP open. Ports 15777 and 15000, used during early access, were removed with 1.0; if you see them in older guides, they are out of date.
| Port | Protocol | Purpose |
|---|---|---|
7777 | UDP | Game traffic and Lightweight Query API |
7777 | TCP | Server traffic and HTTPS API |
8888 | TCP | Reliable messaging |
If you use UFW on Ubuntu, example rules are:
sudo ufw allow 7777/tcp
sudo ufw allow 7777/udp
sudo ufw allow 8888/tcp
The community wiki states that all three rules are required and that a missing port leads to connection timeouts. On Windows, create the equivalent inbound rules in Windows Defender Firewall.
To move a world you started in single-player or a friend session to the server, use the save upload feature in Server Manager; you do not need to copy files manually. Once connected as admin, pick the save from your PC under Manage Saves, upload it and start the uploaded session.
Save files are stored in these folders:
~/.config/Epic/FactoryGame/Saved/SaveGames/server%LocalAppData%\FactoryGame\Saved\SaveGames\serverIf you prefer to move the save manually, copy the .sav file into this folder and select it in Server Manager. Stop the server before moving it; a running server may overwrite the file during an autosave.
Server settings (name, player password, admin password, session to autoload) are kept in a separate ServerSettings save file. According to the wiki, deleting this file resets the admin password if you forget it, but it also resets the server name, player password and certificate. That is why this file belongs in your backups too.
In Satisfactory, players connect by adding the server’s IP address and port in the Server Manager screen on the main menu; there is no classic public server list. This means your server is only found by people who know the address, giving private friend groups a natural layer of privacy.
From the player’s side, the steps are:
If you want a memorable name instead of an IP address, create an A record under your own domain (for example factory.yourdomain.com) pointing to the VDS’s IPv4 address; players can type that name into Server Manager. The record stays valid as long as the server IP does not change. Make sure everyone’s Steam or Epic client is up to date to avoid version mismatches; Satisfactory lets Steam and Epic players meet on the same server.
A Satisfactory server allows 4 players by default; more requires a configuration change. The community wiki shows the limit can also be changed with a launch parameter:
./FactoryServer.sh -ini:Game:[/Script/Engine.GameSession]:MaxPlayers=8
The same setting can be written to the server’s Game.ini file. The game is balanced for four-player co-op; raising the limit also raises memory use and network traffic. If you plan for eight or more players, choose resources from the upper ranges in the table.
Other management options are on the Server Manager settings tab:
To shut the server down cleanly, the wiki recommends the Shutdown function of the HTTPS API; killing the process directly can put the last save at risk.
Yes, Satisfactory mods are developed by the community and can be used on a dedicated server, but there is no official Workshop support. The mod ecosystem revolves around the Satisfactory Mod Repository on ficsit.app and the Satisfactory Mod Manager (SMM).
Things to watch when running mods on a server:
Opening a modded save on an unmodded server can make the structures added by the mod disappear, so always take a separate backup before removing mods.
Satisfactory server security rests on a strong admin password, opening only the ports you need and network-level DDoS filtering working together. On LIONFIN infrastructure the RouteFence firewall filters at the network level and traffic is monitored 24/7 by our NOC and SOC teams; more on that on our data center page.
Measures to take on the server:
Keep in mind that the HTTPS API allows admin actions such as shutting down the server, loading saves and changing settings. If you use the API for automation, do not leave the credentials in plain text in script files, and store scripts with permissions that only the game server user can read. As more people gain access, changing the admin password and revoking former admins’ access is a good habit. Applying operating system updates regularly and disabling unused services completes the rest of server security.
Satisfactory’s autosaves live on the server’s own disk; if the disk or operating system has a problem, they are affected too. The way to protect a factory with hundreds of hours in it is to copy the save folder off the server regularly.
SaveGames/server folder into a dated file at least once a day.Following the 3-2-1 rule (three copies, two media types, one off-site) is a sound general strategy for valuable saves.
Most connection problems on Satisfactory servers come from a missing port rule, and most performance problems from insufficient memory.
| Symptom | Likely cause | Fix |
|---|---|---|
| Server Manager cannot find the server | 7777/TCP or UDP closed | Open all three port rules |
| Timeout while connecting | 8888/TCP closed | Open the reliable messaging port |
| Server crashes on start-up | Unsupported CPU model | Open a support ticket to have the virtual CPU type checked |
| Stutter and disconnects in late game | Insufficient memory | Move to a larger plan, remove unnecessary mods |
| Connection refused | Server and client versions differ | Update the server with SteamCMD, match branches |
To tell network delay apart from a resource shortage, compare ping with the server’s CPU and memory use at the time of the problem. A data center in Türkiye suits players connecting from Türkiye and the surrounding region.
Choose a VDS plan
Pick a VDS plan suited to your factory size, with at least 8 GB and preferably 16 GB of memory; Ubuntu or Debian is recommended as the operating system.
Download the server files
Create a separate user and run app_update 1690800 with SteamCMD to download the dedicated server files.
Open the ports
Allow 7777/TCP, 7777/UDP and 8888/TCP in the firewall.
Start the server as a service
Define FactoryServer.sh as a systemd service and start it, so the server comes back up automatically after reboots.
Claim it with Server Manager
Add the server’s IP address in the in-game Server Manager and set the server name and admin password.
Upload your save and back it up
Upload your existing save from the Manage Saves screen, then set up a job that backs up the save folder regularly.
According to the community wiki, at least 8 GB of memory is required, and 16 GB is recommended for large saves and more than four players. Planning for more than 16 GB for late-game factories and modded setups reduces the risk of stutter.
Yes. The Satisfactory dedicated server officially supports 64-bit Linux; Debian and Ubuntu are common choices. 32-bit and ARM processors are not supported. A Linux install takes up less disk space than Windows.
Current versions use port 7777 over both TCP and UDP and port 8888 over TCP. The 15777 and 15000 ports left over from early access are no longer needed. All three rules must be open.
Yes. After connecting as admin, upload the save from your PC under Manage Saves in Server Manager and start the session. You can also copy the .sav file into the server’s save folder manually if you prefer.
The default limit is 4 players. The MaxPlayers value can be raised in Game.ini or with a launch parameter. The game is balanced for four-player play; more players need more memory and bandwidth.
According to the community wiki, deleting the server’s ServerSettings save file resets the admin password. It also resets the server name, player password, autoload session and certificate; your game saves are not affected. Back the file up before deleting it.
That depends on a Server Manager setting. If pause-when-empty is enabled, the simulation stops and saves resources; if disabled, production lines keep running while you are away. Choose based on how your group plays.
Yes; mods are community-made and managed with the Satisfactory Mod Manager. The server and players must use the same mod versions, and each mod must support dedicated servers. Wait for mod compatibility after big game updates.
Yes. Add -beta experimental to the SteamCMD command to download the experimental branch. Players must select the same branch in their client. Because experimental builds carry a save compatibility risk, always take a backup before switching.
After ordering your VDS, open a ticket from the Support section of the customer panel and ask for the Satisfactory dedicated server to be installed. Mention the target player count, the branch you want and whether you have a save to transfer. If you need help ordering, contact us by email.