Eco Recommended
€7.14 / month
- vCPU
- 4 cores
- RAM
- 8 GB
- Storage
- 100 GB NVMe SSD
- Processor
- AMD Ryzen 9 9950X3D
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Linux/Windows
SIMULATION · PC
Eco continuously processes ecosystem simulation, player economy, law and citizenship data, production chains, and a changing world.
Choose a processor family
€7.14 / month
€12.49 / month
€17.85 / month
€23.20 / month
€15.17 / month
€20.53 / month
€30.34 / month
Economic transactions, production tables, environmental calculations, and developed settlements create sustained work unlike an empty world.
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.
Active citizens add trade, production, property, and governance records, not just connections; measure busy market periods.
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 | Active citizens add trade, production, property, and governance records, not just connections; measure busy market periods. | Measure a busy session |
| Game activity | Economic transactions, production tables, environmental calculations, and developed settlements create sustained work unlike an empty world. | Repeat the peak scenario |
| World / save growth | Citizen, property, contract, and world history expands databases and backups; track save duration over each cycle. | 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.
Server mods must match the data schema and game release. Test economy or world-data upgrades on a staging save.
Mod compatibility can vary by game and server-software release.
Record world goals, skill progression, economy, laws, administrator roles, and the mod list with change history.
After deployment, manage Eco processes, version changes, and settings that require restarts in controlled maintenance windows.
Back up Eco saves, configuration, and additional-content data as separate restore points before changes.
Limit file access to Eco configuration, logs, and managed content directories; stop the relevant process before replacing active files.
Describe production, trading and settlement plans alongside the expected community. When moving an established world, compare plans using resource use during a busy market session and the current data size.
Groups of the same size can generate different amounts of production, contracts and land activity. Measure a busy trading and production session, and assess CPU, memory and storage separately.
Keep a recovery copy of the world and economy data first. Test the game version, mod and data structure together separately; do not assume an update automatically preserves save compatibility.
Track data size, save duration and backup growth together. Separate unnecessary log accumulation, then compare capacity for the resource that reaches its limit during a busy session.
Agree the world goal, skill progression, economy rules and administrator roles with the community. If retaining the previous season, plan which data to archive and how it could be restored.
Contact support for ordering details and special requirements.