Best Windrose Server Hosting (2026): Invite Codes, Saves, and Early Access Checklist
Windrose does not use the normal “type an IP and port” hosting model. Crews join a managed dedicated world with an invite code, so the key comparison is whether the provider keeps the Windows server process, code, save, and client version in sync while the game remains in Early Access.
Supercraft’s S/M/L tiers are 4/8/12 GB RAM. Compare persistent-world behavior, restart and memory pressure, invite-code recovery, settings access, and update safety before committing to a long term.
The short version
| Join model | Invite-code joins; the normal customer flow is not a raw public IP:port connection. |
|---|---|
| Lifecycle | Early Access; client/server version parity and hotfix handling are first-class concerns. |
| Capacity signal | Supercraft tiers are 4, 8, and 12 GB RAM; long sessions and memory pressure matter. |
| World | Persistent pirate-survival world, crew progression, saves, and managed restarts are the product. |
| Operations | The source page lists Windows dedicated hosting, automatic backups/restarts, file/config access, and four regions. |
What actually matters when choosing Windrose hosting
Use these checks when comparing any provider. They are deliberately tied to this game’s server model, so a high slot number or generic “unlimited” badge cannot answer them for you.
1. Invite-code reliability
An invite-code game can fail without a port problem if the code is stale, hidden, or not regenerated after a restart.
Check: Ask where the code appears, how it survives restarts, and what the recovery path is when players are kicked to the menu.
2. Early Access version parity
Steam hotfixes can leave the client and Windows dedicated process on different builds.
Check: Confirm update timing, restart notices, version mismatch handling, and rollback limits.
3. RAM and long-session pressure
Persistent sessions can decay in performance if the process accumulates memory pressure over time.
Check: Compare 4/8/12 GB with session length, crew size, world age, and restart policy.
4. Save transfer and recovery
A pirate crew’s world and ship/base progress should remain recoverable after a hotfix or failed restart.
Check: Verify save backups, downloadable files, restore behavior, and safe transfer between worlds.
5. Settings and admin expectations
Invite-code access simplifies joining but does not automatically give you every admin command or world setting.
Check: Ask what settings JSON/config, console, admin, and multi-world controls are actually exposed.
6. Price during Early Access
A changing game and unusual connection model make flexibility and support more valuable than a low long-term prepay price.
Check: Compare monthly terms, region, backups, restarts, support, and upgrade behavior.
Green flags and red flags
Use these as questions for a provider, not as a substitute for testing the exact game build, map, mod list, or save.
Green flags
- The invite-code join/recovery path is documented.
- Windows server version and hotfix handling are explicit.
- Memory pressure and restart cadence are measured.
- Saves, settings, and backups can be recovered by the owner.
Red flags
- The provider gives a raw IP/port that is not the game’s primary join model.
- Early Access hotfixes are applied without a restart/backup plan.
- 4 GB is promised for every long session.
- The invite code disappears with no recovery instructions.
Where Supercraft fits the checklist
Supercraft is the operator behind the offer shown below, so this section is an affiliation disclosure as well as a comparison. The useful claim is limited to what the corresponding hosting page actually lists; verify unusual mods, platform mixes, or capacity assumptions before ordering.
Current Windrose hosting offer
These are the current plan facts collected from the canonical hosting page. Prices are loaded from WooCommerce at request time and adapt to the visitor’s store currency; no static price is embedded in the guide.
Small crew and shorter/light persistent sessions.
Growing crew and longer sessions with more world state.
Larger crew or the most headroom for persistent Early Access sessions.
The cards show Supercraft’s current plan structure for this game. They are included so you can compare a concrete offer against the checklist; they are not a claim that Supercraft is objectively the best provider for every group.
See the full Windrose server hosting pageWindrose hosting FAQ
How do Windrose dedicated servers work?
Windrose uses an invite-code join flow. The hosted server runs persistently and exposes the code through the managed panel/files rather than relying on players typing a normal public IP and port.
Which Windrose plan should I choose?
Use S for a small/light crew, M for longer or larger sessions, and L for the most persistent-world headroom. The 4/8/12 GB tiers are workload starting points while Early Access evolves.
Can I move or restore a Windrose world?
The provider should support save transfer and backups. Keep a downloadable copy of the world/settings and test a restore after a hotfix before deleting the source.
What happens after a Windrose Steam update?
The client and dedicated server must be on compatible builds. A managed host should restart safely, expose the current invite code, and provide a mismatch/recovery path.
Does Windrose need port forwarding?
The customer-facing join flow is invite-code based, so players generally do not port-forward a home router. Confirm the current official guide and host setup for any operational ports.
Keep researching
Sources used for this guide: Windrose official dedicated-server guide · Supercraft Windrose hosting page.