Getting started¶
There are only a few clicks between you and a working Stationeers server. None require a degree in orbital mechanics.
The normal SSUI path is intentionally simple: download one executable, place it in a writable folder, run it and follow the browser wizard. This guide helps you choose the host and understand the few decisions that matter. You do not need to learn the advanced pages before the first server starts.
1. Choose where SSUI will run¶
| Host | Good choice when... | Start here |
|---|---|---|
| Windows 10 or 11 | You want the simplest familiar setup or already have a Windows server | Windows installation |
| Ubuntu LTS or Debian 13 | You want a lightweight native server and are comfortable with a terminal | Linux installation |
| Docker on Linux amd64 | You already operate containers and want the complete installation in one volume | Docker guide |
The installation guide covers the actual dependencies and commands for each platform. Not sure whether the machine is large enough? Read requirements and sizing. The world simulation consumes most of the resources, not the web interface.
2. Install it¶
The native installation is deliberately boring:
- Download the correct SSUI executable.
- Put it in a new writable folder.
- Run it as your normal user.
- Let SSUI install SteamCMD and Stationeers.
- Open
https://<server-address>:8443.
The installation guide includes copyable commands, the Windows runtime dependency and Linux permissions. If you have done this sort of thing before, use the quick start.
3. Build the first configuration¶
The browser setup asks for a server name, a save name, a world, network settings and the first owner account. The first-time setup guide explains what each important choice means and how to bring an existing world.
You are finished when all four of these are true:
- You can sign in to SSUI again.
- Stationeers reaches a joinable running state.
- A player can connect through the network you intend to use.
- SSUI creates and can download a backup after an autosave.
That last item is not optional busywork. A backup system first tested after the disaster is just a confidence-themed folder.
After the first launch¶
- Learn the safe save, stop and update sequence in server operations.
- Understand archive retention and restores in backups.
- Add other administrators and restrict their permissions in access and HTTPS.
- Set up the Discord hub or mods when the basic server is stable.
If something fails, start with troubleshooting. If the logs are mostly hieroglyphics, create a support package and ask in the SSUI Discord.