Don't Starve Together Starter · 2 GB
€2.14 / month
- vCPU
- 2 cores
- RAM
- 2 GB
- Storage
- 30 GB SSD
- Processor
- Intel Xeon E5-2699 v4
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Selectable operating system
CO-OP · PC
Don't Starve Together Game Server
Do not treat a Don't Starve Together server as one process: surface and cave shards, world entities, seasons, and mods need shard-aware observation.
Intel Xeon E5-2699 v4
Don't Starve Together Starter · 4 GB
€3.03 / month
- vCPU
- 2 cores
- RAM
- 4 GB
- Storage
- 40 GB SSD
- Processor
- Intel Xeon E5-2699 v4
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Selectable operating system
Don't Starve Together Recommended · 6 GB
€4.10 / month
- vCPU
- 4 cores
- RAM
- 6 GB
- Storage
- 50 GB SSD
- Processor
- Intel Xeon E5-2699 v4
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Selectable operating system
Don't Starve Together Recommended · 8 GB
€5 / month
- vCPU
- 4 cores
- RAM
- 8 GB
- Storage
- 60 GB SSD
- Processor
- Intel Xeon E5-2699 v4
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Selectable operating system
Don't Starve Together Performance
€7.14 / month
- vCPU
- 6 cores
- RAM
- 12 GB
- Storage
- 80 GB SSD
- Processor
- Intel Xeon E5-2699 v4
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Selectable operating system
Resource selection
Choose Your Don't Starve Together Server Plan
Caves can run as a separate shard, while world events, developed bases, and creature counts shape each shard differently.
Don't Starve Together Starter · 2 GB
The first resource profile for a controlled launch and measurement baseline.
- Processor
- Intel Xeon E5-2699 v4
- vCPU
- 2
- RAM
- 2 GB
- Storage
- 30 GB SSD
Don't Starve Together Recommended · 6 GB
A middle profile to assess as community and content workload grows.
- Processor
- Intel Xeon E5-2699 v4
- vCPU
- 4
- RAM
- 6 GB
- Storage
- 50 GB SSD
Don't Starve Together Performance
A higher resource profile to compare when measured CPU, RAM or storage needs increase.
- Processor
- Intel Xeon E5-2699 v4
- vCPU
- 6
- RAM
- 12 GB
- Storage
- 80 GB SSD
Evaluate CPU, memory, and storage options against the expected game workload.
Player load
How player count affects resources
Players split between surface and caves distribute work across shards; gathering at one boss area concentrates entities locally.
-
Processor workload
Measure processor peaks and game-loop response during a busy session.
-
RAM
Track peak memory use together with growth headroom.
-
SSD storage
Measure storage behaviour across saves, logs, and backups.
-
Mod and script density
Measure actual mod, plugin, and script workload separately from extension count.
-
World / map size
Track world size, active regions, and persistent-data growth together.
-
Player scenario
Evaluate concurrent-player distribution, activity, and content workload together.
Detailed planning notes
| Scenario | Resource effect | Check |
|---|---|---|
| Concurrent players | Players split between surface and caves distribute work across shards; gathering at one boss area concentrates entities locally. | Measure a busy session |
| Game activity | Caves can run as a separate shard, while world events, developed bases, and creature counts shape each shard differently. | Repeat the peak scenario |
| World / save growth | Exploration, bases, and entities accumulate in long-running worlds; keep cluster, master, and caves saves in the same restore point. | Track save and restore duration |
CAPACITY ESTIMATE
Estimate Resources for Your Don't Starve Together Server
Estimate starting capacity from your player and world goals.
Capacity summary
Estimated CPU, memory, storage, and a suitable resource profile appear here.
Mod / plugin level
Mods, plugins, and additional content
Workshop content includes client-required and server-only mods. Review mod settings and cluster dependencies before updates.
Mod compatibility can vary by game and server-software release.
Administration
Administration and server settings
Maintain cluster tokens, shard links, world generation, rollback count, and mod overrides as one consistent configuration.
Installation and management
After deployment, manage Don't Starve Together processes, version changes, and settings that require restarts in controlled maintenance windows.
Backups
Back up Don't Starve Together saves, configuration, and additional-content data as separate restore points before changes.
File access
Limit file access to Don't Starve Together configuration, logs, and managed content directories; stop the relevant process before replacing active files.
Frequently asked questions
Don't Starve Together
How should I plan resources for a world with caves?
Plan surface and cave use together rather than measuring an empty surface-only session. Compare CPU, memory and save requirements while both parts of the world are active.
Does it matter if the group splits between surface and caves?
Test that separately from a session where everyone gathers at one boss encounter. Player location can change the work handled by each shard, so total player count should not be the only measure.
What should I tell players before adding Workshop mods?
Identify the chosen mods’ client requirements and settings in advance. Test the server and player versions with a world copy, and confirm any installation service separately.
How should I organise backups for a long-running world?
Treat cluster, surface and cave saves as a consistent recovery point. Track the growth and restoration time of that set, not just the number of files stored on disk.
Which settings must survive a server rebuild?
Keep the cluster token, shard connections, world generation and mod settings securely. Test surface-to-cave travel and recovery of the previous save in the rebuilt setup before retiring the old copy.
NEXT STEP
Choose Your Don't Starve Together Server Plan
Contact support for ordering details and special requirements.