Pay for 10 months and use 12 months on all VDS products

Choose language
Türkçe Türkiye Azərbaycan Azərbaycan Dansk Danmark Deutsch Deutschland English United Kingdom Español España Filipino Pilipinas Français France Hrvatski Hrvatska Indonesia Indonesia Italiano Italia Kiswahili Tanzania Magyar Magyarország Nederlands Nederland Norsk Norge Oʻzbekcha Oʻzbekiston Polski Polska Português Portugal Português (BR) Brasil Română România Suomi Suomi Svenska Sverige Tiếng Việt Việt Nam Čeština Česko Ελληνικά Ελλάδα Русский Россия Українська Україна Қазақша Қазақстан اردو پاکستان العربية المملكة العربية السعودية فارسی ایران हिन्दी भारत বাংলা বাংলাদেশ ไทย ประเทศไทย 中文 中国 日本語 日本 한국어 대한민국

SIMULATION · PC

Space Engineers Game Server

Space Engineers load comes from physics, moving grids, piston and rotor systems, scripts, voxel changes, and persistent world data.

Space Engineers Server Plans

Choose processor infrastructure first, then compare price, memory, and storage resources.

Ryzen 9950X3D

AMD Ryzen 9 9950X3D

Space Engineers Recommended · 6 GB

€5.35 / month

vCPU
4 cores
RAM
6 GB
Storage
80 GB NVMe SSD
Processor
AMD Ryzen 9 9950X3D
Location
Turkey
More features
Traffic
Unlimited
Operating system
Linux/Windows
Order now

Space Engineers Recommended · 8 GB

€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
Order now

Space Engineers Performance · 10 GB

€9.82 / month

vCPU
6 cores
RAM
10 GB
Storage
120 GB NVMe SSD
Processor
AMD Ryzen 9 9950X3D
Location
Turkey
More features
Traffic
Unlimited
Operating system
Linux/Windows
Order now

Space Engineers Performance · 16 GB

€17.85 / month

vCPU
8 cores
RAM
16 GB
Storage
200 GB NVMe SSD
Processor
AMD Ryzen 9 9950X3D
Location
Turkey
More features
Traffic
Unlimited
Operating system
Linux/Windows
Order now
Xeon Platinum

Intel Xeon Platinum 8160

Space Engineers High Resource · 24 GB

€15.17 / month

vCPU
8 cores
RAM
24 GB
Storage
140 GB SSD
Processor
Intel Xeon Platinum 8160
Location
Turkey
More features
Traffic
Unlimited
Order now

Space Engineers High Resource · 32 GB

€20.53 / month

vCPU
8 cores
RAM
32 GB
Storage
160 GB SSD
Processor
Intel Xeon Platinum 8160
Location
Turkey
More features
Traffic
Unlimited
Order now
Resource selection

Choose Your Space Engineers Server Plan

Large connected grids, collisions, mechanical blocks, and programmable blocks can affect simulation speed; measure a busy base and fleet scenario.

Space Engineers Recommended · 6 GB

The first resource profile for a controlled launch and measurement baseline.

Processor
AMD Ryzen 9 9950X3D
vCPU
4
RAM
6 GB
Storage
80 GB NVMe SSD

Space Engineers Performance · 10 GB

A middle profile to assess as community and content workload grows.

Processor
AMD Ryzen 9 9950X3D
vCPU
6
RAM
10 GB
Storage
120 GB NVMe SSD

Space Engineers High Resource · 32 GB

A higher resource profile to compare when measured CPU, RAM or storage needs increase.

Processor
Intel Xeon Platinum 8160
vCPU
8
RAM
32 GB
Storage
160 GB SSD

Evaluate CPU, memory, and storage options against the expected game workload.

Player load

How player count affects resources

Separate planetary and space operations multiply active physics areas, while a shared battle or station project creates a local peak.

  • Single-core strength

    Measure processor peaks and game-loop response during a busy session.

  • RAM

    Track peak memory use together with growth headroom.

  • NVMe / 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
Player capacity varies with game version, add-ons, and world activity.
ScenarioResource effectCheck
Concurrent playersSeparate planetary and space operations multiply active physics areas, while a shared battle or station project creates a local peak.Measure a busy session
Game activityLarge connected grids, collisions, mechanical blocks, and programmable blocks can affect simulation speed; measure a busy base and fleet scenario.Repeat the peak scenario
World / save growthGrids, floating objects, and voxel edits expand the save; use simulation speed and save duration to guide maintenance.Track save and restore duration
CAPACITY ESTIMATE

Estimate Resources for Your Space Engineers Server

Estimate starting capacity from your player and world goals.

Define the workloadNo personal data is sent.
Simulation workload

Scripts, framework, database, and game-specific choices affect the estimated workload profile.

Expected growth margin

The result is a starting estimate. Reassess it using busy-session CPU, memory, and storage measurements after deployment.

Capacity summary

Estimated CPU, memory, storage, and a suitable resource profile appear here.

Mod / plugin level

Mods, plugins, and additional content

Workshop mods add block definitions and world data. Validate a copied save because opening with missing dependencies can remove grids or blocks.

Mod compatibility can vary by game and server-software release.

Administration

Administration and server settings

Manage PCU and object limits, cleanup, script permissions, encounters, and mod order around the community design.

Installation and management

After deployment, manage Space Engineers processes, version changes, and settings that require restarts in controlled maintenance windows.

Backups

Back up Space Engineers saves, configuration, and additional-content data as separate restore points before changes.

File access

Limit file access to Space Engineers configuration, logs, and managed content directories; stop the relevant process before replacing active files.

Frequently asked questions

Space Engineers

How should I compare plans for a large station and fleet?

Evaluate an established world with its grids, mechanical systems and a busy physics scenario rather than an empty world. Use simulation speed alongside CPU and memory usage to identify the resources needed.

How should we test a group spread across different planets?

Try both a shared-station session and one where the group operates grids in separate areas. Do not assume that the same number of players creates the same physics workload in both situations.

Should I load a save when a Workshop dependency is missing?

Preserve the working save and resolve the mod list and dependencies first. Test a copy and check that important grids remain intact before writing back to the live world.

Should I buy a larger plan as soon as simulation slows down?

Review grids, loose objects and script workload, and test any cleanup on a backed-up copy. If a measured CPU or memory limit remains, compare plans that address that need.

How should we choose PCU limits and script permissions?

Start with the experience you want for the community, then set object limits and script permissions accordingly. Record changes and test a busy session; do not assume unlimited construction or script capacity.

NEXT STEP

Choose Your Space Engineers Server Plan

Contact support for ordering details and special requirements.

Game Calculator — Run a lookup Review game plans