Skip to content

Downloads

Pick a platform and the page will query the latest stable SSUI release directly from GitHub. The filename shown below is the actual release asset you are about to download, not a filename guessed from an old install.

Latest stable release

Checking GitHub...

Loading the current release metadata.

View release
Windows 64-bit

Run the `.exe` from a writable installation folder.

Open release page Waiting for release data...
Linux amd64

Download the executable, then make it runnable with `chmod +x`.

Open release page Waiting for release data...
Docker

Pull the image and keep the complete installation in one `/app` bind mount.

Open Docker guide ghcr.io/steamserverui/stationeersserverui:latest

GitHub release lookup is loading.

If GitHub's API is temporarily unavailable, use GitHub releases and choose the asset for your platform. The page caches a successful lookup in your browser for a short time so opening the documentation does not hit the API on every visit.

Which file do I need?

Platform Asset to choose Notes
Windows 64-bit Windows amd64 executable It has the .exe suffix. Install the current Microsoft Visual C++ runtime if Stationeers asks for it.
Linux 64-bit Linux amd64 executable It has no .exe suffix. Make it executable with chmod +x before the first run.
Docker Published container image Do not download a native executable into the container. Pull the image and keep the complete installation in the /app bind mount.

The release asset name includes the SSUI version and platform. Use the asset from the release you selected instead of guessing from an older filename. If you are on v5 and moving to v6, read the upgrade notes before replacing anything.

For a complete migration checklist, use Upgrade from v5. It explains the API, backup identity, authentication and Docker changes that are easy to miss when the first browser login looks normal.

Stable, nightly and release candidates

  • Stable is the normal choice for a server you want to forget about for a while.
  • Release candidates are intended for real-world testing before a stable release. They can contain rough edges and require deliberate update confirmation.
  • Nightly builds are development builds. Use them when you are testing a fix or feature and are prepared to report what broke.

Do not mix the executable from one release with the runtime data of an unrelated installation while troubleshooting. Keep the binary and its installation folder together, and keep a copy of the complete data directory before a major upgrade.

After downloading

Continue with the platform-specific installation guide, or jump directly to first-time setup if SSUI is already running.


Documentation home · Installation · First-time setup