You had a good server. Forty people on a Friday, a nesting pack up by the lake, someone's Deinosuchus living in the river for a fortnight. Then a patch dropped on a Tuesday afternoon while the owner was at work, the server stayed on the old build, and by the time anyone noticed the browser had quietly emptied. That's how most Isle communities die. Not drama. Just a build mismatch nobody was around to fix.
Or the other version: a mate set up a server on his PC, gave everyone his IP, and nobody could join because the game never registered with Epic and he'd forwarded the wrong port. Both of those come up in our tickets every week, and this article is about avoiding both, whether you run the box yourself or rent one from us.
Current as of Evrima 0.21.7xx, September 2026.
Evrima, and only Evrima
The Isle has two branches on Steam. Legacy is the old game, frozen since February 2022. Evrima (people type Evirma and Envirma too) is the rebuild, and it's the only one still being developed, the only one with the current 23-species roster, and the only one we host. If you're setting up a server in 2026, you're setting up Evrima. If you're not sure which one you've been playing, the Evrima vs Legacy guide sorts that out in a couple of minutes.
Running it yourself
You can absolutely self-host. Plenty of people do, and if you've got a spare Windows machine, a decent upload speed and the patience to forward ports, here's the whole thing.
Install SteamCMD, then pull the server. The dedicated server is app 412680 (the game itself is 376210), it takes anonymous login, and the branch is evrima:
login anonymous
force_install_dir C:\TheIsleServer
app_update 412680 -beta evrima validate
quit
One line for the curious: -beta hordetesting in place of -beta evrima gets you the public test branch, where patches land before they reach everyone else. Don't run a community server on it: test-branch clients and Evrima clients can't see each other, and a test build can be replaced without notice.
Now the bit that catches people. Evrima doesn't advertise itself through Steam's server browser. It registers with Epic Online Services (EOS), and for that the server needs an [EpicOnlineServices] block in Engine.ini with a DedicatedServerClientId and DedicatedServerClientSecret. Those two values ship with the server files and are the same for every host, so this isn't a credential you apply for. It's a block you have to make sure is present:
[EpicOnlineServices]
DedicatedServerClientId=<from your server files>
DedicatedServerClientSecret=<from your server files>
Then Game.ini, which on a Windows box sits at TheIsle\Saved\Config\WindowsServer\Game.ini. Evrima boot-loops without a valid one. It'll sit there at about 1.3 GB of RAM and no CPU, restarting forever, and the log won't shout about it. Two section headers matter:
[/Script/TheIsle.TIGameSession]
ServerName=My Isle Server
MaxPlayerCount=50
bEnableMigration=true
[/Script/TheIsle.TIGameStateBase]
Note the key is bEnableMigration, singular. Guides that write bEnableMigrations are wrong. Fill the rest of the file in from the settings you want (the settings guide lists the ones that matter), then launch:
TheIsleServer.exe TheIsle -log -Port=7777
Ports. The game port is UDP, whatever you put in -Port. RCON is TCP at the game port plus two, so 7779 here. Evrima honours -Port and ignores -QueryPort, and it opens no query socket at all, so don't waste an evening forwarding one. And then you wait. A freshly started Evrima server takes two to five minutes to register with EOS and show up in the in-game browser. Every self-hoster I've talked to has restarted their server at least once in that window thinking it was broken. It wasn't. It was registering.
After that, you own the updates. Every patch means running the SteamCMD line again, on the day, before your players update their clients, or you get the Friday-night scenario from the top of the page.
What you get on a LOW.MS server
Everything above, done for you, and then a panel on top of it. Honestly the panel is the reason to rent rather than the hardware, so here's what it actually does for The Isle.
Settings as a form. Manage > Settings holds every field we expose: server name, map (Gateway, Spiro or Panjura), max players, password, the day and night lengths, growth multiplier, AI spawning, the Playable Classes multi-select and the Enabled Mutations list. Save applies at the next start, Save & Restart applies now, and Game.ini is written from the form on every boot. You never touch the file.
A Players tab. Roster with who's online and last seen, an Admins list and a Whitelist backed by the SteamID64 fields, kick and ban per row. Ban asks for a reason.
A console that speaks Evrima. Evrima's RCON protocol is its own thing, and standard tools like mcrcon don't talk to it. The panel does. The Console tab shows live output and takes announce, kick, ban, playerlist and save straight from the command box. If you'd rather run a Discord bot, flip on External RCON access under Manage > Settings > Advanced and point it at the RCON port. The settings guide covers the toggle.
Updates from a button. The Game updates card on the Overview tab tells you a patch is waiting, and Update installs it. Restarts can be scheduled too.
Backups, DDoS, regions, people. One-click backups and restore on the Backups tab. DDoS protection in front of every server. A choice of region at checkout so the server sits near your players. And a support team around at all hours who've seen every Isle ticket there is. Plans and locations are on the hosting page.
Ordering
Pick a plan on the hosting page, choose a region, pay. The server provisions itself and shows up in the panel with the Evrima branch already installed, an RCON password already generated, and a connection address in the strip at the top of the page. That's it. There's no "wait for a human" step.
First-time setup
Don't repeat what the getting started guide already does properly. Short version: set a server name, decide whether you want a password, add your own SteamID64 to Admin SteamIDs, save, start, then give it those two to five minutes before you go looking for it in the browser. Everything else can wait until you've joined once.
A few things we've learned running these
Patch day is the whole game. When The Isle updates, Steam patches the players within the hour and the server waits for you. A server on the old build is still visible in the browser, which is the cruel part. People see it, try to join, get "Client Disconnected" or a timeout at twenty seconds, and assume it's dead. Press Update, or schedule one.
The 1.3 GB idle is normal. A fresh Evrima server sits at roughly 1.3 GB of RAM doing nothing, and that number barely moves until players arrive. It's also, confusingly, exactly what a boot-loop looks like, so if you're self-hosting and your server is at 1.3 GB with no CPU and nobody can find it, check Game.ini before anything else.
CPU is single-core at high population. Evrima leans hard on one thread as the player count climbs, so a busy server is bound by clock speed rather than core count, and more RAM helps AI density more than it helps player count. I won't give you numbers. They change every patch.
EOS is slower than you'd like. Two to five minutes after every restart before the browser lists you, and the odd EOS outage that makes every server on the planet vanish at once. When the whole list is empty, it isn't you.
Does Evrima support mods?
No, not in any official sense. There's no Workshop, no mod loader, and no plan the developers have put a date on. What the community calls "mods" for Evrima is a mix of injector tools and UE4SS-style scripting that runs alongside the game process on a machine you control. Those don't run on a shared game server, ours included, because a game server executes the game and nothing else. RCON tools and Discord bots are a different story and work fine. If an injector or a DLL is the reason you want a server, open a ticket and ask before ordering anywhere, ours included, and we'll tell you straight what runs.
Go and build something
Whether it's a box under your desk or a server with us, the hard part isn't the setup. It's keeping it patched and keeping the people. If you get stuck on ours, open a ticket from the panel with the server name and what you tried, and someone who's done this a hundred times will pick it up. We'd rather hear from you early than after the Friday crowd has gone.