Core Keeper 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
SANDBOX · PC
Core Keeper Game Server
Core Keeper load follows explored underground area, mining edits, base automation, creatures, and persistent player progression.
Intel Xeon E5-2699 v4
Core Keeper 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
Core Keeper 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
Core Keeper 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
Core Keeper 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 Core Keeper Server Plan
Broad exploration, dense production systems, and boss encounters create different peaks; compare against a developed base rather than a new world.
Core Keeper 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
Core Keeper 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
Core Keeper 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 digging in separate directions expand world data faster, while a shared boss fight concentrates combat entities in one region.
-
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 digging in separate directions expand world data faster, while a shared boss fight concentrates combat entities in one region. | Measure a busy session |
| Game activity | Broad exploration, dense production systems, and boss encounters create different peaks; compare against a developed base rather than a new world. | Repeat the peak scenario |
| World / save growth | Mined areas, placed objects, and character progress expand the world file; track backup duration against exploration speed. | Track save and restore duration |
CAPACITY ESTIMATE
Estimate Resources for Your Core Keeper 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
Check game-release and multiplayer compatibility for community mods. Test save-affecting content against a world copy.
Mod compatibility can vary by game and server-software release.
Administration
Administration and server settings
Record world identity, access, player lists, save location, and mod versions as part of maintenance.
Installation and management
After deployment, manage Core Keeper processes, version changes, and settings that require restarts in controlled maintenance windows.
Backups
Back up Core Keeper saves, configuration, and additional-content data as separate restore points before changes.
File access
Limit file access to Core Keeper configuration, logs, and managed content directories; stop the relevant process before replacing active files.
Frequently asked questions
Core Keeper
Should I size a new group and an established base the same way?
Base your comparison on the actual base and production systems you intend to run. Observe exploration, a boss event and shared production separately before selecting CPU and memory resources.
What should we observe when players dig in different directions?
Track world-file growth alongside resource use during a busy exploration session. A short test with everyone at the same base is not enough to establish capacity for ongoing exploration.
Are community mods supplied ready to use?
Choosing resources does not confirm a mod installation service. Agree the intended mods, versions and installation responsibility first, and test world-changing content on a copy.
Is extra disk space enough when saves grow?
Separate space used by the world, backups and logs. Check CPU and memory limits in the same session as well; file capacity and processing workload are different requirements.
What should I prepare before opening the world in a new setup?
Record the world identifier, save location, mod versions and access settings. Keep the working copy until you have checked that the intended world loads and the required progress remains available.
NEXT STEP
Choose Your Core Keeper Server Plan
Contact support for ordering details and special requirements.