I've run Squad servers for a couple of clans and a public community over the years, and the honest answer to "should I self-host?" is: it depends on whether you actually want to be the server admin every night. Not casually. Every night. That's the real choice – everything else is implementation detail.

Squad is a game where the community server list IS the matchmaking system. Offworld Industries didn't build a traditional ranked queue. You open the server browser, you pick a server based on its rules, its region, its ping, its reputation, and you join. That means a dedicated server isn't a nice-to-have – if you want to play Squad the way the game is actually designed to be played with a persistent group, a server is table stakes.

Why you need a dedicated server in the first place

A lot of "how to host" guides for other games start with "you can host it from your own PC for your friends" and work up from there. Squad doesn't really have that mode. There's no listen server, no in-game host-a-match. The dedicated server binary is a separate thing you install via SteamCMD – App ID 403240 if you're curious (the game itself is 393380). It runs headless, it expects to be on the public network browser, and it assumes players will find it by browsing the list.

So when people ask "do I need a dedicated server for Squad?", the answer is just "yes, that's the only way". The real question is where it runs.

The self-hosting path

You can absolutely run a Squad server on a box under your desk. I've done it. Here's the rough shopping list if you want to go that route:

A Linux or Windows machine – Offworld ship dedicated server binaries for both, and they're functionally equivalent. Linux is slightly cheaper to operate; Windows is slightly easier if you've never touched a terminal.
A decent upload speed. 50 Mbps up is the realistic floor for a 50-slot server. You'll push roughly 3-5 Mbps per active player under combat load, and bursty when vehicles and logistics pile up.
A static public IP, or a CGNAT workaround. If your ISP is CGNAT (a lot of fibre providers in the UK are now), you cannot port-forward. You're done before you start. This catches people out constantly.
Port forwarding for the three UDP/UDP/TCP ports Squad uses for game, query, and RCON. Squad's defaults sit around the 7787 range but you can move them – just don't hard-code assumptions across multiple servers on the same box.
SteamCMD, to pull down the server binary and patch it every time Offworld ships an update (which is reasonably often).
A licensing decision – do you want to apply for a Squad Server License and appear on the Licensed list, or stay unlicensed?

The self-hosting path is genuinely satisfying when it works. It's also the path that has you restarting services at 11pm on a Tuesday because a Workshop mod pushed a broken dependency, or diagnosing why players from the Netherlands are getting 120ms ping when your line test says 30ms. If that sounds like fun, go for it. Seriously – I still do it for personal projects.

The Squad community docs cover the raw installation steps well. I won't rehash them here because they keep changing.

The managed path

The alternative is paying a host to do the box-wrangling so you can focus on being the admin – which, even with managed hosting, is still plenty of work once you have a community attached.

This is where LOW.MS Squad hosting is our pitch. I'll keep it short because nobody likes a marketing paragraph in the middle of a technical post:

Instant provisioning, so you're in RCON within a few minutes of ordering.
Automated Steam Workshop sync – the server picks up whitelisted mods on restart, no SFTP pushing .pak files.
DDoS protection at the network layer, which matters more for Squad than people think. Licensed public servers attract grief.
Ryzen 7950X or 9950X CPU upgrade available as an option. Squad is heavy on single-thread performance, so this genuinely helps 80-100 slot servers keep a stable tick rate.
RAM ladder from 10 GB up through 15, 20, 25, and 30 GB. The default 10 GB is comfortable for a 50-slot server with a modest mod list; bump it for large mod stacks or 80+ slot boxes.
24/7 support that actually understands Squad, rather than a ticket system that replies "please restart your server" at every opportunity.

That's it. That's the pitch. Pricing is on the plan page because it moves with configuration, and I'd rather not bake numbers into a blog post that'll go stale.

System requirements – rough guidance

I say "rough" because this is always a lived-experience call rather than a spec sheet:

50-slot server with a light mod list: 10 GB RAM, 2 cores of a recent Ryzen, and a 1 Gbps line. Most community servers live here.
80-100 slot licensed milsim night: 15-20 GB RAM, the Latest CPU option if you're on LOW.MS or a 7950X-class chip if you're self-hosting, proper network headroom.
Heavy modded private clan server: depends entirely on the mods. A realism overhaul like Global Escalation eats RAM; vehicle-heavy mods eat CPU.

If you're unsure, start at the 50-slot default and upgrade. It's cheap to scale up on LOW.MS; it's annoying to downgrade hardware you own.

Layers, rotation, and why Squad maps are weird

Squad doesn't have "maps" in the traditional sense. It has Layers – each base map (Yehorivka, Narva, Talil Outskirts, etc.) has multiple Layer variants for different game modes and faction matchups. A single map might have ten or fifteen Layers in rotation.

You configure the rotation in Layers.cfg or, for more elaborate logic, LayerRotation.cfg. I've written up the full format in the Squad server configuration guide because it's too much for a blog post. The short version: most communities just hand-pick 15-20 Layers they like and repeat. Licensed servers tend to lean on the rotation logic to match the time of day or player count.

Mods via Steam Workshop

Squad uses Steam Workshop, which is actually a nice-to-have – players subscribe in the Workshop, the server whitelists mod IDs, and on restart everyone's synced. No "download this 4GB pack from a Google Drive link" drama.

Full config walkthrough lives in the server configuration KB. If Workshop sync breaks (it does, occasionally), the Squad troubleshooting guide has the diagnostic steps I use.

Licensed vs unlicensed

Worth addressing because the terminology confuses newcomers. Offworld Industries maintain a Licensed server list – servers that have applied, been vetted, and agreed to tighter moderation standards. Being on the Licensed list gets you visibility and a certain kind of player who specifically filters for it.

Most public and private servers are unlicensed. Unlicensed servers still appear in the community browser, still work fine, still show ping and player count. If you're running a clan server or a small public community, unlicensed is completely normal. If you want the milsim crowd that takes rules-enforcement seriously, apply for a licence.

The honest take

If you've got one of those Tuesday nights free and you enjoy infrastructure work, self-hosting a Squad server is a genuinely good hobby project. If you just want the server to be there when your community logs in, and you want to spend your time being a good admin rather than a reluctant sysadmin, managed hosting pays for itself within about a week.

Either path, get the server up, get a small group playing regularly, and work out your Layer rotation and admin culture before you worry about licensing or scale. That's the part of Squad hosting nobody talks about – and it's the part that actually decides whether your community sticks around.

How to Host a Squad Dedicated Server