Fits your load
VDS MicroCore
2 dedicated cores, 8 GB DDR5, 100 GB NVMe, 8 TB traffic
₹4,970$52.49/mo
Deploy MicroCoreAbout MicroCoreRedM server requirements
What a RedM server needs in CPU, memory, disk and bandwidth, by player count. Change the numbers for your own server; the sources are listed below.
What it needs
- CPU
- 2 coresSingle-thread heavy: clock speed matters more than core count.
- Memory
- 8 GB
- NVMe storage
- 50 GB
- Traffic per month
- 1.5 TB
- Busiest upload
- 13 Mbit/s
On Clouduxe
Room to grow
VDS FusionCore
4 dedicated cores, 16 GB DDR5, 200 GB NVMe, 10 TB traffic
₹9,940$104.49/mo
- 2 more dedicated cores, 8 GB more memory, 100 GB more NVMe.
- Headroom for busy evenings, more players, and the mods and updates you add later.
Sized with Clouduxe's own table for cfx.re servers: cfx.re publishes no hardware figures.
By player count. Without framework and scripts (vorp/redem:rp, custom maps); each step up in the calculator adds memory, disk and sometimes a core.
| Players | CPU | Memory | NVMe | Traffic a month | Fits your load | Room to grow |
|---|---|---|---|---|---|---|
| 10 | 2 cores | 8 GB | 50 GB | 454 GB | VDS MicroCore | VDS FusionCore |
| 15 | 2 cores | 8 GB | 50 GB | 680 GB | VDS MicroCore | VDS FusionCore |
| 32 | 2 cores | 8 GB | 50 GB | 1.5 TB | VDS MicroCore | VDS FusionCore |
| 48 | 4 cores | 16 GB | 50 GB | 2.2 TB | VDS FusionCore | VDS OmniCore |
| 64 | 4 cores | 16 GB | 50 GB | 2.9 TB | VDS FusionCore | VDS OmniCore |
| 100 | 6 cores | 24 GB | 50 GB | 4.5 TB | VDS OmniCore | VDS PrimeCore |
| 128 | 6 cores | 24 GB | 50 GB | 5.8 TB | VDS OmniCore | VDS PrimeCore |
| 200 | 8 cores | 32 GB | 50 GB | 9.1 TB | VDS PrimeCore | VDS TitanCore |
Traffic assumes 35% of the player cap online on average across the month; change it under Assumptions in the calculator. Sized with Clouduxe's own table for cfx.re servers: cfx.re publishes no hardware figures.
Where the numbers come from. Clouduxe's own sizing, and what cfx.re publishes.
How Clouduxe sizes cfx.re servers
cfx.re publishes no hardware figures for RedM servers. This is the table Clouduxe sizes them with, on dedicated EPYC cores. With heavy scripts and MLOs, pick the room-to-grow plan the calculator shows.
| Players | Plan | Cores and memory |
|---|---|---|
| 1 to 32 | VDS MicroCore | 2 cores, 8 GB |
| 33 to 64 | VDS FusionCore | 4 cores, 16 GB |
| 65 to 128 | VDS OmniCore | 6 cores, 24 GB |
| 129 to 200 | VDS PrimeCore | 8 cores, 32 GB |
| 201 to 300 | VDS TitanCore | 12 cores, 48 GB |
| 301 and more | VDS UltraCore | 16 cores, 64 GB |
Published by cfx.re
OneSync is free up to 48 slots, after such, you should get one of the following tiers from the Cfx Portal starting from FiveM Element Club Argentum
Disk (10 GB plus 40 GB for saves) and bandwidth (400 kbit/s a player) are planning estimates.
Before you set it up. The ports it listens on and what the guides say drives its load.
Ports
| Port | Protocol | Used for |
|---|---|---|
| 30120 | TCP | game (HTTP resource delivery) |
| 30120 | UDP | game (client connection) |
Game server hosting: every game we size, the protection each one gets, and the plan for it.
DDoS protection is on every Clouduxe plan. How Prism handles game traffic.
What drives the load
- RedM shares its FXServer engine with FiveM, so it is likewise bound by single-thread performance; prioritize CPU clock speed over core count.
- Servers over 48 players need OneSync plus a paid Cfx.re Element Club subscription (Argentum for 64, Aurum for 128, Platinum for up to 2048), separate from your hardware.
- Disk needs scale with custom maps, peds, and script packs (VORP, RedEM:RP) more than with raw player count.
- Bandwidth figures for RedM are not well documented publicly; monitor actual usage after launch rather than relying on a fixed per-player number.
RedM server questions
How much RAM does a RedM server need?
About 8 GB for 10 players and 32 GB for 200, before framework and scripts (vorp/redem:rp, custom maps). That is the memory of the plan Clouduxe sizes this player count on; cfx.re publishes no hardware figures.
How many CPU cores does a RedM server need?
2 for 10 players, 8 for 200. The server is single-thread heavy, so the clock speed of one core matters more than how many cores it has. Clouduxe sizes cfx.re servers on dedicated EPYC cores, from its own table below.
How much bandwidth does a RedM server use?
About 400 kbit/s of upload per connected player, so 13 Mbit/s with 32 players online and about 1.5 TB a month if 35% of that cap is online on average. No official or widely sourced per-player bandwidth figure exists for RedM. Hosting guides only give plan-level guidance (about 100 Mbps for small servers, 1 Gbps network capacity for established/large ones). 400 kbps/player sustained upload is an estimate consistent with those plan-level numbers at typical player counts (400*32=12.8Mbps, well under the 100Mbps small-server guidance) and with the similar, better-documented FiveM platform it shares an engine with. Treat this figure as low confidence.
Which Clouduxe plan should I pick for RedM?
For 32 players, VDS MicroCore fits the load and VDS FusionCore leaves room to grow. Every plan includes DDoS protection: 17 Tbps of upstream mitigation plus Clouduxe Prism on the server.
Other games. The same calculator, sized from each game's own documentation.
All calculators- 7 Days to Die
- ARK: Survival Ascended
- ARK: Survival Evolved
- Arma Reforger
- Assetto Corsa
- Conan Exiles
- Counter-Strike 2
- DayZ
- Enshrouded
- Factorio
- FiveM
- Garry's Mod
- Minecraft: Bedrock Dedicated Server
- Minecraft: Java Edition
- Palworld
- Project Zomboid
- Rust
- Satisfactory
- Space Engineers
- Team Fortress 2
- Terraria
- Unturned
- V Rising
- Valheim
Host RedM on VDS MicroCore.
Sized for 32 players, with DDoS protection included. Or talk to us about a bigger server.