Icarus Server Requirements: RAM, CPU, Storage & Network
Icarus server load depends on whether you run a timed Prospect, persistent Outpost, or Open World, how much players build, the number of concurrent players, and any mods. Use the figures below as planning guidance, not as a guaranteed player-count formula.
Official baseline versus server sizing
The official Steam listing currently gives the game's client requirements: 16 GB RAM minimum, 32 GB recommended, and 70 GB available storage. Those figures are not a dedicated-server SLA. A server should be sized from observed CPU, memory, storage, and network peaks for the exact world and build.
Practical planning categories
| Workload | Starting approach | What to watch |
|---|---|---|
| Small Prospect group | Fast CPU, SSD storage, and a modest memory allocation with headroom. | CPU spikes during activity and mission transitions. |
| Persistent Outpost or Open World | More memory and NVMe headroom than a short session. | World growth, save times, and long-running memory use. |
| Large build or modded world | Test the exact mod set and increase resources from measured peaks. | AI, world simulation, save I/O, and plugin/mod errors. |
CPU, memory, and storage
- CPU: prioritize strong per-core performance, then add capacity for additional instances or workloads.
- Memory: leave operating-system and file-cache headroom; do not size from a single idle reading.
- Storage: SSD or NVMe is the sensible production choice for world saves, updates, and backups.
- Backups: store independent snapshots before updates, migrations, and large world changes.
Network and ports
There is no reliable universal “Mbps per player” formula for Icarus. Use a stable route with enough headroom, expose the ports required by the current dedicated-server build, and verify reachability from outside the server's network. The setup guide and your panel should be the source of truth for the current port mapping.
How to validate sizing
- Record the server build, mode, world, mods, and planned player count.
- Test the busiest expected activity: building, wildlife, weather, travel, and saves.
- Measure CPU, memory, disk latency, save duration, and network errors over a full session.
- Leave headroom for updates and concurrent backups.
- Repeat after adding a major mod or moving from a Prospect to an Open World.
Related Icarus guides
Host Icarus with Supercraft for managed storage, backups, and regional dedicated-server deployment.