TL;DR / Summary: Factorio’s headless server lets friends share one factory without tying it to a living-room PC. A budget VPS with modest CPU, enough RAM for your save, and a stable network path beats a laptop that sleeps mid-smelt. Pick a plan using VPS buying guides, then keep mods and autosaves disciplined.
Why headless belongs on a VPS
Hosting on a home machine couples playtime to whoever’s electricity and Wi-Fi mood. A small always-on VPS keeps the belt running while you work. Headless builds skip GPU needs; Factorio cares about single-thread speed and memory for entity counts more than flashy graphics silicon.
Sizing against base bloat
Early game saves are light. Late-game megabases with rich mods are not. Start with 2–4 GB RAM for vanilla-ish maps and watch resident memory after each science surge. CPU clock matters; a quieter dual-core with higher GHz often feels better than many slow cores. Check regional latency so peers in your time zone are not simulating rubber belts.
- Disk: SSD for save churn; keep old autosaves pruned.
- Network: foresee map downloads when friends join the first time.
- Backups: copy the save directory off-box before experimental mods.
Install without turning the VPS into a desktop
Use the official headless package on a minimal Linux image. Run under a dedicated user. Open only the Factorio port you need. Skip installing full desktop environments “for convenience”—they waste RAM you paid for factories. When comparing hosts on virtualserversvps.com, favor clean Linux templates over Windows for this workload.
Autosave policy that saves friendships
Frequent autosaves protect against biters and bad deconstruction planners. Too frequent on a tiny disk fills inodes and space. Keep a rotating handful, plus a weekly offsite copy named by date. Agree in chat before anyone clicks “delete all unused chunks” experiments.
The factory must grow; the save folder must not grow forever.
Mods as a contract
Publish a pinned mod list in a repo or shared note. Mismatched versions strand friends at the join screen. Update mods on a scheduled night, snapshot the VPS first, and keep the previous save zip. Chaos mods are content; unversioned chaos is downtime.
Admin commands and trust
Limit who holds the server password. Griefing with diggers is funny once. Use Factorio’s admin tools for pause, kick, and quieting of friendly fire accidents during late-night sessions.
Performance smell tests
If UPS drops or belts stutter for everyone, check entity counts, pathfinding from biters, and whether a roommate process stole CPU. Upsize RAM before assuming you need a huge CPU plan. Sometimes pruning abandoned outposts helps more than spending money.
Firewall and friend access patterns.
Prefer allowlisting friend IPs when the group is small and stable. If IPs churn, use a VPN hub or password rotation schedule rather than leaving the Factorio port casually open to the world. Griefers enjoy unsecured factories as much as biters do.
Document who holds the server password in a shared vault. People leave gaming groups; credentials should not linger like abandoned drills.
Version upgrades as scheduled events.
Factorio updates can invalidate saves or mods. Treat major versions like tiny launches: announce a night, snapshot the VPS, copy the save offsite, upgrade, smoke-test alone, then invite friends. Surprise updates mid-session are how Sunday afternoons turn into Discord forensics.
Keep the previous headless binary zip for one rollback window when an experimental build misbehaves.
Power spikes and neighbor processes.
If you co-host a website on the same budget VPS, expect FPS-like stutter when traffic and factories peak together. Serious groups dedicate the instance. Casual groups schedule website deploys away from peak play. Shared tiny boxes are political documents as much as technical ones.
Name the Linux service unit clearly and enable it on boot so a provider reboot does not wait for a human to restart the factory. Friends will assume the server is “dead” when only systemd was never enabled. Test a reboot once during daytime.
Collect a short join guide with ports, mod versions, and preferred headset etiquette. Technical hosting still fails socially when voice chat norms are undefined. Put the guide beside the save backups.
Watch CPU steal time on busy hypervisors. If the factory stutters while graphs show low usage inside the guest, the neighbors may be noisy—migrate region or plan before blaming belt designs. Not every hitch is a spawner problem.
Archive scenic screenshots outside the VPS. When a map finally collapses under its own beauty, you will want memories that are not trapped inside a deleted instance.
Keep a “map seed and mod hash” note beside each offsite save zip. When someone asks to roll back three weeks, you need identity, not a folder of mysterious timestamps.
Agree on quiet hours if some players live with light sleepers on voice chat while others smash biters at midnight. Hosting is social infrastructure. Put quiet hours in the same note as the mod list so nobody claims ignorance.
When the map outgrows the budget plan, vote before upgrading: cut abandoned outposts, split to a new save, or pay for RAM. Silent upgrades by one player create awkward money talks later. Put the decision on a calendar like any other factory milestone.
Factory floors that stay online overnight
A budget Factorio VPS is a social appliance: sized for the save you actually play, patched lightly, backed up before mod nights, and closed to surprise ports. Keep the image minimal, the mod list pinned, and the autosaves finite. When morning players log in to the same smelter line you left humming, the hosting choice already paid for itself.



