For an occasional game with a small, trusted group, self-hosting on a computer you already own is usually the cheapest and simplest choice. For a world that should stay available while nobody is playing, renting a managed server—or running a separate always-on machine—is usually better. The real decision comes down to uptime, administration time, CPU performance, backups, network reachability and how much control you want over saves and mods.
Factorio includes a free Linux headless-server package, so self-hosting does not require buying another server licence. Renting trades that control for a recurring bill and less infrastructure work. This guide explains the practical differences, the hardware and networking requirements, and which approach fits different kinds of factories.
What is the difference between self-hosting and renting a Factorio server?
Self-hosting means the server process runs on your home PC, a spare desktop, a small home server or another machine you administer. You supply the hardware, power, internet connection, operating system, firewall rules, updates and backups. You can run a normal multiplayer session from a gaming PC or use Wube Software’s dedicated Linux headless package.
Renting means the Factorio process runs on a virtual private server (VPS) or a managed game-hosting account in a provider’s facility. The provider supplies the datacenter connection and physical infrastructure. Depending on the plan, you may still be responsible for the game version, mods, saves and settings; “managed” does not automatically mean that someone else maintains your world.
| Concern | Self-hosting | Renting or managed hosting |
|---|---|---|
| Cost | Low marginal cost when suitable hardware and internet service already exist; electricity and eventual hardware replacement still count. | Recurring monthly charge; a reliable current price comparison was not established, so compare live plans before buying. |
| Availability | Stops when the host, household power or home connection goes offline. | Designed for continuous operation in a datacenter or provider environment. |
| Control | Control of the operating system, Factorio version, mods, saves, firewall and backup method. | Control depends on the panel and contract; file access, version pinning and restore tools must be checked. |
| Administration | You handle installation, port forwarding, updates, monitoring, security and recovery. | The provider handles infrastructure, while game administration may remain your responsibility. |
| Performance | You choose the CPU and can reuse strong hardware, but home equipment and network quality set the limit. | Performance depends on the allocated CPU and whether shared resources are oversubscribed. |
| Backups | You create, retain and test save and mod backups. | Backups may be included, but retention, download access and restoration procedures vary. |
Which option fits the way your group plays?
The best choice is determined more by availability and maintenance tolerance than by the number of players shown on a hosting plan.
Occasional sessions with a small, trusted group
Start with client hosting or a self-hosted machine that is already available. This avoids a monthly charge and is adequate when everyone can agree on a play schedule. The compromise is that the host must be online, and the world is inaccessible during a power, internet or computer outage.
A persistent friends’ world
Rent a managed server or operate a separate always-on machine. Players can join at different times without waiting for one person to launch the game, and the world can continue between sessions if auto-pause is disabled. A separate home machine gives similar availability without putting the server on the host’s gaming desktop, but you still own every maintenance task.
A technical owner with spare hardware
Self-hosting provides the greatest control and can have a low marginal cost. It is suitable only if your connection accepts inbound traffic, you are willing to maintain the operating system and Factorio installation, and you will make tested backups rather than relying on the live save.
A large factory or mod-heavy save
Choose the strongest predictable per-core CPU you can obtain, enough memory for the world and mods, and storage with dependable snapshots or downloads. Do not select a plan solely because it advertises a high player count: Factorio’s simulation load is driven heavily by factory complexity, mod behavior and activity.
No networking or Linux experience
A managed host removes router configuration and much of the server installation friction. Before paying, confirm that its panel supports the mods you need, lets you download the save, allows the required game version to be pinned and explains how a restore works.
How much CPU and RAM does a Factorio server need?
Wube Software’s current PC requirements, checked in 2026, list 4 GB of RAM and a dual-core processor running at 3 GHz or faster as the minimum. The recommended desktop specification is 8 GB of RAM and a quad-core 3 GHz-or-faster processor. Those figures describe the game generally, not a guarantee for a heavily modded or very large server.
| Reference point | Memory | Processor guidance | Qualification |
|---|---|---|---|
| Official minimum (Wube Software, checked 2026) | 4 GB | Dual-core, 3 GHz or faster | Minimum PC requirement; leaves less headroom for large factories or other services. |
| Official recommended (Wube Software, checked 2026) | 8 GB | Quad-core, 3 GHz or faster | Recommended desktop specification, not a server performance guarantee. |
| IONOS planning figure (2023) | 2 GB | Not stated | Suggested for 1–4 players; world size and mods can raise demand. |
| IONOS planning figure (2023) | 4 GB | Not stated | Suggested for 5–12 players; treat as a planning estimate. |
| IONOS planning figure (2023) | 8 GB | Not stated | Suggested for more than 12 players; not a guarantee for every factory. |
Factorio simulation is particularly sensitive to single-core speed. A shared virtual CPU with an impressive total core count can still produce poor UPS (updates per second) if its per-core performance is weak or inconsistent. Ask a provider for the CPU model or a meaningful per-core guarantee rather than accepting “vCPU” as a performance description.
Player count is only one variable. A compact eight-player map can be lighter than a heavily automated two-player megabase. Trains, active production, enemy settings, scripted mods and the size of the explored map all affect simulation work. Leave memory for the operating system and any monitoring or backup process running alongside Factorio.
What do I need to self-host Factorio at home?
You need a machine that can remain powered on, a stable connection, a Factorio installation and a reachable network path for the players. Wube’s free Linux headless build is a practical option for a dedicated machine because it runs without graphics or audio. The stable headless release listed by Wube on October 26, 2026 was 2.1.23; pin the version that matches your clients rather than assuming the newest build is appropriate.
Home-hosting checklist
- A supported Factorio installation and a save file. A dedicated server needs a save before it can start.
- Enough CPU and memory for the factory, plus storage for the active save and dated backups.
- A fixed local address for the server, so the router rule does not point to a changing device.
- Firewall and router rules that permit Factorio’s normal UDP port, 34197.
- A way for players to reach your public address. Carrier-grade NAT (CGNAT) or an internet service that blocks inbound connections can prevent direct hosting.
- Automatic startup after a reboot, operating-system updates, account permissions and monitoring.
- Separate backups of the save and the exact mod set, with a restoration test.
How do I set up a self-hosted Factorio server?
The exact commands differ by Linux distribution and installation method, but the order below avoids the common dependency and version mistakes.
- Prepare the machine. Use a dedicated user account, update the operating system, choose a fixed local address and make sure the disk has room for saves and backups.
- Install the server package. Download Wube’s Linux headless build and unpack it under a directory owned by the server account. The package does not need a graphical desktop.
- Place or create a save. A dedicated instance cannot start without a save file. Copy an existing world or create one with a client, then keep the original safe while testing.
- Configure server settings. Set the server name, visibility, authentication options, autosave behavior and any whitelist or admin settings in the server configuration.
- Start the headless process. Use the package’s documented dedicated-server/start-server option and point it at the save. Run it under a service manager so it restarts after a reboot instead of depending on an open terminal.
- Open the network path. Allow UDP 34197 through the machine firewall and forward the same UDP port from the router to the server’s fixed local address. Test from outside your home network; a test from the same LAN can succeed even when inbound internet access is blocked.
- Synchronize clients. Every player must use exactly the same Factorio version and mod versions as the server. Have one known-good mod list before inviting the group.
- Back up before changes. Copy the save and mod list to separate storage, label the date and version, and verify that a copy can actually be restored.
- Monitor and maintain it. Watch disk space, CPU load, memory, UPS and logs. Apply operating-system and Factorio updates during a planned maintenance window, keeping a rollback copy first.
If your provider uses CGNAT and offers no inbound address or forwarding option, ordinary port forwarding will not solve the problem. You may need a different network arrangement, a relay or a rented machine; do not expose random ports or disable the firewall as a workaround.
What should I check before renting a Factorio server?
Renting removes the need to keep a home computer online, but it does not make every plan equivalent. Compare the operational details that affect your particular save.
CPU allocation
Look for the CPU model, dedicated or shared wording, and any per-core or performance policy. A plan with many low-performance vCPUs may be worse for a megabase than one with fewer, faster cores.
Memory and storage
Match memory to the world and mod load, then leave headroom for the operating system and backups. Confirm storage type, available space, snapshot limits and whether you can download the raw save.
Version and mod control
Check whether you can pin a Factorio release, install mods from your required set, upload a mod pack and roll back an update. A panel that only offers the latest version can strand a group whose clients have not updated.
Backups and restoration
Ask how often snapshots run, how long they are retained, where they are stored and whether you can restore a single save yourself. “Backups included” is not useful if retention is too short or the provider requires support intervention for every restore.
Access and location
Console access helps diagnose a failed launch or mod error. Choose a region close to most players when possible, while remembering that geographic distance is only one part of latency.
Cancellation and data export
Verify how to retrieve saves and mod files before cancellation, how quickly a server is deleted after non-payment and whether billing continues during a suspended state. A portable copy keeps your world from being locked to one provider.
How do mods, versions and backups affect the choice?
Factorio’s multiplayer documentation states that all game instances need exactly the same game versions and mods. A mismatch can prevent joining even when the server itself is healthy. Treat the save and its mod set as one release: record the game version, mod names, versions and configuration files together.
Safe update procedure
- Stop or pause the server at a planned time and announce the maintenance window.
- Make a dated copy of the save, mod directory and server settings.
- Change the game or mod version on the server first, then verify that the intended client set is available.
- Start the server and test with one administrator before inviting everyone.
- If a client cannot join or the simulation behaves incorrectly, restore the known-good save and versions rather than repeatedly changing files on the live instance.
Talos recommends backing up mods and saves together because a careless server-side mod update can leave clients unable to connect until they synchronize. This is equally important on a rented host: provider snapshots do not replace a downloadable backup that you control.
Will a Factorio server run while nobody is connected?
It depends on the auto-pause setting. Headless servers may pause automatically when no players are connected; ForgeWorld notes that administrators can disable auto-pause when overnight production is required. Disabling it keeps the simulation advancing and consumes CPU while the world is empty, so use it only when unattended production is intentional.
Availability and simulation are separate decisions. A home server can be configured not to pause, but it still stops if the machine or connection fails. A rented instance is designed to remain online, yet its game process can still be paused, stopped or broken by a version change unless you configure and monitor it.
What are the hidden administration tasks?
Self-hosting’s price advantage is partly payment in time. Plan for these recurring jobs:
- Applying security and operating-system updates without changing the game’s working version accidentally.
- Rotating credentials and limiting administrative access to trusted users.
- Checking logs, disk capacity, CPU saturation and UPS before players report a problem.
- Testing that automatic startup works after a power failure or reboot.
- Keeping dated save and mod backups off the server and periodically performing a restore drill.
- Documenting the router rule, local address, server version and recovery steps so another group member can restart the world.
A managed host usually performs the datacenter, power and hardware work, but you still need to maintain game settings, saves and mods unless the contract explicitly includes those tasks. Read the support scope instead of assuming “managed” covers gameplay administration.
What can go wrong, and how do I recover?
Players cannot see or join the server
Confirm that the server is running, UDP 34197 is allowed by the host firewall and forwarded to the correct local address. Test the public address from an external network. If the home service uses CGNAT, ask the provider about a public address or move the instance to reachable infrastructure.
A version or mod mismatch blocks connection
Compare the server’s Factorio build and every mod version with the client’s list. Restore the last known-good pair of save and mod files if an update introduced uncertainty.
The server starts but UPS falls
Check single-core CPU load, not only total utilization, and examine what changed in the factory or mod set. On a rented VPS, investigate noisy-neighbor or shared-CPU policies and request a move or a higher-performance allocation if the plan does not guarantee consistent CPU time.
A save is corrupted or an update fails
Stop making changes to the live copy. Restore the newest backup that predates the failure, validate it with the intended mod set, then keep the failed files for diagnosis rather than overwriting your only evidence.
The host computer is also used for gaming
Running the server and client on the same machine is convenient, but a reboot, crash or graphics-intensive workload affects everyone. A separate always-on machine or rented instance isolates the world from the host’s personal use.
Is renting worth it for a Factorio megabase?
Renting is worth considering when continuous access and predictable operations matter more than minimizing recurring cost. For a megabase, make CPU quality, memory headroom, snapshot access and version control the first purchasing criteria. A cheap plan that cannot sustain the simulation or restore a save is not economical.
Self-hosting can be the better technical choice when you already own a quiet, fast machine and have a reachable connection. You can select the operating system, pin every version, inspect files directly and tune backups without a provider’s panel. The trade-off is that you become the operator responsible for uptime and recovery.
How should I make the final decision?
- Decide whether the world must be available 24/7. If yes, use a rented instance or a separate always-on machine; if no, client hosting may be enough.
- Measure your real hardware. Compare the machine’s per-core performance, memory and storage with the factory and mod set, not just the player count.
- Verify network reachability. Confirm that inbound UDP 34197 and port forwarding are possible before committing to home hosting.
- Choose your maintenance budget. Count updates, monitoring, backups and troubleshooting as part of self-hosting’s cost.
- Demand portability. Whether rented or self-hosted, retain downloadable saves, mods and settings so you can recover or migrate.
- Test before inviting the group. Connect from an external network, run the intended mod set, restart the server and perform a restore test.
Wube’s official FAQ says, “Yes. For Linux servers there is a free lightweight dedicated headless server package.” That makes self-hosting viable without a separate server licence, but free software does not remove the costs of power, connectivity, administration or downtime. Rent when availability and reduced infrastructure work are worth the recurring charge; self-host when control, existing hardware and low marginal cost matter more.
Frequently Asked Questions
Can I move my Factorio save from a home server to a rented host?
Yes. Export the save, the complete mod set and the server configuration, then start the rented instance on the same Factorio version before changing anything else. Test the transferred world with one player and keep the original home copy until the migration has been verified.
Does a VPS need a graphics card to run Factorio?
A Linux headless server runs without graphics or audio, so a dedicated GPU is not the deciding component for server sizing. Spend the budget on strong per-core CPU performance, adequate memory, reliable storage and backups instead.
How can I tell whether my home internet uses CGNAT?
Compare the router’s reported internet-facing address with the public address shown by an independent external service. If they differ and your provider does not offer a forwardable public address, ordinary port forwarding may not make the server reachable from the internet.
How do I measure whether a host is fast enough for my factory?
Run the actual save and mod set, then observe UPS and single-core CPU usage during the busiest production and train activity. A short player-count test is not representative of a mature megabase, so keep a trial or migration window long enough to reproduce peak simulation load.