Core Keeper 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
SANDBOX · PC
Core Keeper Game Server
Core Keeper load follows explored underground area, mining edits, base automation, creatures, and persistent player progression.
Game-ready plans
Xeon E5 — Intel Xeon E5-2699 V4
5 matching plans
Core Keeper Starter 4 GB
€3.16 / month
- vCPU
- 2 cores
- RAM
- 4 GB
- Storage
- 40 GB SSD
- Processor
- Intel Xeon E5-2699 V4
- Location
- Türkiye
More features
- Traffic
- Unlimited
- Operating system
- Selectable operating system
Core Keeper Recommended 6 GB
€4.27 / month
- vCPU
- 4 cores
- RAM
- 6 GB
- Storage
- 50 GB SSD
- Processor
- Intel Xeon E5-2699 V4
- Location
- Türkiye
More features
- Traffic
- Unlimited
- Operating system
- Selectable operating system
Core Keeper Recommended 8 GB
€5.20 / month
- vCPU
- 4 cores
- RAM
- 8 GB
- Storage
- 60 GB SSD
- Processor
- Intel Xeon E5-2699 V4
- Location
- Türkiye
More features
- Traffic
- Unlimited
- Operating system
- Selectable operating system
Core Keeper Performance
€7.43 / month
- vCPU
- 6 cores
- RAM
- 12 GB
- Storage
- 80 GB SSD
- Processor
- Intel Xeon E5-2699 V4
- Location
- Türkiye
More features
- Traffic
- Unlimited
- Operating system
- Selectable operating system
CAPACITY ESTIMATE
Model the Core Keeper workload
Estimate starting capacity from your player and world goals.
Capacity summary
Estimated CPU, memory, storage, and a suitable resource profile appear here.
PLAN SELECTION
Which plan should I start with?
Mined areas, placed objects, and character progress expand the world file; track backup duration against exploration speed.
Core Keeper Starter 2 GB
The first resource profile for a controlled launch and measurement baseline.
- RAM
- 2 GB
- Storage
- 30 GB SSD
Core Keeper Recommended 6 GB
A middle profile to assess as community and content workload grows.
- RAM
- 6 GB
- Storage
- 50 GB SSD
Core Keeper Performance
An upper profile for re-measuring denser content and persistent-world growth.
- RAM
- 12 GB
- Storage
- 80 GB SSD
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 |
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.
OPERATIONS GUIDE
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.
Server settings
Record world identity, access, player lists, save location, and mod versions as part of maintenance.
Frequently asked questions
Core Keeper
Game-specific answers for capacity and operations decisions.
Which workload should I watch first on a Core Keeper server?
Broad exploration, dense production systems, and boss encounters create different peaks; compare against a developed base rather than a new world.
How should I set a player target for Core Keeper?
Players digging in separate directions expand world data faster, while a shared boss fight concentrates combat entities in one region.
Do Core Keeper mods or plugins change capacity needs?
Check game-release and multiplayer compatibility for community mods. Test save-affecting content against a world copy.
When should I upgrade a Core Keeper server?
Mined areas, placed objects, and character progress expand the world file; track backup duration against exploration speed.
Which settings should a Core Keeper administrator review?
Record world identity, access, player lists, save location, and mod versions as part of maintenance.
NEXT STEP
Estimate the resource profile that fits your needs.
Contact support for ordering details and special requirements.