Don't Starve Together Starter 2 GB
€2.23 / month
- vCPU
- 2 cores
- RAM
- 2 GB
- Storage
- 30 GB SSD
- Processor
- Intel Xeon E5-2699 V4
- Location
- Türkiye
More features
- Traffic
- Unlimited
- Operating system
- Selectable operating system
CO-OP · PC
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.
5 matching plans
€2.23 / month
€3.16 / month
€4.27 / month
€5.20 / month
€7.43 / month
Estimate starting capacity from your player and world goals.
Estimated CPU, memory, storage, and a suitable resource profile appear here.
Exploration, bases, and entities accumulate in long-running worlds; keep cluster, master, and caves saves in the same restore point.
The first resource profile for a controlled launch and measurement baseline.
A middle profile to assess as community and content workload grows.
An upper profile for re-measuring denser content and persistent-world growth.
Players split between surface and caves distribute work across shards; gathering at one boss area concentrates entities locally.
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 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 |
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.
Maintain cluster tokens, shard links, world generation, rollback count, and mod overrides as one consistent configuration.
After deployment, manage Don't Starve Together processes, version changes, and settings that require restarts in controlled maintenance windows.
Back up Don't Starve Together saves, configuration, and additional-content data as separate restore points before changes.
Limit file access to Don't Starve Together configuration, logs, and managed content directories; stop the relevant process before replacing active files.
Maintain cluster tokens, shard links, world generation, rollback count, and mod overrides as one consistent configuration.
Game-specific answers for capacity and operations decisions.
Caves can run as a separate shard, while world events, developed bases, and creature counts shape each shard differently.
Players split between surface and caves distribute work across shards; gathering at one boss area concentrates entities locally.
Workshop content includes client-required and server-only mods. Review mod settings and cluster dependencies before updates.
Exploration, bases, and entities accumulate in long-running worlds; keep cluster, master, and caves saves in the same restore point.
Maintain cluster tokens, shard links, world generation, rollback count, and mod overrides as one consistent configuration.
Contact support for ordering details and special requirements.