Windrose Dedicated Server Status
Status in one line: Windrose dedicated servers are live. The Early Access build ships real server support, hosting providers (including us) run the official dedicated build today, and crews join through invite codes rather than IP addresses. This page tracks what works now, how the join model differs from other survival games, and where the rough edges still are.
Status as of June 9, 2026
- Dedicated servers: live in Early Access. Both self-hosted and rented servers run the official dedicated build.
- Join model: invite codes only. There is no public IP:port to type and no in-game server browser.
- Persistence: a dedicated server keeps your ship, island bases, and crew progression online 24/7, independent of any one player's PC.
- Still thin: official admin and config documentation remains limited, and the config surface is still evolving with Early Access patches.
How joining a Windrose dedicated server works
Windrose skips the classic IP:port flow entirely. The server generates an invite code, and crew members enter that code in-game to join. The practical consequences:
- No port forwarding for players. Joining never touches router or firewall settings on the player side.
- No server browser. Your world is private by default; only people with the code can join, which suits Windrose's small-crew co-op design.
- The code is the address. On a managed server the panel shows the current invite code as soon as the server is up; share it once and the crew is in.
Self-hosted vs rented
| Category | Self-hosted | Rented (managed) |
|---|---|---|
| Server build | Official dedicated build, run and patched by you | Same official build, updated for you after each Steam patch |
| Uptime | Tied to your machine being on | 24/7, world persists while everyone is offline |
| Updates | Manual; mismatched versions block joins until you patch | Kept in step with the current Steam build automatically |
| Backups | Your responsibility | Automatic, with restores from the panel |
| Existing worlds | Local save on disk | Upload your existing save from the panel and continue the same world |
The one issue every crew hits: version mismatch
Windrose patches frequently in Early Access, and the client and server must be on the same Steam build to connect. After a game update, players who have patched cannot join a server that has not (and vice versa), which usually looks like a failed join or a kick back to the menu rather than a clear error. If your crew suddenly cannot connect on patch day, check versions first: the full walkthrough is in client/server version mismatch after a Steam update. Related join problems are covered in host/join errors and kicked-to-menu fixes, and slow or hanging world loads in stuck on loading screen and world load crashes.
What's still evolving
- Official admin tooling. Config and admin documentation from the developers is still sparse; expect the option surface to grow through Early Access.
- Patch cadence. Frequent updates mean version matching matters more than in most survival games; plan crew sessions for after everyone has patched.
- Feature growth. Server-side features are being added as Early Access progresses; we update this page when the hosting workflow changes.
Want a Windrose world that is always online? Rent a Windrose dedicated server: the panel shows your invite code, keeps the server on the current Steam build, takes automatic backups, and lets you upload an existing save so your crew continues the same world.