Raft Starter · 4 GB · Ryzen 9950X3D
€4.10 / month
- vCPU
- 2 cores
- RAM
- 4 GB
- Storage
- 60 GB NVMe SSD
- Processor
- AMD Ryzen 9 9950X3D
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Linux/Windows
CO-OP · PC
Raft server load changes with raft size, placed objects, automation, floating resources, and exploration stored in the save.
Choose a processor family
€4.10 / month
€5.35 / month
€7.13 / month
€9.81 / month
€3.03 / month
€4.10 / month
€4.99 / month
A large moving raft with production objects, nets, and animal areas creates different continuous work from a starter raft.
The first resource profile for a controlled launch and measurement baseline.
A middle profile to assess as community and content workload grows.
A higher resource profile to compare when measured CPU, RAM or storage needs increase.
Evaluate CPU, memory, and storage options against the expected game workload.
Players share one moving hub, so workload often concentrates there; island exploration and story locations create temporary peaks.
Measure processor peaks and game-loop response during a busy session.
Track peak memory use together with growth headroom.
Measure storage behaviour across saves, logs, and backups.
Measure actual mod, plugin, and script workload separately from extension count.
Track world size, active regions, and persistent-data growth together.
Evaluate concurrent-player distribution, activity, and content workload together.
| Scenario | Resource effect | Check |
|---|---|---|
| Concurrent players | Players share one moving hub, so workload often concentrates there; island exploration and story locations create temporary peaks. | Measure a busy session |
| Game activity | A large moving raft with production objects, nets, and animal areas creates different continuous work from a starter raft. | Repeat the peak scenario |
| World / save growth | Raft pieces, storage, and progression raise save value; take a distinct save before major redesigns. | Track save and restore duration |
Estimate starting capacity from your player and world goals.
Estimated CPU, memory, storage, and a suitable resource profile appear here.
The mod loader and mod versions must match participating clients. Test the result on a world copy before removing save-affecting content.
Mod compatibility can vary by game and server-software release.
Manage difficulty, password access, save slot, mod list, and maintenance notices together.
After deployment, manage Raft processes, version changes, and settings that require restarts in controlled maintenance windows.
Back up Raft saves, configuration, and additional-content data as separate restore points before changes.
Limit file access to Raft configuration, logs, and managed content directories; stop the relevant process before replacing active files.
Identify the platform, who hosts the session, where the world files are stored and the mod list. Use those details to confirm the installation method, files to transfer and management responsibilities before ordering.
Evaluate the developed raft with its production equipment, nets, storage and animal areas. Compare CPU and memory use during island exploration as well. Do not generalise from a starter raft with only a few pieces.
Keep the world file, mod loader and versions together. Load the changed copy and inspect important objects on the raft. Do not make the working world your first test of removing a mod that adds content.
Measure CPU and memory use during busy production, save duration and free disk space separately. After checking for a problem tied to one object or mod, compare packages against any remaining resource constraint.
Transfer the version, mod list and access method with the world file. Confirm in a copy that the new administrator can load the intended world and the group can join before retiring the old files.
Contact support for ordering details and special requirements.