We've been quietly testing this for the past four months, and today we're making it official: AxonITech now offers dedicated Assetto Corsa server hosting. Full stop. No shared resources, no "gaming VPS where you figure out the rest" - proper, optimized AC servers with Content Manager integration, mod support, and the kind of low-latency networking that sim racers actually need.
If you've ever tried hosting an AC server on your home PC and dealt with port forwarding nightmares, lag spikes when someone in your household starts streaming Netflix, and that lovely moment when Windows decides to restart for updates mid-race - you know why dedicated hosting matters. We've been there. Several of our team members have been deep in the sim racing rabbit hole for years. Two of us run regular league nights. One has an embarrassingly expensive direct-drive wheel setup that his wife has opinions about.
So let's talk about why this matters, what we're offering, and how to build a racing community that people actually want to come back to.
Why Sim Racing Is Having a Moment
Sim racing isn't niche anymore. Steam's concurrent player counts for Assetto Corsa consistently hit 8,000-12,000 daily, and that's for a game released in 2014. The modding community has transformed it into something that arguably looks and drives better than many newer titles. Steam Charts showed a 23% increase in average monthly players over the past two years - not the trajectory of a dying game.
The sim racing hardware market passed $2 billion globally in 2025. Fanatec, Moza, Simagic - companies that barely existed a decade ago are now shipping hundreds of thousands of units. The audience is real, it's growing, and it's hungry for organized multiplayer.
And here's the thing: AC's server infrastructure hasn't kept up. The official servers are sparse. Most community servers are someone's PC running 24/7 or a cheap VPS that drops frames when more than 15 people join. If you want to run a serious community - league racing, practice sessions, organized championships - you need proper hosting.
Assetto Corsa vs. Assetto Corsa Competizione: Why AC Still Wins for Community Servers
ACC is a fantastic game. We love it for its GT3 focus and out-of-the-box online experience. But for community server hosting, original AC has decisive advantages:
- Mod support: Thousands of cars, hundreds of tracks. Want to race Group C prototypes at the Nordschleife? Vintage F1 cars at Spa? Drift sessions on Ebisu? AC does it all. ACC locks you into GT3/GT4 on a fixed track list.
- Content Manager: This community-built launcher and server manager is genuinely one of the best pieces of modding software ever created. Server configuration that would take hours of INI file editing takes minutes.
- Custom Shaders Patch + Sol: These mods transform AC's visuals to near-photorealistic quality. Rain, dynamic weather, night racing - features Kunos never built are now standard through community mods.
ACC is better for quick, competitive GT racing. AC is better for everything else, especially community building.
What Our AC Server Hosting Looks Like
We're launching with three tiers, designed for different community sizes and use cases.
Starter - 16 Slots
- 2 vCPU cores, 2GB RAM, 20GB SSD
- Single server instance
- Up to 16 concurrent drivers
- Ideal for: friend groups, small drift communities, practice servers
- Starting at 8 EUR/month
Community - 32 Slots
- 4 vCPU cores, 4GB RAM, 40GB SSD
- Up to 2 server instances (run different tracks/configs simultaneously)
- Up to 32 concurrent drivers per instance
- Priority network routing
- Ideal for: growing communities, small leagues, multi-config servers
- Starting at 18 EUR/month
League - 64 Slots
- 6 vCPU cores, 8GB RAM, 80GB SSD
- Up to 4 server instances
- Up to 48 concurrent drivers per instance
- Priority network routing + DDoS protection
- Scheduled restart automation
- Ideal for: organized leagues, championship series, large communities
- Starting at 32 EUR/month
All tiers include: full FTP access, Content Manager server integration, automatic backups, mod upload support, and our management panel for easy configuration.
Setting Up Your Server: A Practical Walkthrough
Let's walk through what actually goes into running a good AC community server. This isn't just "click start" - there are decisions that separate a server people visit once from a server that builds a loyal community.
Track Rotation Strategy
The temptation is to load every track you've ever downloaded. Don't. We've watched dozens of servers die because they rotate through 40 obscure tracks that nobody has installed.
A better approach:
- Keep a core rotation of 6-8 popular tracks. Spa, Nurburgring (both Nordschleife and GP), Monza, Imola, Brands Hatch, Silverstone, Mugello. These are universally installed and universally loved.
- Add 2-3 mod tracks that define your community's identity. If you're a Japanese car community, add Shutoko Revival Project or Akina. If you're into vintage racing, add classic Monza or old Hockenheim. This is what makes people bookmark your server.
- Rotate the mod tracks weekly. Keep the core tracks permanent, swap the specialty tracks on a schedule. Post the rotation in your Discord so people can download tracks before race night.
Car Selection and Balance
This is where servers get messy. An open car server sounds democratic but plays terribly - you'll have someone in a Formula Hybrid lapping GT3 cars, which isn't fun for anyone.
Best practice: pick a class and commit to it.
- Street car servers: Popular and accessible. Limit it to 200-400hp street cars. Mazda MX-5, Toyota GT86, BMW E30, Honda S2000. Close racing, forgiving mistakes.
- GT3 servers: The competitive sweet spot. Good car variety with reasonable BoP (Balance of Performance).
- Drift servers: Open car selection but on dedicated drift tracks. Usual suspects: Nissan Silvia S13/S14/S15, BMW E36, Toyota Chaser.
- Mixed vintage: Group A, Group C, or classic F1 eras. Niche but incredibly passionate communities.
We had a client launch a server with every car enabled on Nordschleife Tourist. It was chaos for two weeks, then the population cratered. They restructured to a "90s JDM only" theme on a mix of Japanese and European tracks. Within a month they had 15-20 regular drivers every evening.
Mod Management: Custom Shaders Patch and Sol
CSP (Custom Shaders Patch) has become essentially mandatory for modern AC. It enables rain, extended physics, new lighting, dynamic weather, and hundreds of quality-of-life features. Your server should specify a minimum CSP version - currently, version 0.2.x or newer is the standard.
Sol handles the weather and time-of-day system. Server-side, you configure weather patterns through Content Manager. The options are deep: cloud coverage, rain probability, temperature curves through a 24-hour cycle, wind patterns. A good weather rotation adds incredible atmosphere - starting a 30-minute race at sunset and finishing under floodlights transforms an ordinary server into an experience.
Important for server hosts: CSP and Sol are client-side mods. You don't install them on the server. But your server configuration needs to enable the extended features they provide (extended physics, weather sync, rain physics). This is handled through Content Manager's server settings under the CSP section.
Anti-Cheat and Fair Racing
Online racing attracts the same problems as any competitive multiplayer: cheaters, trolls, and rammers.
Checksums: AC allows you to enforce file checksums on cars and tracks. This prevents modified car data (boosted power, reduced weight). Enable checksums for all competitive sessions. For casual practice servers, you can relax this - some people run visual-only mods that trigger checksum failures.
Kick voting: AC has built-in kick voting. Set the threshold at around 65-70% - low enough that a majority can remove a griefer, high enough that a couple of frustrated drivers can't abuse it.
Admin tools: Content Manager provides real-time server admin capabilities. You can spectate any driver, send warnings, kick or ban users, and modify server settings without restarting. For league events, having a dedicated admin who isn't racing is valuable - they can monitor for corner-cutting and intentional contact.
Booking mode for league races: For competitive events, use booking mode. Drivers register in advance, get assigned a slot, and the server locks once the session starts. This prevents random joiners from disrupting a championship race.
Running a Competitive League
This is where dedicated hosting earns its keep. A league requires reliability, consistency, and tools that home-hosted servers simply can't provide.
League Infrastructure Checklist
- Dedicated server that's up 24/7: Practice between race nights is essential. Drivers need to learn tracks and setups.
- Consistent ping: Our servers are located in central European data centers with sub-30ms latency to most of Western and Central Europe. Balkan and Eastern European connections typically see 15-25ms.
- Results tracking: Tools like SimResults or custom Discord bots can parse AC server log files to track championship points, fastest laps, and penalties automatically.
- Scheduled restarts: Configure your server to restart automatically before each race event. This clears any memory buildup and ensures clean sessions. Our League tier includes scheduled restart automation through our management panel.
- Backup configurations: Before each round, back up your server config. We've seen leagues lose a full season of results because someone accidentally overwrote the server configuration during pre-race setup.
Season Structure That Keeps People Coming Back
From communities we've helped build: a 10-12 round season with races every 1-2 weeks is the sweet spot. Longer seasons suffer from dropout. Shorter ones don't build enough momentum.
Include 1-2 "drop rounds" (worst results don't count). This keeps drivers engaged even after a bad race or missed event. Schedule a mid-season break of 2-3 weeks - it prevents burnout and gives people time to catch up on practice.
Pre-season testing sessions (2-3 weeks before Round 1) build hype and help new drivers learn the format.
Performance Tuning for Low-Latency Racing
Server performance in sim racing isn't about frames per second - it's about tick rate, network stability, and consistent physics calculations.
Key Parameters
- Server tick rate: AC defaults to 18Hz. For competitive racing, increase this to 30-48Hz. Higher tick rates mean more frequent physics updates sent to clients, which reduces "warping" and improves collision detection. The tradeoff is higher CPU and bandwidth usage - which is why dedicated hosting with guaranteed resources matters.
- UDP packet optimization: AC uses UDP for real-time data. Our servers are configured with optimized network buffer sizes and minimal routing hops to major ISPs.
- Maximum ping limits: Set a max ping limit of 100-120ms for competitive servers. Drivers above this threshold experience desync that affects everyone around them on track. For casual servers, 200ms is a reasonable limit that keeps the experience playable for most.
Resource Scaling
Rule of thumb from our testing:
- Each connected driver uses approximately 40-60MB of RAM
- CPU usage scales linearly with driver count up to about 24 slots, then increases more steeply
- Track complexity has minimal impact on server resources (it's a client-side rendering concern)
- Car count in the mod selection affects server startup time and memory, but not runtime performance
A properly configured 4-core server handles 32 concurrent drivers with CPU utilization around 35-45%, leaving plenty of headroom for traffic spikes.
Getting Started
If you're running a sim racing community on someone's home PC or a generic VPS that wasn't configured for game hosting, you're working harder than you need to and delivering a worse experience to your drivers.
We built this offering because we're part of the sim racing community ourselves. We know the difference between a server that technically works and one that actually feels right - where cars don't teleport on corner entry, where qualifying results are reliable, and where a championship can run a full season without a single server-caused incident.
Pick a tier, upload your track list, configure your cars, and go racing. We'll handle the infrastructure. You focus on building the community.
See you on track.