StarRupture, the first-person factory-automation survival game from Creepy Jar (the studio behind Green Hell), launched into Steam Early Access on January 6, 2026. It dropped players onto the hostile planet Arcadia-7 to build, automate, and survive — and it pulled roughly 28,000 concurrent players at launch with a low-to-mid-80s positive rating. One of the most common questions since launch has been simple: does StarRupture have a real dedicated server? The honest answer is yes, but with an important asterisk: the dedicated server is officially an experimental feature, and a lot of the config detail floating around the web is community-reported rather than documented by Creepy Jar. This guide separates what is confirmed from what is not, so you can set up a server that actually works and avoid copying settings that may be wrong.
Three ways to play StarRupture together
Before touching a server, it’s worth understanding that StarRupture gives you three distinct multiplayer paths. The official Steam description puts it plainly: you can explore Arcadia-7 solo, host a co-op session for up to four players yourself, or join friends on a dedicated server that is “currently available as an experimental feature.” Each path has trade-offs.
- Host-from-game co-op (default, most stable). One player creates the world and owns the save. Up to three others join via Steam invites. The host can set privacy to “Invite Only” or “Friends Only.” The catch: when the host is offline, no one can play that world. This is the path most players actually use today.
- Dedicated server (experimental). A separate Steam tool or SteamCMD application that keeps a persistent world online independently of any single player. This is what the rest of the guide covers.
- SaveSync — a separate third-party Steam app (App ID 3832010). This is not a built-in StarRupture feature. It syncs and backs up the co-op save between players so that anyone in the group can host the next session, keeping a world alive without depending on one host. It only runs while StarRupture itself is closed, and it is also in Early Access (targeting roughly Q4 2026). Some secondary guides incorrectly describe SaveSync as an in-game feature — the Steam store listing confirms it is a standalone application.
Throughout all of these, the co-op cap is four players (host plus three). Online co-op only; an internet connection is required for multiplayer, and there is no documented LAN mode. The four-player limit is described as fixed for stability — keep that number in mind, because you’ll see claims later that you can push it higher.
Game and server identity at a glance
| Field | Value |
|---|---|
| Game title | StarRupture |
| Steam App ID (game) | 1631270 |
| Developer / Publisher | Creepy Jar (self-published) |
| Status | Early Access (launched Jan 6, 2026; EA exit planned ~2027) |
| Co-op cap | Up to 4 players (online only) |
| Dedicated server App ID (SteamCMD) | 3809400 |
| Server OS | Windows 10/11 (64-bit) only |
| Server executable | StarRuptureServerEOS.exe |
What’s officially confirmed about the dedicated server
The following facts come from Creepy Jar’s official setup guide, linked from the pinned Steam thread “Setting up a SR Dedicated Server (Experimental feature).” Treat these as the reliable foundation.
- Status: Officially labeled an “Experimental Feature” as of the January 2026 Early Access launch. It works, but expect to handle port forwarding and firewall rules manually, edit a batch file, and tolerate the occasional bug.
- Operating system: Windows 10/11 (64-bit) only. There is no native Linux server documented by Creepy Jar. Community Docker images exist but are unofficial (more on those below).
- Server networking: The server uses Epic Online Services (EOS), which is why the executable is named
StarRuptureServerEOS.exe. - Same-Steam-account limitation: You cannot run the server tool and the game at the same time on two PCs under the same Steam account if the server is launched from the Steam client. For a genuinely separate, always-on box, install via SteamCMD with anonymous login instead.
Installing the server: two confirmed methods
Method A — Steam library tool
The simplest route is through the Steam client. Filter your Steam library by “Games + Tools,” then find and install “StarRupture Dedicated Server (Experimental).” This is convenient for hosting on a spare local machine, but remember the same-account limitation above if you also want to play on that account.
Method B — SteamCMD (recommended for a separate box)
For a dedicated machine or rented server, SteamCMD is the better path. The confirmed dedicated-server App ID is 3809400 (verified via SteamDB). Install it anonymously:
steamcmd.exe +force_install_dir C:\StarRuptureServer +login anonymous +app_update 3809400 validate +quitOne historical caveat: at launch, the Steam thread reported “subscription” / anonymous-login errors while Creepy Jar was still pushing the server files live. Anonymous login should now work, but if you hit an error, that’s the known cause — verify the files are available rather than assuming your command is wrong.
Launching the server
The server launches through a batch file, SRServerWithLog.bat, which calls the executable with logging enabled and a port argument. The confirmed launch form looks like this:
start .\StarRuptureServerEOS.exe -Log -port=7777The game port is 7777, set with the -port= argument — this is the one port value that is confirmed by the official launch argument itself. The -Log flag keeps a running log so you can diagnose crashes, which is worth keeping enabled given the experimental status. Make sure your firewall and router forward the port you choose (UDP/TCP per your network setup) so players can reach the server.
The config file: what’s reported but NOT confirmed
This is the section where you need to be skeptical. The official Creepy Jar guide documents only the command-line / batch launch above. It does not document any config-file syntax. Everything below comes from secondary host-vendor guides, and those sources contradict each other. Verify against your actual server install before relying on any of it.
- Config file name is disputed. Most host guides cite a JSON-style
DSSettings.txtsitting next to the executable. But at least one guide claims configuration is done through aGame.inifile instead. These cannot both be authoritative — check which file (if either) your install actually creates. - Query port 27015 (UDP) for Steam server query/browser is plausible because it’s the standard, but it is not in the official guide.
- EOS ports 27031–27036 (UDP) are cited by a single source only.
- An 8-player override (
MaxPlayers=8) is claimed by one guide, which also notes it causes desync and crashes. The game is officially capped at 4 — treat 4 as the real, safe limit and do not expect a higher count to be stable. - Save-management keys like
SaveGameInterval,StartNewGame, andLoadSavedGameare secondary-source only.
For transparency, here is the community-reported DSSettings.txt example that circulates across host guides. Use it as a starting hypothesis to test, not as documented gospel:
{
"SessionName": "MyServer",
"SaveGameInterval": "300",
"StartNewGame": "false",
"LoadSavedGame": "true",
"SaveGameName": "AutoSave0.sav",
"Port": 7777,
"QueryPort": 27015
}The single value in there that aligns with the official guide is the game port (7777). Everything else — the file name, the key names, the query port, the save keys — should be confirmed by inspecting what files your server actually generates on first launch. If your install produces a different file or different keys, trust the install over any blog (including the community examples here).
Managed and community hosting options
If you’d rather not babysit an experimental Windows tool, managed StarRupture hosting is already offered by several providers, and we run it too. If you want a ready-to-go box with the server files, ports, and updates handled for you, our StarRupture server hosting plans save you the manual batch-file and firewall work — and we keep configurations current as Creepy Jar formalizes the experimental tooling. For deeper step-by-step instructions tailored to our panel, see the StarRupture documentation.
On the community side, unofficial Docker images exist (for example under the Docker Hub names struppinet, nitje, and lancer1977). These imply Linux containerization despite the official Windows-only stance, so treat them strictly as community experiments — not supported, and not guaranteed to survive game updates.
Which path should you choose?
| Path | Best for | Trade-off |
|---|---|---|
| Host-from-game co-op | Small friend groups, casual play | World offline when host leaves; 4-player cap |
| Dedicated server (experimental) | Always-on persistent worlds | Windows-only, experimental, manual config |
| SaveSync app (3832010) | Rotating hosts without a server | Separate app; only runs when game is closed |
For most groups of four or fewer, host-from-game co-op or SaveSync covers the need without server overhead. Choose the dedicated server when you specifically want a world that stays online regardless of who is logged in — and accept that, for now, it’s an experimental tool that may change.
Frequently asked questions
Does StarRupture have a dedicated server?
Yes — but it is officially labeled an “experimental feature” as of the January 2026 Early Access launch. You can install it as a Steam library tool (“StarRupture Dedicated Server (Experimental)”) or via SteamCMD using App ID 3809400. Expect to do some manual port and batch-file setup.
What is the StarRupture dedicated server App ID and port?
The dedicated-server SteamCMD App ID is 3809400 (the base game is 1631270). The confirmed game port is 7777, set with -port=7777 when launching StarRuptureServerEOS.exe via the SRServerWithLog.bat batch file.
Can a StarRupture server hold more than 4 players?
Officially, no. StarRupture co-op is capped at 4 players for stability. One community guide claims an 8-player override is possible, but the same guide warns it causes desync and crashes. Treat 4 as the real limit.
Where is the StarRupture server config file?
This is unconfirmed. Creepy Jar’s official guide documents only the command-line launch, not a config file. Host-vendor guides disagree — most cite a JSON-style DSSettings.txt next to the executable, while at least one cites Game.ini. Verify against your actual install before trusting any specific file or key.
Can I run a StarRupture server on Linux?
There is no official Linux server. Creepy Jar documents Windows 10/11 (64-bit) only. Community Docker images exist on Docker Hub, but they are unofficial workarounds and aren’t supported.
What is SaveSync, and do I need it?
SaveSync is a separate Steam app (App ID 3832010), not a built-in StarRupture feature. It syncs co-op saves between players so anyone can host the next session without a dedicated server. It only runs while StarRupture is closed and is itself in Early Access. It’s the simplest no-server way to keep a shared world alive.
Ready to play?
Run your own StarRupture server with XGamingServer
Spin up an always-on StarRupture server your friends can join in minutes — no port-forwarding, no tech headaches.
