Fits your load
VPS Mini
2 vCPU, 4 GB DDR5, 40 GB NVMe, 2 TB traffic
₹1,780$18.99/mo
Deploy MiniAbout MiniAssetto Corsa server requirements
What a Assetto Corsa 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
- 3 GB
- NVMe storage
- 30 GB
- Traffic per month
- 816 GB
- Busiest upload
- 7.2 Mbit/s
On Clouduxe
Room to grow
VDS MicroCore
2 dedicated cores, 8 GB DDR5, 100 GB NVMe, 8 TB traffic
₹4,970$52.49/mo
- 4 GB more memory, 60 GB more NVMe.
- Dedicated cores: your server never waits for a core another customer is using.
- Headroom for busy evenings, more players, and the mods and updates you add later.
By player count. Without ai traffic density (assettoserver); 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 |
|---|---|---|---|---|---|---|
| 8 | 2 cores | 2 GB | 30 GB | 408 GB | VPS Mini | VDS MicroCore |
| 16 | 2 cores | 3 GB | 30 GB | 816 GB | VPS Mini | VDS MicroCore |
| 24 | 3 cores | 3.5 GB | 30 GB | 1.2 TB | VPS Starter | VDS FusionCore |
| 32 | 3 cores | 4.5 GB | 30 GB | 1.6 TB | VPS Starter | VDS FusionCore |
Traffic assumes 35% of the player cap online on average across the month; change it under Assumptions in the calculator.
Where the numbers come from. Published figures first, then how the calculator turns them into a model.
Published requirements
Minimum (Steam client requirements): Processor: AMD Athlon X2 2.8 GHZ, Intel Core 2 Duo 2.4 GHZ; Memory: 2 GB RAM; Storage: 15 GB. Kunos has never published separate dedicated-server hardware requirements.
Recommended (Steam client requirements): Processor: AMD Six-Core CPU, Intel Quad-Core CPU; Memory: 6 GB RAM; Storage: 30 GB
How the model is built
- Memory
- 1 GB plus 100 MB per player. AssettoServer is a lightweight .NET relay/session server (car physics run client-side, per Assetto Corsa's own C++ client / Go original-server split documented on Wikipedia); no official dedicated-server RAM table exists. Base and per-player figures are a conservative derived estimate for a plain PvP lobby with no AI traffic; the mods multiplier represents AssettoServer's signature AI traffic feature, which adds real server-side simulation load and is the actual documented driver of extra RAM/CPU, not player count alone.
- CPU
- 2 cores, one more for every 16 players. No official CPU sizing exists. A plain relay lobby (no AI traffic) is not CPU-heavy per player. AssettoServer's own FAQ confirms AI traffic density (AiPerPlayerTargetCount / MaxAiTargetCount) scales with player count and is a documented CPU driver for freeroam/AI-traffic servers (e.g. Shutoko Revival Project style setups), captured here via the mods multiplier rather than the base player-scaling term.
- Disk
- 5 GB for the server plus 25 GB for saves and backups, on SSD or NVMe. The AssettoServer binary itself is small (a single executable release); most disk use comes from copying custom car and track content into the server's content folders, which for popular freeroam maps can mean thousands of small files (AssettoServer's FAQ describes a single layout combining 170 pit spawns). SSD mainly helps load time for large content libraries, not runtime tick performance. No official disk-size figure is published.
- Bandwidth
- 450 kbit/s of upload per player. No official bandwidth figure exists. AssettoServer's own default server_cfg.ini sets CLIENT_SEND_INTERVAL_HZ=20 (each client sends position/state updates 20 times per second), and the server relays every client's state to every other client (an all-to-all topology), so total server egress grows faster than linearly with player count, not per-player linearly. This figure linearizes that relay cost around a ~20-player lobby using the sourced 20Hz rate and an assumed compact UDP state-packet size; treat it as a floor, and expect meaningfully more than this simple multiple at 24-32 players.
- AI traffic density (AssettoServer)
- Memory times 1.3 for some and 1.8 for heavy; a heavy load also adds a core.
Kunos never published hardware requirements for a dedicated server, either for the original acServer or for AssettoServer, the actively maintained community C#/.NET server this entry models (used with Content Manager on the client side, per the assignment). The only official numeric anchors available are Kunos' 2014 Steam client (single-player) requirements, which include client-side graphics/physics load a headless server does not carry. RAM, CPU, disk and bandwidth figures here are derived estimates built from AssettoServer's own default configuration and documented features, not a published sizing table. Confidence on this game is lower than the others in this set for that reason.
Before you set it up. The ports it listens on and what the guides say drives its load.
Ports
| Port | Protocol | Used for |
|---|---|---|
| 9600 | UDP | game (default UDP_PORT, configurable) |
| 9600 | TCP | game handshake (default TCP_PORT, configurable) |
| 8081 | TCP | HTTP server info / lobby registration (default HTTP_PORT, configurable) |
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
- AssettoServer relays every connected car's state to every other connected car, so bandwidth grows faster than linearly as the lobby fills. Budget more headroom than a flat per-player number for 24+ player servers.
- AI traffic (AssettoServer's signature server-simulated traffic feature) is a bigger CPU/RAM driver than human player count alone; a dense freeroam server needs more than a plain PvP race server with the same headcount.
- Enable Steam Auth in extra_cfg.yml to stop SteamID spoofing. It requires a minimum Content Manager and CSP version on the player's side, not extra server hardware.
- Storage needs are really about your car/track mod list, not the server binary itself. Large freeroam maps with hundreds of pit spawns and many mod cars add up fast.
Assetto Corsa server questions
How much RAM does a Assetto Corsa server need?
About 2 GB for 8 players and 4.5 GB for 32, before ai traffic density (assettoserver). AssettoServer is a lightweight .NET relay/session server (car physics run client-side, per Assetto Corsa's own C++ client / Go original-server split documented on Wikipedia); no official dedicated-server RAM table exists. Base and per-player figures are a conservative derived estimate for a plain PvP lobby with no AI traffic; the mods multiplier represents AssettoServer's signature AI traffic feature, which adds real server-side simulation load and is the actual documented driver of extra RAM/CPU, not player count alone.
How many CPU cores does a Assetto Corsa server need?
2 for 8 players, 3 for 32. The server is single-thread heavy, so the clock speed of one core matters more than how many cores it has. No official CPU sizing exists. A plain relay lobby (no AI traffic) is not CPU-heavy per player. AssettoServer's own FAQ confirms AI traffic density (AiPerPlayerTargetCount / MaxAiTargetCount) scales with player count and is a documented CPU driver for freeroam/AI-traffic servers (e.g. Shutoko Revival Project style setups), captured here via the mods multiplier rather than the base player-scaling term.
How much bandwidth does a Assetto Corsa server use?
About 450 kbit/s of upload per connected player, so 7.2 Mbit/s with 16 players online and about 816 GB a month if 35% of that cap is online on average. No official bandwidth figure exists. AssettoServer's own default server_cfg.ini sets CLIENT_SEND_INTERVAL_HZ=20 (each client sends position/state updates 20 times per second), and the server relays every client's state to every other client (an all-to-all topology), so total server egress grows faster than linearly with player count, not per-player linearly. This figure linearizes that relay cost around a ~20-player lobby using the sourced 20Hz rate and an assumed compact UDP state-packet size; treat it as a floor, and expect meaningfully more than this simple multiple at 24-32 players.
Which Clouduxe plan should I pick for Assetto Corsa?
For 16 players, VPS Mini fits the load and VDS MicroCore 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 calculatorsHost Assetto Corsa on VPS Mini.
Sized for 16 players, with DDoS protection included. Or talk to us about a bigger server.