How to Host a Factorio Dedicated Server Yourself

Factorio is still widely played more than a decade after launch, and multiplayer is where factories get ambitious. If you want a world that stays online when your PC is off, you need a dedicated server.

You have two realistic paths: host it yourself on a VPS or home machine, or rent a managed Factorio server. This guide focuses on the DIY route so you know what is involved before you decide.

Self-host vs managed Factorio hosting

Self-hosting gives you full control, and you install the headless server, open ports, and manage updates, backups, and mods. Managed Factorio hosting trades that work for installation, panel access, restarts, DDoS protection, and file management. A home machine or a VPS is still self-hosting: you do the same admin work either way.

Managed hosting is the practical choice when UPS drops, friends need the world available around the clock, or you would rather build belts than debug systemd. This page does not publish a VPS price or an AleForge plan price.

What you need to run a Factorio dedicated server

A Factorio dedicated server needs a stable always-on machine or VPS, a strong single-thread CPU, enough RAM for the save and mods, fast storage, network access for players, and time for updates and backups. Factorio is CPU-bound, so a stronger single core matters more than a large core count. This page does not publish a core count, a RAM size, or a size by player count.

• CPU: Prioritize solid single-thread performance, especially for megabases, heavy mods, and late-game UPS.
• RAM: Start modestly for a small vanilla co-op world and scale as the save and mod set grow.
• Storage: Use SSD or NVMe storage where possible for autosaves and map loading.
• Network: Use a public IP or a port-forwarded home connection, with the UDP/TCP access Factorio requires.
• Operations: Plan time to apply game updates and maintain backups.

Space Age, larger mod packs, and late-game factories are the situations most likely to need a CPU and RAM upgrade sooner.

How to set up a headless Factorio server

Install the dedicated server files, create or add a save, configure server-settings.json, allow player connections through your firewall or router, and supervise the process so it can restart after crashes or reboots. Keep regular autosaves and copies of those saves off the server machine.

1. Get the dedicated server files through SteamCMD or the official standalone dedicated server package.
2. Create or copy a save into the server save directory, or generate a new map on first launch.
3. Configure server-settings.json with the server name, description, visibility, maximum players, autosave interval, and an optional password.
4. Add trusted admins in server-adminlist.json so they can run multiplayer commands.
5. Open the Factorio port on the firewall or router so friends can join by IP.
6. Start the headless process and verify that friends can join directly, or that the server appears in the in-game browser when it is public.
7. Place matching mod ZIPs in the mods folder when using mods, and enable Space Age content when the group owns it.
8. Use systemd, Docker, or a panel to supervise the process, then schedule autosaves and copy them off the machine regularly.

The Factorio multiplayer wiki is the reference for multiplayer behavior. Factorio’s forums also have dedicated-server guides for Windows and Linux.

Mods, Space Age, and common DIY gotchas

Game version, mods, autosaves, and backups have to stay in step on a DIY server. Every host and client needs the same game version and the same mod set, or players cannot join. This page does not publish a save-migration procedure.

• Versions and mods: Keep the game version and the full mod set identical on the server and every client.
• Public listings: Put a Factorio username and token on the server when you want it in the in-game browser.
• Autosaves and backups: Keep rolling autosaves. A corrupted save after a power blip is worse than a missed production cycle.
• Performance: UPS drops as factories grow. One home PC can eventually fail to keep the simulation smooth.
• Home connectivity: CGNAT, dynamic IPs, and residential upload limits are common reasons a server works locally and fails for friends.

Getting Started with Factorio covers token setup, autosaves, admin lists, and Discord bridges on a managed server.

When DIY stops being worth it

DIY stops being worth the effort when the server machine limits UPS, friends cannot reliably connect, or updates and save recovery take time away from playing. Compare a host on the features already in this guide: installation and restarts, panel access, DDoS protection, file and mod management, one-click mods, a location closer to the group, and always-on uptime.

• Your factory’s UPS is limited by the machine under your desk.
• Friends cannot join because of networking problems or power outages.
• You are tired of applying updates and restoring saves.
• You want one-click mods, locations closer to your group, or always-on uptime without babysitting.

At that point, a managed Factorio server can cost less than the time spent on administration.

Start DIY, or skip the sysadmin work

You can absolutely host Factorio yourself with the headless dedicated server, a stable CPU, open ports, and disciplined backups. Use this guide to try DIY first if that is your goal.

When you want the factory online without the maintenance, spin up an AleForge Factorio server and get back to building.