FreeOrion

Last reviewed Sep 13, 2026 · 849 words

Hosting a FreeOrion game is the rare self-hosting job with no Docker image, no web UI and no database: you run one binary called freeoriond, open one TCP port, and hand your friends the address. The catch is not the setup, it is the calendar. A 6-player galaxy takes 150 to 300 turns to resolve, each turn waits on the slowest human, and the version lock means one player updating their client mid-game can lock everyone else out. Plan for those three things and the rest is easy.

What you are actually running

FreeOrion is a C++ engine with most of the game content, including the AI players, scripted in Python. The 1,039-star repository ships the client (freeorion), the dedicated server (freeoriond) and the AI client as separate executables, and the project has been going since 2003 under GPL-2.0, which is why it feels closer to a mature Master of Orion successor than a hobby project. Builds exist for Windows, macOS and Linux; there is no container because the server expects the same data directory as the client and nobody has felt the need.

Budget the 1 GB of RAM from the catalogue for the server itself, then add memory for every AI empire you enable, since each AI runs as its own Python process and a large galaxy late in the game gets noticeably heavier. A 4-core box with 4 GB handles a 6-empire game comfortably; a Raspberry Pi will run it but late-game turn processing gets slow enough to annoy people.

Two ways to host, and only one suits a homelab

The easy path is in-client hosting: one player picks Multiplayer, Host, and their machine becomes the server for as long as the client stays open. That is fine for a Saturday LAN and wrong for a game that lasts weeks, because the host has to be present for every turn.

The homelab path is the dedicated server. freeoriond runs on its own in what the project calls hostless mode, listens on TCP 12345 by default, and keeps the game state between sessions. Players connect whenever they have a spare 20 minutes, submit orders, and disconnect; the turn advances once everyone has submitted or a turn timer expires. Run it under a systemd unit or a screen session on a machine that stays on, forward 12345 through your router or put the box on Tailscale so the port never touches the open internet. The server also broadcasts on UDP 12346 for LAN discovery, which you can ignore for remote play.

The version lock is the trap

FreeOrion refuses connections between mismatched versions, and it means it: same release, same build, on every client and the server. This is the single most common way a multi-week game dies. Someone's package manager updates their client, they can no longer join, and either everybody upgrades (and the save may not load) or that player is out.

Pin the version before the first turn. On Linux, install from the project's own release archive rather than a distro package that will move under you, and tell players to do the same. Keep the server's save files backed up every few turns; they live in the server's data directory as plain files and a copy is cheap insurance against the one player who insists on upgrading.

Turn timers keep the game alive

Without a timer, a game at turn 80 quietly dies the week one player goes on holiday. Set a turn deadline in the server's multiplayer settings so the turn advances without absent players, and use the empire's automatic orders where possible. My rule from two long-running games: 24 hours per turn early on, 48 hours once fleets are moving and turns need thought, and be explicit with the group that a missed turn is a missed turn. The game is deep enough (procedural galaxies, tech trees that reward planning, diplomacy) that people stay engaged if the pace is predictable.

Where it sits among self-hosted games

If your group wants real-time strategy, 0 A.D. and OpenRA are the bigger projects and both have simpler LAN hosting. FreeOrion is the one to host when the appeal is the slow burn: a persistent galaxy that people log into on their own schedule, the only serious free answer to Master of Orion. The broader games category has the dedicated-server options for everything else.

What I'd do

Run freeoriond as a systemd service on whatever always-on box you have, expose port 12345 only over a VPN, pin every player to one release from the official download page, and set a 48-hour turn timer from day one. Copy the save directory nightly with the rest of your backups. That is about an hour of setup for a game that will then run for months with no further attention from you, which is a better return than most of what I host.