How to Host a Windrose Dedicated Server

Darius N.
4.9

510+ Satisfied Customers

Windrose supports solo and co-op play (up to 8 players) and requires an internet connection to play - there’s no split-screen or local mode.

There are two ways to get a Windrose dedicated server. You can run one yourself on a Windows machine using SteamCMD, or you can use a managed hosting provider that handles the infrastructure. Here is what each path actually involves.

Server Hardware vs Client Hardware

Before getting into specs, a note on terminology: this guide talks about dedicated server hardware, not the hardware you need to play the Windrose client. Those two numbers are often mixed up in hosting comparisons and AI summaries. The game client renders the world and simulates physics locally on your PC. The dedicated server holds the world state and coordinates connected players. The two have different minimums and scale differently.

One Important Note Before You Start

Windrose’s dedicated server is currently Windows-only. The developers have confirmed there’s no Linux binary yet. Every Linux-based host, including WinterNode, runs the Windows server binary through a compatibility layer. That’s the industry norm for Windows-only titles. The question worth asking a host isn’t whether they use compatibility, it’s how quickly they match Windrose client updates, because version mismatches prevent players from connecting.

Which Path Is Right for You?

Self-Hosted (Windows PC)WinterNode Hosting
CostFree (hardware + electricity)From $11.94/mo (6GB)
Setup time30-60 minutesUnder 60 seconds
Windows requiredYes - your PC or a dedicated Windows machineHandled by the host
UptimeOnly when your machine is on24/7
BackupsManualAutomatic
UpdatesManual (re-run SteamCMD)One-click or automatic
MaintenanceAll on youHandled by the provider

Self-hosting makes sense if you have a spare Windows machine, your group plays on a consistent schedule where the host is always online, and you don’t mind managing updates yourself. Managed hosting makes sense if you want the server running 24/7 without tying up your gaming PC, or if the idea of configuring SteamCMD and troubleshooting Windows firewall rules sounds like work you’d rather skip.

Self-Hosted Setup: Running Windrose on Your Own Windows PC

Dedicated Server Hardware Requirements

These are the dedicated server specs, separate from the Windrose game client. If you’re running both on the same PC, you’ll need to add the client’s own requirements on top (covered below).

PlayersServer RAMServer CPU
28 GB2 cores, 3.2 GHz (Xeon Scalable class)
412 GB2 cores, 3.2 GHz
1016 GB2 cores, 3.2 GHz

Storage: 35 GB SSD minimum for the server installation.

If you’re running the server and the game client on the same machine, add the game’s own RAM requirements on top. The developers recommend 24 GB total for a combined client and server setup.

Warning

Running both the game client and the dedicated server on the same PC is workable for solo or small groups, but the performance ceiling is lower. If you plan to have four players while also playing on the host machine, a dedicated machine (or managed hosting) is a better fit.

Installing the Windrose Dedicated Server

Windrose’s dedicated server downloads via SteamCMD using a separate app ID from the game itself. No paid Steam account is required - the server downloads anonymously.

First, download SteamCMD from Valve’s developer site if you don’t have it. Then run the following in SteamCMD to install the Windrose server:

force_install_dir "C:\Game_Servers\Windrose_Server"
login anonymous
app_update 4129620 validate
quit

App ID 4129620 is the Windrose Dedicated Server. The game client is a different app (ID 3041230). Once the download completes, your server files are in whatever directory you specified with force_install_dir.

Starting the Server

Inside your server directory, you’ll find two startup options:

  • StartServerForeground.bat - Recommended. Opens a command window that shows live server logs. You can see connections, errors, and server status as they happen.
  • WindroseServer.exe - Runs the server as a background process. No visible log window - you’d need to close it via Task Manager.

Run StartServerForeground.bat unless you have a specific reason to run headless.

Configuration Files

Windrose uses two JSON files for server configuration.

ServerDescription.json lives in the server’s root folder and handles common server settings:

  • InviteCode - a case-sensitive code (6+ characters) that players use to join your server. Set this to something you can share with your group.
  • IsPasswordProtected - set to true if you want an additional password layer beyond the invite code.
  • MaxPlayerCount - up to 8. The developers recommend 4 for best performance.
  • WorldIslandId - must match the ID in WorldDescription.json.

WorldDescription.json lives deeper in the save path and handles world-specific settings including difficulty presets (Easy, Medium, Hard) and custom gameplay parameters.

Info

Always stop the server before editing config files. Windrose writes server state to disk on shutdown, and changes made while the server is running may be overwritten. Stop, edit, save, then restart.

Save File Location

Windrose’s dedicated server saves world data at:

WindroseServer\R5\Saved\SaveProfiles\Default\RocksDB\

Back up this directory regularly. RocksDB is a persistent key-value store - it isn’t a single file you can quickly copy and restore, so a proper backup process matters. Copy the entire RocksDB folder.

Networking: UPnP and Port Forwarding

Windrose uses NAT punch-through via UPnP for player connections. If your router has UPnP enabled (most consumer routers do by default), players can connect using the invite code without any manual port forwarding on your end.

If UPnP is disabled on your router, you’ll need to configure manual port forwarding. Check the official Windrose dedicated server guide for the specific ports to forward, as these may change as the game updates.

Keeping the Server Updated

When Windrose updates, your dedicated server needs to match the game client version. Version mismatches prevent players from connecting. To update:

login anonymous
app_update 4129620 validate
quit

Re-run this in SteamCMD whenever Windrose releases an update. During Early Access, expect updates frequently. Server binaries change alongside client updates, so keep your install tooling current.

Managed Hosting: Getting a Windrose Server on WinterNode

If the SteamCMD setup process sounds like more infrastructure work than you signed up for, managed hosting handles all of it.

WinterNode runs Windrose servers on Linux infrastructure through a compatibility layer for the Windows-only server binary. We patch our server image the same day Windrose ships a client update, so your server stays aligned with the game version your crew is playing, no lag between client patch and server update.

The setup process:

  1. Pick your RAM tier on the game server page - 8GB for two players, 12GB for four, 16GB for six to eight
  2. Select the data center closest to your group
  3. Your server is live in seconds

From the Game Control Panel, you can manage your invite code, server settings, file access, and backups without touching a command line.

What’s included on every WinterNode Windrose server:

  • Automatic backups every 12 hours with 45-day retention
  • DDoS protection
  • NVMe SSD storage
  • No CPU limits - your server uses what it needs, no throttling
  • Access to server files via the file manager or SFTP

For initial configuration - setting your invite code, adjusting player count, and editing your world settings - the help center has task guides at help.winternode.com. Those cover the specific control panel steps so this article doesn’t have to repeat them.

Get your Windrose server →

Windrose Early Access: What to Expect

Windrose is in Early Access. That means the game will change, the server software will change, and some features that exist in other survival games aren’t in Windrose yet.

A few things worth knowing before you start:

No mod support currently. Windrose has no modding framework in Early Access. Don’t expect Steam Workshop integration or third-party mods - that may come during development but doesn’t exist now.

Co-op only, no PvP. The game is designed around cooperative play. There are no PvP mechanics.

Online-only. Windrose requires an internet connection to play. There’s no offline or LAN mode.

Server and game versions must match. Keep your dedicated server updated alongside the game. If you’re self-hosting, check for server updates when the game client updates.

Getting Help

For detailed configuration steps - changing your invite code, adjusting difficulty settings, managing your world - our help center covers those in task-specific guides once you have a server running.

Questions before you get started? Reach out via ticket or Discord. Our support team is available and familiar with the game.


For a full comparison of Windrose hosting options, see our Windrose hosting comparison. For RAM sizing guidance by player count, the Windrose RAM guide breaks down exactly what to expect as your world grows.

Frequently Asked Questions

Use app ID 4129620. The game client is app ID 3041230 - the server app is separate and downloads anonymously at no cost.

No. As of Early Access launch, Windrose's dedicated server is Windows-only. There is no official Linux binary. Linux-based hosts including WinterNode run the Windows server binary through a compatibility layer, with same-day update tracking to keep versions aligned with Windrose client patches.

Not if your router supports UPnP. Windrose uses NAT punch-through via UPnP for player connections. If UPnP is disabled on your router, you may need to manually configure port forwarding - consult the Windrose dedicated server guide on playwindrose.com for details.

Save files are stored at WindroseServer\R5\Saved\SaveProfiles\Default\RocksDB\ relative to your server installation directory.

Up to 8 players. The developers recommend 4 as the sweet spot for performance. The player limit is configured in ServerDescription.json via the MaxPlayerCount field.