VDS Start
₺899.00 / month
- 4 ayrılmış çekirdek
- 8 GB RAM
- 200 GB NVMe
- 10 TB Trafik
- 1 IPv4
Keep your factory running while you are offline: run the Factorio headless server on a VDS with dedicated cores and let your friends join whenever they like.
Quick answer
Factorio server hosting means running the game's official headless server on a machine that is online 24/7. By default the server listens on 34197/UDP, reads its configuration from server-settings.json and requires every player to run the same game version and the same mods. Because the Factorio simulation leans heavily on a single core, clock speed matters more than core count; for large factories a VDS with dedicated cores is the most balanced choice.
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
| Scenario | RAM | vCPU (high clock) | Disk |
|---|---|---|---|
| 2–4 players, vanilla, early game | 2–3 GB | 2 | 10 GB NVMe |
| 4–8 players, mid-size factory | 4–6 GB | 2–4 | 20 GB NVMe |
| Space Age, several planets | 6–8 GB | 4 | 30 GB NVMe |
| Megabase or heavy mod pack | 8–16 GB | 4+ | 40 GB NVMe |
Estimates; actual needs depend on mods, plugins and settings.
Factorio multiplayer uses a lockstep architecture: every client simulates the whole world itself, and only player actions travel over the network. The server is the referee that orders and distributes those actions. This keeps traffic low, but every participant must run exactly the same game version and mod set, otherwise the connection is refused or a desync occurs.
Hosting from your own PC is fine for short sessions, but when you quit the factory stops and your friends cannot join. A dedicated server keeps the map online, takes regular autosaves and does not depend on your home upload speed. When nobody is connected, the headless server pauses the game by default; if you want the world to keep running while empty, start it with --no-auto-pause.
The official server software comes in two forms: the Linux headless package from factorio.com, which ships without graphics and sound libraries, and the regular game files started with --start-server. On a rented server the lightweight headless package is the usual choice.
For a small group of friends on an early-game map, 2–3 GB of RAM and two fast cores are usually enough; what really decides the requirement is the size of the factory. The table above is an estimate: two factories with the same player count can consume very different resources once one of them becomes a train-filled megabase.
Factorio performance is measured in UPS (updates per second), with a target of 60. The main simulation loop runs largely on one core, so the cure for UPS drops is usually higher clock speed and fast memory access rather than more cores. Because of lockstep, if the server slows down every player slows down, and the weakest client can also drag the factory's rhythm down.
Size the server for your factory goals rather than the number of players.
This page lists VDS packages for Factorio: you can install the server yourself or request a ready-made setup through a support ticket. On a VDS the CPU cores and memory are reserved for you, so a neighbour's load does not cut your UPS, a difference you feel directly in a game as sensitive to single-core speed as Factorio.
A VDS also gives you full root access: you can pin the headless package to any version, switch to the experimental branch, open an RCON port and run a second test map on the same machine. Choose the package that matches your factory goals from the live table; you can add resources later if you grow.
To compare the two models, see game server package or VDS. In short: a group playing one map that never wants to touch a terminal is better served by a managed setup; anyone running several maps, testing mods or using custom scripts benefits from the flexibility of a VDS. NVMe storage, KVM virtualisation and network-level DDoS filtering are shared by both models on LIONFIN infrastructure.
You can also run several Factorio servers side by side, each started with its own port and folder, and test a new mod pack or Space Age map on a staging server without touching your main factory.
server-settings.json controls how the server behaves. You create it by copying the bundled server-settings.example.json and point the server at it with --server-settings. The most used fields are:
| Field | What it does |
|---|---|
name, description, tags | Name, description and tags shown in the server browser |
max_players | Concurrent player limit; 0 means unlimited |
visibility | public and lan visibility; the public list requires a factorio.com account |
username, token | Credentials for the public list; a token is recommended over a password |
game_password | Password to join the server |
require_user_verification | Verifies players against their factorio.com account |
autosave_interval, autosave_slots | Autosave interval (minutes) and number of rotating save slots |
afk_autokick_interval | Time before an idle player is kicked |
The admin list lives in server-adminlist.json and updates automatically when you use /promote in game. Use --create for a new map and --start-server-load-latest to open the latest save.
Mods go into the server's mods folder as .zip files and are enabled in mod-list.json. When a player connects, Factorio lists missing or mismatched mods and lets the client sync mods from the official mod portal in one step, so running a modded server is less painful than in most games.
Restart the server after changing the mod list. Adding a mod to an existing map is usually painless; removing one deletes its items from the map, so rolling back means restoring a backup.
The most common cause of UPS drops is the factory itself, so reviewing the in-game design is often more effective than upgrading hardware. On the server side, a fast single core, dedicated resources and sensible save settings make the difference.
autosave_interval that suits your pace; saving too often hurts gameplay, too rarely increases the risk of data loss.Use top or htop to watch load from the command line: a single core sitting near 100% means the factory has reached the CPU limit.
A publicly listed Factorio server exposes its IP address, so it is open both to denial-of-service attacks and to unwanted players. The first layer of defence is the network: at LIONFIN traffic is filtered at network level by the RouteFence firewall, DDoS attacks are filtered before they reach your server where possible, and the infrastructure is monitored 24/7 by our NOC and SOC (see our data center).
34197/UDP and, if you use it, the RCON port open; close the rest with a firewall such as UFW.require_user_verification enabled and use game_password or a whitelist for a private community.--rcon-port, --rcon-password) only with a strong password and, if possible, to specific IP addresses.Factorio saves can contain commands and mod scripts; check saves and mods from unknown sources before uploading them.
A map you played single-player or on a friend's PC can be moved straight to the server: a save is a single .zip file. On Windows saves are in %APPDATA%\Factorio\saves; upload the file over SFTP to the server's saves folder and start it with --start-server mysave.zip.
mods folder.Factorio's rotating autosave slots are the first safety net, but not enough on their own: saves on the same disk do not protect against disk failure or a wrong command. Copy the save folder off the server daily and take a manual copy before big updates, following the 3-2-1 rule.
In Factorio the server's location determines how quickly your commands are confirmed, so if most of your players connect from Türkiye a nearby data center makes the game feel noticeably smoother. In lockstep the client only applies the final result of an action once the server has scheduled it. Factorio hides this wait with client-side latency hiding: walking and building previews appear instantly, the real result arrives a few frames later.
Latency hiding doesn't cover everything. At high latency fast belt placement, driving vehicles or firing weapons in combat feel “sticky”. Packet loss is worse: the player's simulation waits until a lost packet is resent, which shows up as short freezes.
If your group is spread across cities, keep the server in the region that is closest on average. Bandwidth is rarely the bottleneck, since even a factory with hundreds of trains generates little traffic. What matters is network stability and whether the CPU keeps up with the simulation: a slow server slows the game even with low ping, and high ping delays actions however powerful the server is.
Updating a Factorio server means downloading the new headless package and replacing the old files; as long as saves and settings are kept separate it takes a few minutes. Wube Software publishes two channels: stable and experimental. The server must run the same version as players' Steam clients, otherwise connections are refused with a version mismatch error.
For community servers: keep players on stable, move to experimental only when you all agree, and copy the save folder before updating. Once a new version converts a save, it may not open on the old version; rolling back is only possible with a pre-update backup.
Pinning matters even more on modded servers. After a big update mod authors may need time to catch up; meanwhile you can keep the server on the old version and ask players to select the same version in Steam's beta tab. On a VDS you can keep several headless versions in separate folders and choose which to start in the service definition. Update during quiet hours and warn players in advance.
Factorio offers in-chat commands to players with admin rights; the same commands work from the server console and over RCON.
/promote and /demote: grant or remove admin rights./kick, /ban, /unban: remove or ban players who break the rules./whitelist: creates a closed community server only listed players can join./server-save: saves immediately without waiting for the autosave; useful before maintenance./players: lists connected and known players.Larger communities often connect the server to Discord through RCON-based tools, relaying in-game chat to a channel or showing the online player count; you can run such a bot as a small process on the same VDS. Lua /c console commands are powerful, but using them disables achievements for that save; use them carefully or turn them off with --disallow-commands. Keeping the admin list short is the best protection against accidental damage to the map.
Most Factorio server problems come from version, mod or port mismatches, and the log file factorio-current.log usually states the cause clearly.
mod-list.json.public is not enabled in visibility, or username/token is missing. Connecting directly by IP works independently of the list.34197/UDP is closed in the firewall, or only TCP was opened. Factorio uses UDP only.If you get stuck, open a support ticket from the customer panel with the log file attached.
Choose a VDS package
Pick a VDS from the package table that matches your factory goals and order it with a Linux distribution such as Ubuntu.
Download the headless package
Connect over SSH, download the Linux headless package from factorio.com and extract it into the home directory of a separate user.
Prepare the settings file
Copy server-settings.example.json to server-settings.json and fill in the name, password, visibility and token fields.
Create or upload the map
Use --create for a new map, or upload your existing save file to the saves folder over SFTP.
Open the port and start
Open 34197/UDP in the firewall, start the server with --start-server and run it as a service so it stays up.
Connect and plan backups
In game, use Multiplayer, Connect to address and enter the IP; then set up a daily backup of the save folder.
Factorio uses port 34197 by default, and only the UDP protocol. You can change the port in the settings or with the --port parameter. Opening TCP in the firewall is not enough; you need a UDP rule. If you use RCON, also open the RCON port you choose.
The separate headless package is published for Linux only. On Windows you can run a server by starting the normal game files with the --start-server parameter. Rented servers usually use the Linux headless package because it consumes fewer resources.
The headless server package can be downloaded from factorio.com, but every player who connects must own the game. Publishing the server in the public list also requires the username and token of a factorio.com account.
With max_players set to 0 there is no fixed limit in the game; the practical limit is set by factory size, the server’s single-core speed and players’ connections. Small servers for groups of friends are common, while event servers host much larger sessions.
Yes. On a Factorio 2.0 server the Space Age expansion is enabled as an official mod. Players need to own Space Age to join a map with the expansion enabled. Because several planets are simulated at once, memory and CPU needs rise compared with a vanilla map.
When a player connects, Factorio lists missing or mismatched mods and offers to download and sync mods from the official mod portal. For mods outside the portal, players must install the same files manually.
Not by default; the headless server pauses automatically when no players are connected. If you want the world to keep running while empty, start the server with the --no-auto-pause parameter. CPU usage then continues around the clock.
UPS usually drops as the factory grows: many trains, robots, fluid systems and belts load a single core. A server with high clock speed and dedicated cores, less frequent autosaves and an efficient factory design all reduce UPS drops.
Yes. A save is a single zip file; take it from your saves folder, upload it to the server’s saves folder and start with --start-server. The server’s game version must not be older than the save, and the same mods must be installed.
Yes. Start the server with the --rcon-port and --rcon-password parameters to send commands remotely. Because RCON provides console access, use a strong password and open the port only to your own IP address if possible.