Windrose server hosting
Windrose server hosting with CFTools Architect runs the dedicated server on a machine you control. Windrose is a newer pirate survival game, so the dedicated server and its patches are still moving. Architect installs it, applies updates, edits configuration, stores backups, restarts, recovers from crashes, and can wipe when the crew wants a new world. Mod management is not a Windrose feature in Architect. CFTools Cloud does not administer Windrose.
Runs on a Windows or Linux machine you control.
Hosting highlights
A dedicated server the crew can rely on
Deploy Windrose to a Windows or Linux host that stays online. Sailors join that machine. Architect does not sell Windrose game slots.
Updates while the game is still moving
New titles patch often. Architect can update the Windrose dedicated server and start it again so the crew is not waiting on one person with the install files.
Backups before the next patch
Keep a backup from before each Windrose update. If a new build will not load the old world, you still have the previous copy on the host.
Configuration you can hand to a mate
Edit Windrose server configuration in Manager. The settings are on the server record, so they survive a staff change and a rebuild of the machine.
Restarts and a fresh world
Schedule restarts so the process does not sit in a bad state. Automatic wipes are supported when the crew agrees to start the world over.
Metrics on a new dedicated server
Watch hardware and game-server metrics after the first busy evening. Crash recovery restarts Windrose if the process dies while nobody is watching the console.
How to self-host Windrose
Install Architect Agent on the machine you want sailors to join, deploy Windrose, open the game port, and enable backups before the first long session. Webhooks report stops and starts. RBAC lets a second admin restart the server without the full host login.
Windrose caveats
Mod management is not enabled for Windrose. CFTools Cloud has no Windrose RCon admin tool. Because the game is newer, treat every major update as something that deserves a backup first. Architect automates the dedicated server. It does not change what the game itself requires to boot.
Wipes are a choice, backups are the safety net
Automatic wipe cycles clear the world when you ask them to. They are the wrong tool for a crash. Use backups to recover, and use a wipe only when the crew wants a new start.
What you need to host Windrose
Provide a computer that stays on. Architect installs and maintains the dedicated server.
- A Windows or Linux VPS or always-on PC
- Disk for the world and for backups
- Architect Agent installed on that host
- The game port open for players
- A backup before each major game update
CFTools Architect features for Windrose
- Automated server deployment
- Automatic updates
- Configuration management
- Automatic restarts
- Backup automation
- Detect and recover from crashes
- Automate server wipe cycles
- WebHooks for every server state and event
- RBAC - Grant others easily limited or full access
- All servers easily visible on one unified dashboard
- Hardware metrics
- Game server metrics