Is there a native Linux dedicated server for Empyrion?

No. Empyrion: Galactic Survival ships only a Windows dedicated server. To host it on a Linux box you run that Windows build under Wine, or use one of the community Docker images that wrap Wine for you. There is no native ELF server binary.

How much RAM does an Empyrion server need?

More than people expect. Empyrion simulates a whole star system of planets, playfields, and structures, so RAM scales with active playfields, not just players. A well-configured 4-core box with 64GB RAM comfortably hosts 20-30 players; high-population community servers run even more hardware. Plan for tens of GB, not the 8GB a small co-op survival game needs.

What is dedicated.yaml in Empyrion?

dedicated.yaml, in the Empyrion - Dedicated Server folder, is the main server config file. You set the server name, password, ports, max players, and the scenario/world there. It is the file you edit after the first install and the one most setup mistakes trace back to.

Should I use Wine or Docker to host Empyrion on Linux?

Both run the same Windows binary under Wine - Docker just packages the Wine environment so it is reproducible and easier to update. If you are comfortable with containers, a community Docker image is the cleaner long-term path; a hand-built Wine prefix gives you more control but more maintenance. Either way, verify the server is actually listening before trusting it booted.

Why are there so few Empyrion Linux hosting guides?

Most coverage assumes Windows or points you at the official Nitrado-powered rental. The Linux/Wine path is documented mainly in a couple of community Steam guides and Docker repos, so it is genuinely under-served - which is exactly why a clear, current Linux guide is worth having.

server setup

Empyrion Dedicated Server on Linux 2026: The Wine/Docker Reality

Empyrion: Galactic Survival has a thriving private-server scene and a glaring documentation gap: there is no native Linux server. On a Linux box you run the Windows build under Wine or in Docker - and almost nobody explains how. Here's the honest path, plus the RAM appetite that surprises first-time hosts.

Published 2026-06-21 · Updated 2026-06-21

The Linux gap nobody documents

Empyrion is a long-running space sandbox - build ships, drop onto planets, fight, mine, automate - with a durable community-server culture (high-population servers like HWS have run for years). It is niche but sticky, which is exactly the profile where good hosting docs are scarce and worth writing.

The thing that trips people up: Empyrion ships only a Windows dedicated server. There is no native Linux ELF binary. So if your fleet is Linux - as most VPS and dedicated boxes are - you have two real options, and both run the same Windows executable under Wine:

A hand-built Wine prefix running the server directly.
A community Docker image that packages Wine plus the server for reproducible deploys.

Most public coverage either assumes Windows or sends you to the official Nitrado-powered rental. The Linux/Wine path lives in a couple of community Steam guides and Docker repos - genuinely under-served, which is the gap this guide fills.

Install: SteamCMD + the Windows server

The dedicated server is a separate Steam app from the game:

Game (client): app 383120
Dedicated server: app 530870 - this is what you install on the host

You pull app 530870 with SteamCMD. On Windows that is the whole story. On Linux, SteamCMD downloads the same Windows files, and Wine is what actually runs them - so the install and the runtime are two separate problems to solve.

Running it under Wine or Docker

The official Empyrion Dedicated Server Setup wiki documents the Windows flow; the Linux specifics come from the community Linux Dedicated Server (WINE/Docker) guide on Steam. The practical decision:

Docker (recommended for most). A community image bundles the Wine environment so updates and redeploys are reproducible. Best if you already run containers - you avoid fighting a Wine prefix by hand.
Hand-built Wine. More control, more maintenance. You manage the prefix, the runtime libraries, and the update cycle yourself.

The cross-cutting rule for any Wine-wrapped server: do not trust "the process is running" as proof it booted. Confirm the server is listening on its ports and answering queries before you tell players to connect - a stalled Wine server can look alive while no world has loaded.

dedicated.yaml and ports

The main config file is dedicated.yaml in the Empyrion - Dedicated Server folder. This is where you set:

Server name, description, and join password
Max players and the game/Steam query ports
The scenario or world the server loads

Forward and open the configured ports on your firewall and router. Most setup failures that are not Wine problems are config problems in dedicated.yaml - a wrong port, a scenario that is not present, or a typo that stops the world from loading.

The RAM appetite

This is the part that surprises people coming from lightweight co-op survival games. Empyrion simulates a star system - multiple planets, orbital playfields, and every structure on them - so RAM scales with active playfields, not just player count.

Server size	RAM	CPU	Notes
Small group (4-8)	16-24GB	4 fast cores	A few active playfields; comfortable for friends.
20-30 players	~64GB	4+ strong cores	A well-configured box hosts this range comfortably.
High-pop community	64GB+	Powerful multi-core	HWS-style servers run serious hardware.

Add Wine overhead on top of the bare numbers. The takeaway: Empyrion is not an 8GB game like a small co-op survival server - budget tens of GB. For how this compares across games, see our game server RAM and sizing guide.

Self-host vs rent

Self-host on Windows. Simplest, because the binary is native - good if you have a spare Windows box with the RAM.
Self-host on Linux (Docker/Wine). The realistic path for a Linux fleet, but you own the Wine wrapping and the update maintenance.
Managed hosts. Empyrion's official servers are powered by Nitrado, and a few other providers (Survival Servers and others) list it. Renting buys you out of the Wine problem entirely - the main reason to pay for this particular game.

Because the Linux path is the awkward one, Empyrion is a game where renting is defensible specifically to skip the Wine maintenance. For the broader trade-off, see dedicated box vs VPS vs cloud game servers.

FAQ

Is there a native Linux dedicated server for Empyrion?: No. Empyrion ships only a Windows dedicated server. To host on Linux you run that Windows build under Wine, or use a community Docker image that wraps Wine. There is no native ELF server binary.
How much RAM does an Empyrion server need?: More than people expect. RAM scales with active playfields, not just players. A well-configured 4-core box with 64GB comfortably hosts 20-30 players; small groups want 16-24GB. Plan for tens of GB, not 8GB.
What is dedicated.yaml in Empyrion?: It is the main server config, in the Empyrion - Dedicated Server folder: server name, password, ports, max players, and scenario/world. Most non-Wine setup mistakes trace back to it.
Should I use Wine or Docker to host Empyrion on Linux?: Both run the same Windows binary under Wine; Docker just packages the environment for reproducible updates. Containers are the cleaner long-term path; a hand-built Wine prefix gives more control but more maintenance.
Why are there so few Empyrion Linux hosting guides?: Most coverage assumes Windows or points at the official Nitrado rental. The Linux/Wine path lives in a couple of community Steam guides and Docker repos - genuinely under-served.