I've run Don't Starve Together dedicated servers for a couple of different co-op groups over the years, and the thing that catches people out every single time isn't mods or world settings – it's the multi-shard architecture. DST isn't like most survival games where you spin up one process and you're done. There's an overworld shard, an optional caves shard, a Klei account token, and a cluster config that ties the whole thing together. Once you've seen it laid out it's not that bad, but first-timers staring at cluster.ini and two separate server.ini files almost always ask the same question: is this really worth self-hosting, or should I just pay someone?
Honestly, that's the right question to ask up front. So let's start there.
Why bother with a dedicated server at all?
DST has a perfectly fine peer-to-peer mode. One person hosts, everyone else joins, and the world only exists while the host is online. That's fine for a weekend session with two friends. It falls apart the moment you want the world to persist through the week, or you want to add caves, or you want mods to stay in sync, or the host's internet drops mid-raid and everyone loses twenty minutes of progress.
A dedicated server fixes all of that. It's online 24/7, the world rolls on whether anyone's connected or not, caves stay warm and ready, and Workshop mods are downloaded and versioned centrally instead of re-synced every time someone joins. The downside is real though: it costs money. Peer-hosted is free. So the honest answer is that a dedicated server is worth it once your group is more than two people and you're playing more than once a week. Below that bar, don't bother.
The self-hosting path
If you've got a Linux or Windows box at home or a VPS sitting spare, you can absolutely run DST on it. Klei ship a free dedicated server binary on Steam (app ID 343050) and the instructions on their wiki are decent.
What you'll actually need:
- A machine that stays on 24/7. An old laptop works until the fan dies. A small VPS is more reliable.
- A static public IP, or a dynamic DNS setup. If your ISP has you behind CGNAT, none of this works without a VPN tunnel or port-forwarding workaround.
- UDP port reachability for the overworld, plus a second UDP port if you enable caves. Your router has to forward these.
- A Klei Account Token (the KU_xxx dance – you generate it at accounts.klei.com under Game Servers).
- Patience for the fact that SteamCMD will occasionally decide to re-download 2 GB of server files at the worst possible moment.
In my experience, the self-hosting path is fine until it isn't. The setup takes an afternoon. The maintenance is what grinds you down – updates land, shards desync, the caves process hangs while the overworld keeps running, and nobody in your group knows how to SSH in to restart it. If you enjoy the sysadmin side, it's genuinely fun. If you don't, you'll be resentful of it within a month.
The managed hosting path
This is the bit where the "just pay someone" option starts looking good. On LOW.MS DST hosting your server gets provisioned in a few minutes, caves come pre-wired if you want them, and the Klei token step is the only bit of Klei-specific faff left. Ports are allocated automatically from our public range so you never touch a router. Workshop mods install via the panel.
On the hardware side, our DST nodes run on AMD Ryzen 7950X and the newer 9950X "Latest" CPUs, so tick rate holds up even with a big modded shard and a full player count. RAM tiers go from 10 GB at the base plan up through 15, 20, 25, and 30 GB for heavier modded setups – a vanilla 6-player server doesn't need anywhere near the top tier, but it's there if you want it. Current pricing lives on the hosting page because I'd rather link the real number than have this blog go stale the next time we shift tiers.
My take: if your group is more than four people, if you want caves, or if you're running a modpack bigger than a handful of QoL mods, managed is the better value for the time you'll save. If you're two people playing vanilla and you already own hardware, self-host.
What specs do I actually need?
People wildly over-spec DST servers. It's not a demanding game. A 4 GB VPS will happily run a vanilla 2-player world. 8 GB is comfortable once you enable caves and add a reasonable mod list. 16 GB is overkill unless you're running 50+ mods and pushing tick rate to 60.
CPU matters more than RAM. DST's simulation is single-threaded per shard, so raw single-core performance is what keeps tick rate stable when the world gets busy. A modern Ryzen or Intel chip handles this easily – a cheap old Xeon tends to wheeze once you've got a full group and a few shadow creatures spawning at once.
Bandwidth is modest. A full 6-player server barely nudges 1 Mbps upload in normal play. You'll use more bandwidth downloading the server update than you will running it for a week.
The ports thing
If you're self-hosting, the overworld shard listens on one UDP port and the caves shard listens on another. Klei's defaults are 10999 and 10998 but you can set these to whatever you want in each shard's server.ini. What matters is that both are UDP, both are reachable from the public internet, and your router forwards both.
On a managed LOW.MS server you don't touch any of this – ports are allocated for you from our public range and the firewall's already open. That's one of the bigger quality-of-life wins over self-hosting, especially if you've never done port forwarding before.
Mods and the Steam Workshop
DST has one of the most active modding communities of any survival game – the Workshop has thousands of mods and a good chunk of them are high-quality. The nice thing about DST specifically is that the server doesn't need a Steam login to pull mods. Klei's dedicated server binary handles Workshop downloads itself via a dedicated_server_mods_setup.lua file, and the server auto-syncs required mods to joining players. You don't have to install anything on the server-side Steam, and players don't need to pre-subscribe to mods to join.
The one gotcha – covered in the getting started guide – is that listing a mod in dedicated_server_mods_setup.lua only downloads it. You also need to enable it in each shard's modoverrides.lua, otherwise the server grabs the files and then ignores them. First-timers miss this constantly.
A quick word on Don't Starve Elsewhere
If you're setting this up in 2026 you might be wondering whether DST is about to go end-of-life now that Klei announced Don't Starve Elsewhere at the Triple-i Initiative in April. The short answer is no – Klei have been clear that they're supporting DST in parallel, not replacing it. The dedicated server binary isn't going anywhere, the Workshop isn't going anywhere, and your cluster will keep working for years yet. Host with confidence.
Where to go next
Once your server's up and the group's connected, most of the interesting work is on the config side – tuning world generation, setting admin commands, dialling in season lengths, and debugging the occasional shard desync. The server configuration guide covers the deeper config knobs, and the troubleshooting guide has the fixes for the handful of issues every DST host hits sooner or later. The first week tends to be the noisy one; after that it mostly just runs.