Short answer. You can host an Avorion server yourself for free: download the Avorion dedicated server (Steam app 565060) with SteamCMD and an anonymous login, start ./bin/AvorionServer with a galaxy name, and open the ports you give it with --port, --query-port, --steam-master-port and --steam-query-port. Or rent an Avorion server and skip the install and the port forwarding.

Players join through the in-game server list while the server is listed, and each player needs their own copy of Avorion (Steam app 445220).

Checked on 5 November 2026 against Avorion 2.5.13 (default branch since 16 March 2026). Boxelware announced patch 2.6 on 29 October 2026 for December 2026.

This guide uses Boxelware's Steam announcements and store page, plus what we run on our own Avorion servers: the exact SteamCMD app, the start line and the files the panel writes. We found no Boxelware page on running the dedicated server, so where a detail could not be confirmed, this guide says so instead of guessing. To go straight to the rental route, see Option 2.

What you need

Operating system: 64-bit Linux for the steps below. The Avorion store page lists Windows, macOS and Linux for the game, and our servers run the Linux server build.
Hardware: Boxelware does not publish dedicated server requirements on the Steam page (it lists what the game itself needs).
Network: four ports, one for each of --port, --query-port, --steam-master-port and --steam-query-port, reachable from the internet. We found no Boxelware source that lists the protocol for each port, so if you are unsure, allow both TCP and UDP on the ports you chose.
Steam account: not needed to download the server. Our install uses an anonymous login.
The game: every player needs their own copy of Avorion.

The server software is free. You pay for the machine, power and bandwidth, not the software.

Option 1: host it yourself

This works on a spare PC, a home server or a cloud virtual machine. The SteamCMD flow below is the one our own install script uses, trimmed to what a single machine needs.

Linux (Debian or Ubuntu)

Create a steam user and switch to it, so the server lives in its own account.
```
sudo useradd -m steam
sudo -iu steam
```
Install SteamCMD as that user, after installing the 32-bit libraries Valve's SteamCMD page lists for your distribution. This is the same tarball our install script downloads.
```
mkdir ~/Steam && cd ~/Steam
curl -sSL https://steamcdn-a.akamaihd.net/client/installer/steamcmd_linux.tar.gz | tar zxvf -
```
Download the server.
```
~/Steam/steamcmd.sh +force_install_dir /home/steam/avorion +login anonymous +app_update 565060 validate +quit
```
Do not trust the "success" message alone. In our installs SteamCMD downloads fail now and then, about two in seven on a clean install, and it still reports success. Check that a file named appmanifest_565060.acf exists in /home/steam/avorion/steamapps/. If it does not, run the command again.
Copy the Steam client libraries. Our install script copies both steamclient.so files from SteamCMD into a .steam folder inside the server folder, and our start line then points HOME at the server folder so the server finds them:
```
mkdir -p ~/avorion/.steam/sdk32 ~/avorion/.steam/sdk64
cp ~/Steam/linux32/steamclient.so ~/avorion/.steam/sdk32/
cp ~/Steam/linux64/steamclient.so ~/avorion/.steam/sdk64/
```

Start the server. This is the shape of our start line, with the settings written as arguments. The numbers are example values to adapt:

cd ~/avorion
mkdir -p galaxy
export LD_LIBRARY_PATH=./linux64
HOME=/home/steam/avorion ./bin/AvorionServer --galaxy-name MyGalaxy --datapath /home/steam/avorion/galaxy \
  --port 27000 --query-port 27003 --steam-master-port 27021 --steam-query-port 27020 \
  --max-players 10 --difficulty 0 --collision-damage 1 --save-interval 300 \
  --same-start-sector true --server-name "My Avorion Server" --threads 1 --listed true

The first start creates the galaxy under --datapath. The server is ready when the log prints:

Server startup complete

Open the ports. Allow the four ports you chose on the machine's firewall and forward them on your router to this machine (TCP and UDP if you are unsure, as above).
Join from the game. With --listed true, look for your server name in the in-game server list. --listed false keeps it out of the list.

What the start-line settings do

--galaxy-name: the save the server loads. In our setup, a name that does not exist yet starts a new galaxy in a folder of that name under --datapath.
--admin: grants admin to the player ID you give (our panel asks for a Steam64 ID). Our start line only adds it when the field is filled in.
--difficulty: our panel accepts -3 to 3, with 0 as the default.
--same-start-sector: true or false. Our default is true.
--threads: how many threads update sectors at the same time. Our default is 1.
--save-interval: seconds between saves. Our default is 300.

Steam Workshop mods

Our setup lists mods in modconfig.lua inside the galaxy folder, one Workshop ID per entry, and the server downloads them from Steam when it starts:

modLocation = ""
forceEnabling = false
mods =
{
  {workshopid = "1234567890"},
}
allowed =
{
}

The ID above is a placeholder. Use the number at the end of a mod's Workshop address.

Running in a container

On our servers, Avorion would not start when it ran as a numeric user ID with no entry in the container's /etc/passwd, because it calls getpwuid() at startup. Our install plants the libnss-wrapper library, and our start line writes a one-line passwd and group file for whatever ID the server runs as, then preloads the wrapper with LD_PRELOAD, NSS_WRAPPER_PASSWD and NSS_WRAPPER_GROUP. On a normal Linux user account you do not need any of this.

Option 2: host it on PlayNHost

Renting removes the SteamCMD install, the firewall and the update routine. The start line, with its four port settings, is filled in for you.

Pick a plan. Open the Avorion server hosting page and compare the plans (NAONITE, OGONITE and AVORION at the time of writing, for 12, 20 and 35 players). Press Create Server on NAONITE or OGONITE, or Customize Plan on AVORION, and finish the order. Prices change, so check them on that page.
Wait for the install. You get an email when it is ready, and the server appears at panel.playnhost.com. On the Console tab, the panel counts the server as running when it prints Server startup complete.
Open Settings, then Game Settings. These fields feed the start line shown above:
- Galaxy Name: the save the server loads. A new name starts a fresh galaxy and leaves the old one on disk.
- Server Name: the name in the server list.
- Admin ID: the Steam64 ID of the player who gets admin. Leave it empty if you do not want one.
- Game Difficulty, Collision Damage, Save Interval (seconds), Same Start Sector and Threads: the matching start-line settings.
- List Publicly: true shows the server in the in-game list, false hides it.
Max Players is shown read only and follows your plan. Under Show advanced you will find Auto Update (on by default, so the server checks Steam for a new build when it starts) and Beta branch.
Restart. When the panel shows "Saved. The server must restart before these take effect.", press Restart now and wait for Server startup complete.
Add Workshop mods (optional). Open the Workshop tab, paste each mod's Steam Workshop address or ID into the Mods list, press Add, then Save. Press Restart to apply: the server rewrites modconfig.lua from that list every time it starts, and downloads the mods from Steam itself.
Join. Find your server name in the in-game server list. Everyone joining needs the same mods as the server.

What the panel does for you

Install checks. The install script retries SteamCMD up to three times and only continues once the app manifest exists, so a silent failed download stops the install instead of leaving an empty server folder.
Ports. The panel passes your game port and the query, Steam master and Steam query ports to the start line for you.
Mods file. modconfig.lua is regenerated at every start from the Workshop list. Hand edits to it do not survive a restart, so change the list instead.
Container fix. The nss_wrapper setup described above is already in place.
Galaxy reset. The Quick Tasks tab has a Galaxy reset task that stops the server, deletes the galaxy save and starts it fresh. Settings survive. It clears the whole galaxy folder, including galaxies kept under other names, so take a backup first if you want an old galaxy.

Self-hosting or renting: an honest comparison

Cost. Self-hosted: the software is free, and you pay for hardware, power and bandwidth, or a cloud virtual machine. Rented: a monthly fee set by plan. See the current plans.
Availability. Self-hosted: as reliable as your machine, power and home internet, and it has to stay on when your crew plays. Rented: runs on the host's hardware, not your PC.
Network exposure. Self-hosted: four ports open to the internet on your connection, and you look after the firewall and router. Rented: your home IP is not involved.
Skill needed. Self-hosted: command line, SteamCMD, port forwarding and an update routine. Very doable, and a good way to learn. Rented: a web panel with form fields.
Updates. Self-hosted: stop the server, run the SteamCMD command again, start it. Rented: Auto Update installs a new build when the server starts.

Self-hosting suits you if a machine already runs all day and you are comfortable with networking. Renting suits you if you would rather not look after hardware.

Common problems and fixes

The server dies on first boot with an empty folder

Cause: the SteamCMD download failed but reported success.

Fix: check for steamapps/appmanifest_565060.acf in the install folder. If it is missing, run the app_update 565060 validate command again.

The server does not start in a container

Cause: in our experience, the user ID has no passwd entry, and Avorion calls getpwuid() at startup.

Fix: use the nss_wrapper setup from the container section above, or run the container as a user that exists in the image.

Your server is not in the list

Cause: it was started with --listed false (List Publicly set to false on PlayNHost), or the query ports are not reachable from outside.

Fix: set it to listed, check that all four ports are open and forwarded, and restart.

Your mods file changes back (PlayNHost)

Cause: the server rebuilds modconfig.lua from the Workshop list every start.

Fix: change the mods on the Workshop tab, save and restart.

FAQ

Can I host an Avorion server for free?

Yes. The dedicated server downloads with an anonymous login, so the software costs nothing. You still pay for the machine, power and internet, and it must stay on while people play.

Do I need to own the game to run the server?

Not to download it: the anonymous login does not need a Steam account. Each player needs their own copy of Avorion to join.

How many players can join?

That is your --max-players value when you self-host. Our plans are 12, 20 and 35 players.

Which Steam app is the dedicated server?

We install app 565060 with SteamCMD. The game itself is app 445220.

Can I use Steam Workshop mods?

Yes. List the Workshop IDs in modconfig.lua, or on PlayNHost add them on the Workshop tab, save and restart.

Ready to skip the setup? See the Avorion server plans.

How to host an Avorion server (2026)