Windrose is an Early Access UE5 survival game. I want to set expectations upfront: performance is going to be imperfect, and some of that is simply out of your control. That said, there are real things you can do to make it better, and understanding where the bottlenecks are helps a lot.
The 4-Player Sweet Spot
The developers at Kraken Express officially support up to 10 players but recommend 4 for the best experience. They've acknowledged that late-game performance degrades with larger groups, particularly once players have built extensive bases and explored significant portions of the map.
This isn't a server hardware limitation. It's the game engine and the way Windrose handles world state. More players means more loaded chunks, more entities being simulated, more network traffic. At 4 players, the server comfortably keeps up. At 8-10, you'll notice the difference – especially in late-game worlds with lots of construction.
Four players is genuinely the sweet spot right now. If you're planning a larger group, it'll work, but temper your expectations for late-game sessions.
It's Probably Not Your Server's Hardware
All LOW.MS Windrose plans ship with 10 GB RAM regardless of player count. That's more than the developer-recommended 16 GB ceiling for 10 players when you factor in that our infrastructure handles the OS overhead separately.
The point being – if you're experiencing lag on a LOW.MS server, the server's RAM or CPU allocation is almost certainly not the problem. The bottleneck is the game itself. Windrose is in Early Access, and optimization is an ongoing process.
You can verify this yourself. In the LOW.MS Control Panel at control.low.ms, click Current Activity & Stats in the sidebar. This shows real-time RAM and CPU usage for your server. If RAM usage is well below the limit and CPU isn't pegged, your performance issues are engine-side, not resource-side.
Server-Side vs. Client-Side Lag
When things feel laggy, the first question is: is it everyone, or just you?
Ask your players. If everyone is experiencing the same stuttering or rubber-banding at the same time, that's server-side. The server is struggling to keep up with the simulation tick rate.
If it's only you, it's client-side. Your PC's hardware, your internet connection, or something between you and the EOS relay is the culprit. Windrose uses P2P relay networking – traditional ping measurements don't map directly because traffic goes through a relay rather than a direct connection.
Configuration Tweaks
Some settings in the server config directly affect performance load. You can edit these through Configuration Files in the panel.
Co-op scaling modifiers increase enemy count and difficulty based on connected players. Lower values mean fewer entities for the server to simulate. If you're running a larger group and noticing performance issues during combat encounters, dialing these back can help.
Reducing the maximum player cap below 10 – even if you don't expect to hit it – prevents surprise guests from pushing the server harder than intended. Set it to your actual expected group size.
The settings blog post has specific recommendations for each config value.
Keep the Server Updated
This matters more for an EA game than for a finished title. Every Windrose patch potentially includes server-side performance improvements, memory leak fixes, and optimization work.
Go to Steam Update in the panel regularly. After a game update drops, update your server promptly. Not just for new features – sometimes a patch cuts server memory usage by 20% or fixes a simulation bug that was tanking tick rate.
Restart Periodically
I know this sounds like the IT cliche. But memory leaks are real, and they're especially common in Early Access games.
Windrose's server process gradually consumes more RAM over extended uptime. After 24-48 hours of continuous operation, you might notice performance degradation that wasn't there on day one. A restart clears that accumulated bloat.
You can automate this with Scheduled Tasks in the panel. Set a daily restart during off-hours – maybe 4 AM or whenever your group isn't playing. The server saves the world on shutdown, so no progress is lost.
Reduce World Complexity
This one's on your players. Dense building clusters – lots of structures, crafting stations, storage containers packed into a small area – create hotspots that the server has to work harder to simulate. Spreading builds out across the map distributes the load.
It's not about telling people they can't build. It's about awareness. If your group's mega-base is causing frame drops every time someone enters the area, that's the world state getting expensive to simulate. Smaller, distributed outposts will perform better than one enormous compound.
Where This Goes From Here
Performance will improve. It always does with EA survival games – Valheim went through it, Enshrouded went through it, Palworld definitely went through it. Early builds run hot, optimization patches roll in over months, and eventually the server runs significantly leaner than it did at launch.
Windrose launched on April 14, 2026. We're in the earliest days. If performance isn't perfect right now, that's expected. Keep your server updated, restart it regularly, and keep an eye on Current Activity & Stats to understand what your server is actually doing. The general troubleshooting guide covers additional diagnostic steps if you hit specific issues.