Hell Let Loose is one of the trickier WWII shooters to run well. It's CPU-hungry, it does not like being undersized on RAM, and most serious community servers end up running a whole second stack of tooling on top via CRCON. If you're shopping for a host, or you're already running one and wondering why match 3 of the evening gets rough, the game punishes shortcuts in ways that other shooters don't.
This is the honest version of what we've learned hosting HLL servers for customers on LOW.MS – what actually matters, what you can safely ignore, and what to look for in a provider before you hand anyone your card details.
The short version
HLL matches run 50 vs 50. That's not a marketing number, that's the actual player cap, and it's the scale the whole game engine and netcode is tuned around. Most people who buy a server buy a 100-slot one because that's what the game's built for, but there are plenty of reasons to run smaller – we'll get into that.
The thing to understand is that "100 players in a match" is not the same kind of workload as "100 players in a sandbox survival game". HLL is simulating vehicles, artillery, garrison logic, supply nodes, and a lot of projectile and damage state, all at a tickrate that matters for gunfights. When it goes wrong, it doesn't crash – it just starts feeling rubbery, and you lose your regulars without ever seeing an error in the log.
Current specs, slot sizes and pricing all live on the Hell Let Loose hosting page – we deliberately don't repeat the numbers here because they move around.
What you actually need from a host
Four things, in rough order of importance.
CPU single-thread performance. This is the one most people get wrong. HLL's dedicated server is not well-threaded; it leans hard on one or two fast cores, and if those cores are shared with other noisy neighbours on the same box, your tickrate will visibly suffer during big pushes. When you're comparing providers, the question to ask is what generation of CPU the box is running and whether there's any form of core pinning or performance guarantee. "Enterprise Xeon" from 2016 is not the answer you want.
Enough RAM headroom for a full lobby. A mostly-empty HLL server looks deceptively light. Load it up, get a couple of garrisons placed, a few SPAs firing and a proper engagement going, and memory usage climbs hard. You do not want to be anywhere near the ceiling when that happens. Don't buy the bargain-bin plan that technically starts but chokes at match 2.
Low-latency routing to your playerbase. HLL players care about ping more than most communities will admit. An EU community server hosted out of a cheap US datacentre will bleed regulars no matter how well-configured it is. Pick a provider that actually has capacity in the region you're targeting – on LOW.MS you pick location at checkout, and for HLL specifically that's worth thinking about before you click buy.
Support that knows what CRCON is. This is where a lot of cheap hosts fall apart. The moment you open a ticket that says "RCON is intermittent from my CRCON container" and the reply comes back asking what CRCON is, you know you're on your own. You want support that doesn't flinch at the acronym.
DDoS protection, automated backups and 24/7 tickets are the table-stakes stuff – we include all three, and honestly any provider you seriously consider should too. It's not a differentiator in 2026, it's the floor.
64, 82, or 100 slots?
Short answer: pick the size you can keep full on a Tuesday night, not the size that sounds impressive on your Discord banner.
A 100-slot server is the full HLL experience, and it's what most players scroll for in the browser. It's also the hardest thing on earth to seed from zero. If you don't already have a community, a 100-slot public server is a lot of empty real estate to stare at.
64 slots works really well for clan servers, scrim nights, and smaller communities where every squad leader actually talks. The matches feel different – tighter, more personal – and you're not fighting the seeding problem.
82 is the quiet middle ground. You get most of the big-battle feel without the full weight of keeping a 100-slot lobby alive, and queue management is less painful during peak hours.
If you're unsure, start smaller and upgrade later. Going 82 → 100 when your community is actually full is a much nicer problem than running a 100-slot ghost town for three months.
What version of the game are we hosting, anyway?
As of April 2026 the live build is on the Update 19 line – 19.1 "Remagen Refresh" dropped at the end of March and reworked Remagen's flow while keeping the Ludendorff Bridge as the centrepiece. Update 19 itself added Smolensk as a new Eastern Front map and introduced the Artillery Squad and SPA vehicles, which changed how a lot of matches play out. If you're writing server rules or tuning map rotations, don't copy something from 2024 and hope for the best.
The big thing on the horizon is Conquest, a 50v50 mode built around a shared ticket pool rather than linear point capture. It's currently live on the experimental_branch Steam beta for players to test – it's not on the default branch yet, and at time of writing there's no official date for when it will be. Worth watching if you're planning rotations for later in the year. The 2026 roadmap also trails a Canadian Forces faction and a Vietnam update; we'll believe the dates when we see them, but the direction is real.
CRCON – the bit nobody tells you about upfront
If you're running a community HLL server and you're not using CRCON, you're making your life much harder than it needs to be. CRCON (Community RCON) is a web app that wraps the game's RCON protocol and gives you real admin tooling: player history, VIP management with expiries, map voting, discord integration, logs, stats, the lot. It's maintained on GitHub at MarechJ/hll_rcon_tool, and every serious HLL community we host for is running it in some form.
The important detail for hosting decisions: CRCON runs separately from the game server. It's a Docker stack that connects to your server over the RCON port. That means all you actually need from your host is a reachable IP, a stable RCON port and the RCON password – which we give you in the control panel. You can run CRCON on a small VPS, a home box, or one of the community-hosted options. You don't need your game host to "support CRCON" in any special way; you just need them to not get in the way of outbound RCON, which we don't.
Before you order
A short checklist, because it saves tickets later:
- Pick your region first. For HLL, ping beats everything.
- Pick a slot count you can realistically fill on a weeknight.
- Decide whether you're going to run CRCON from day one. If yes, have somewhere to put it.
- Have a rough idea of your rules before you open the config files – it's much easier to set them once than to change them after your regulars have learned the old ones.
Once you've ordered, the Hell Let Loose getting started guide walks through the first boot, connecting in, and handing out admin. When you're ready to actually tune the experience, our server settings post covers the knobs that matter, and the map guide for server operators is worth a read before you build a rotation. The one piece of advice we'd leave you with: don't over-tune on day one. Get the server up, get ten friends on it, play a full match, and only then start changing things. HLL rewards patience more than most games, and so does running a server for it.