Keep your StarRupture factory standing between sessions with a dedicated co-op world in İstanbul, running the Windows server build under Wine.

Select from our wide range of optimized game servers. Each server is configured for maximum performance and comes with DDoS protection.





Compare recommended use, plan hardware and monthly prices.
| Plan | Recommended for | Hardware | Monthly price |
|---|---|---|---|
| Gold 8GB | 1–2 players, early-game baseAbove the 6 GB bare minimum the community lists; gets tight as the factory sprawls. | 4 vCore Ryzen 9950X · 8 GB DDR5 6000MHz · 70 GB NVMe SSD Samsung 990 PRO | ₺440.00/mo |
| Platinum 10GB | 2–3 players, early to mid gameLeaves room for Wine overhead plus a growing production network. | 4 vCore Ryzen 9950X · 10 GB DDR5 6000MHz · 100 GB NVMe SSD Samsung 990 PRO | ₺530.00/mo |
| Diamond 12GB | Full four-player co-op, mid gameFirst tier inside the 12–16 GB range the community recommends; our pick for a full group. | 4 vCore Ryzen 9950X · 12 GB DDR5 6000MHz · 110 GB NVMe SSD Samsung 990 PRO | ₺617.50/mo |
| Emerald 16GB | 4 players, large late-game factoryTop of the recommended range, with 6 vCores for heavy late-game simulation. | 6 vCore Ryzen 9950X · 16 GB DDR5 6000MHz · 120 GB NVMe SSD Samsung 990 PRO | ₺840.00/mo |
| Xtreme 32GB | More than a four-player world needs12 vCores and 32 GB exceed StarRupture's needs; only if you want maximum headroom. | 12 vCore Ryzen 9950X · 32 GB DDR5 6000MHz · 200 GB NVMe SSD Samsung 990 PRO | ₺1520.00/mo |
What it takes to run a Windows-only, still-experimental server build reliably on Linux.
Creepy Jar ships StarRuptureServerEOS only as a Win64 build; Wine translates its Windows calls on a Linux game server, so you get a dedicated world without renting a Windows machine.
SessionName, SaveGameInterval, StartNewGame, LoadSavedGame and SaveGameName decide which world boots and how often it autosaves, with no in-game menu clicks after every restart.
Admin and join passwords live in Password.json and PlayerPassword.json in the server root, so they survive restarts and stay put once the remote Manage Server interface is switched off.
Upload the .sav and .met files from your own game into the session folder, rename them to AutoSave0, and carry an existing base onto the dedicated server intact.
Production lines, resource processing and defense against alien hordes all add simulation work; Ryzen 9 9950X cores and DDR5 give the server room as your industrial network grows.
The dedicated server is still considered experimental, so take a manual backup of SaveGames and your password files before each update while automatic backups keep running.
For ₺440.00 ($11.00) a month, TheCrewHost gives you a StarRupture dedicated server on a Ryzen 9 9950X with NVMe storage, and 5 plans scale from 8 GB to 32 GB of DDR5 as your factory grows. StarRupture is Creepy Jar's first-person base-building and factory game, and its dedicated server ships only for Windows, so this edition runs it on Linux through Wine. You control saves through DSSettings.txt and keep admin and join passwords in Password.json and PlayerPassword.json. Hosted in İstanbul, it gives co-op groups in Türkiye and nearby regions a low-latency home base that no longer depends on the host's PC staying on.
StarRupture is a first-person open-world game from Creepy Jar, the studio behind Green Hell, that entered Early Access in January 2026. On a planet reshaped by recurring cataclysms, you extract and process resources, build a complex industrial system and defend your base against hordes of alien creatures. The Steam page pitches it as a solo game or a co-op experience for a group of up to four friends.
The dedicated server is a separate Steam app, but it only exists as a Windows build: StarRuptureServerEOS-Win64-Shipping.exe. With no native Linux server, this edition runs it under Wine, the compatibility layer that translates Windows program calls for Linux. Players notice no difference; on the server side, expect the first boot to take longer while the Wine environment is prepared, and memory use to sit a little above what a native server would need.
Server logs go to StarRupture/Saved/Logs/StarRupture.log. Community resources are open about the server software still being experimental, which makes backing up before updates a requirement here rather than a nice habit.
Community hosting notes list 6 GB as the bare minimum for a StarRupture server and 12–16 GB or more as the recommended range. That is why our plans start at 8 GB: Gold 8GB sits above the floor and covers the extra load Wine brings, but it gets tight once a late-game factory sprawls.
What grows memory is less the player count than the world itself. Explored terrain, placed structures, production chains and the enemies active during a defense all add objects the server has to track. When a group of four reaches mid-game, Diamond 12GB enters the recommended range; for a big late-game industrial network, Emerald 16GB is the top of that range and its 6 vCores leave extra CPU for the simulation.
Xtreme 32GB plainly exceeds what a four-player co-op world needs, and it is better to say so than to upsell it. On disk, the community suggests 40 GB or more; the 70 GB of NVMe on Gold comfortably holds the server files, the Wine environment and a history of saves.
DSSettings.txt is a small JSON file in the server root that decides which world loads. SessionName names the save session and allows up to 20 characters, SaveGameInterval is the autosave interval in seconds (300 means five minutes), and SaveGameName is the file to load, usually AutoSave0.sav. Always edit it with the server stopped.
To create a new world, set StartNewGame to true and LoadSavedGame to false, then start the server. Once it is up, join, open the ESC menu and press Save; the game writes the save into a folder named after your session under StarRupture/Saved/SaveGames. Then stop the server and flip both values. Leaving StartNewGame on is the classic mistake: the next boot generates a fresh world over your save.
To move an existing world over, find the saves in your game client's Steam userdata folder, upload the .sav and .met files into a folder named exactly like your session, and rename them to AutoSave0. Confirm LoadSavedGame is true and StartNewGame is false before you start the server.
In early 2026, community researchers disclosed a serious flaw in StarRupture dedicated servers whose Remote Control web interface is reachable over TCP. Without any authentication, an attacker could change the admin and join passwords, tamper with save files or crash the server process. It affects the game server, not the machine underneath, but that is still enough to lose your world.
The recommended mitigation is two launch parameters, -RCWebControlDisable and -RCWebInterfaceDisable, which switch the Remote Control interface off entirely, with the game port exposed over UDP only. The trade-off is that the in-game Manage Server screen stops working. That is exactly why this setup manages saves through DSSettings.txt and passwords through Password.json and PlayerPassword.json, which also has the advantage of persisting across restarts.
Check that both parameters appear in the startup line shown in your panel. If you do not see them, open a support ticket and our team will go over the server with you.
Players connect with the public IP address and port shown in your panel; community notes say joining over a LAN address does not work for this game. If you set a join password through PlayerPassword.json, players need it too. Without one, anyone who knows your IP and port can walk in, so create that file unless you want an open world.
The most common problem is a server that loads no save at all. With the Remote Control interface disabled, a missing or malformed DSSettings.txt leaves the server unable to open your world, so check the quotes and commas in the JSON. If you created the file on Windows and uploaded it, make sure it was not accidentally saved as DSSettings.txt.txt.
The other is a version mismatch: when the game updates, the server has to update too or players cannot join. If anything misbehaves after a patch, StarRupture.log is the first place to look. The İstanbul location keeps latency low for crews in Türkiye, so nobody lags behind while an alien horde hits the base.
Gold 8GB handles one or two players early on; for a four-player group and a growing factory, choose Diamond 12GB or Emerald 16GB from the recommended range.
After payment the Windows server files download automatically; the first boot takes longer while Wine prepares its environment, so wait for the console to report the server is up.
Generate admin and join passwords with the community StarRupture Utilities tool and upload the output as Password.json and PlayerPassword.json in the server root.
For a new world, boot with StartNewGame true and LoadSavedGame false, join and save, then flip both; for an existing save, place it as AutoSave0 in the session folder.
Confirm the startup command in your panel includes -RCWebControlDisable and -RCWebInterfaceDisable; if either is missing, contact our support team.
Share the public IP, port and join password with your friends, and pick up the base right where you left it.
Common questions about StarRupture dedicated servers: Wine, passwords, saves and security.
Our İstanbul datacenter runs on Ryzen 9 hardware, delivering low latency to players in Türkiye and good connectivity to Europe, the Middle East and the Caucasus.
Turkey
Everything your project needs — from game servers to VPS, dedicated servers, web hosting and Discord bot hosting.
Connect with our community of gamers and developers
Get instant support, share experiences, and stay updated with the latest news