RedM Starter
€4.10 / month
- vCPU
- 2 cores
- RAM
- 4 GB
- Storage
- 60 GB NVMe SSD
- Processor
- AMD Ryzen 9 9950X3D
- Location
- Turkey
More features
- Traffic
- Unlimited
- Operating system
- Linux/Windows
ROLE-PLAYING · PC
A RedM server combines framework events, persistent characters, horse and vehicle entities, custom areas, and script behaviour into one capacity profile.
€4.10 / month
€5.35 / month
€7.14 / month
€9.82 / month
€17.85 / month
€23.20 / month
Town events, NPC interaction, and frequently running resource loops can peak together; observe server-side script time per resource.
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.
A crowd in one town increases entity and event density, while players spread across the map create a different synchronization pattern; test both expected cases.
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 | A crowd in one town increases entity and event density, while players spread across the map create a different synchronization pattern; test both expected cases. | Measure a busy session |
| Game activity | Town events, NPC interaction, and frequently running resource loops can peak together; observe server-side script time per resource. | Repeat the peak scenario |
| World / save growth | Characters, properties, inventories, and administration logs expand the database over time; review indexes, query duration, and backup recovery regularly. | 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.
Job, inventory, economy, clothing, and map resources may depend on shared framework data. Verify version and dependency compatibility before production changes.
Mod compatibility can vary by game and server-software release.
Control resource order, permissions, population behaviour, persistent-entity policy, and database timeouts using observations from busy sessions.
After deployment, manage RedM processes, version changes, and settings that require restarts in controlled maintenance windows.
Back up RedM saves, configuration, and additional-content data as separate restore points before changes.
Limit file access to RedM configuration, logs, and managed content directories; stop the relevant process before replacing active files.
List the framework, job and inventory resources, and database needs. Compare resources for that setup, while confirming prepared content, licences and installation responsibilities separately from compute capacity.
Measure a concentrated town gathering separately from a group spread across the map. Resource execution time and synchronisation patterns can differ, so an empty map is not a representative capacity test.
Check its framework dependencies and associated database data first. Keep a backup consistent with the working resource versions and test separately; replacing files alone does not complete a data migration.
Identify and address a repeatedly expensive resource or slow query first. Compare plans for any remaining CPU, memory or storage constraint; a larger plan is not a guaranteed remedy for a faulty script.
Retain resource versions, settings and the database from a consistent operating point. Document permissions and restoration order, then test recovery away from the active community.
Contact support for ordering details and special requirements.