Eco might be the only survival game where leaving the server off for a weekend can quietly ruin the save. Not because someone raids you, there is no combat and your character cannot die, but because the planet keeps simulating without you. Trees grow, animal populations shift, pollution spreads, and the meteor countdown keeps ticking.
That one detail changes the whole "can I just host it myself?" question, and it is the part almost nobody mentions. So here is the honest version, including the two things people keep asking us: whether a free Eco server is real, and whether you can rent one for Xbox or PlayStation.
The server software is free. Running it is not.
Strange Loop Games gives the Eco dedicated server away. It is a separate download from the game, either through SteamCMD as app 739590 or as a package from play.eco. Nobody needs a second copy of Eco to run it, and there is no per slot licence. With a spare machine and an evening you can have a world up on port 3000 with the browser dashboard running next to it.
So yes, a free Eco server is a real thing. Anyone who tells you otherwise is selling something.
What is not free is everything wrapped around that software. A machine that stays powered on. An upload connection that does not fall over when six people load chunks at the same time. A router you are willing to open ports on. Backups, because an Eco world is dozens of hours of collaborative work and a corrupted save has no undo button. And your own attention every time an update lands and the world needs migrating.
Eco on Xbox and PlayStation: there is no console version
This comes up constantly, so let's be blunt about it. Eco has never shipped on Xbox, PlayStation or Switch, and Strange Loop Games has not announced a port. The game is PC only, on Windows, Mac and Linux, and it has been that way since early access opened in 2018.
That means there is nothing to rent for a console. No host has a secret Xbox build. If you are searching for an Eco server for PS5, what you have found is either a different game with a similar name or a listing that is about to waste your money.
It is worth understanding why a port is not a small job here. Eco is not a survival game with a menu of sliders. Its civilization layer runs on law that players write themselves: you draft legislation in a node editor, argue about it, vote it through, and then the server enforces it on every block placement and every sale. Look at what that interface actually is and you can see why this is a keyboard, mouse and second monitor game.
World size drives the cost, not player count
Most games size a server by slots. Eco does not really work that way. Its load comes from the simulation, and the simulation scales with how much planet there is.
Every plant tracks its own growth. Animal populations move and reproduce. Since Update 14 arrived in August, crafting also produces garbage as a byproduct, and pollution diffuses through ground, water and air across the whole map. None of that cares whether a single player is logged in.
In practice, 30 players on a small map is often calmer than 6 players on a huge one. Our Eco RAM calculator reflects that: changing the world size moves the answer by several gigabytes, while each extra player adds a fraction of one. When someone tells us their Eco server is struggling, the fix is usually a smaller world next cycle, not more slots.
Eco never pauses, and that is the real decider
Here is the part that settles self-hosting for most groups.
Eco's world clock is real time. The meteor deadline your server is configured with counts down in real hours, not in playtime. Crops finish while you sleep. Contracts come due. The economy your players built keeps running whether or not they are there to run it.
Turn the machine off overnight and you have not paused the game, you have skipped it. Do that for a week and the planned harvest, the law that was mid vote and the timeline everyone agreed on all drift apart. Groups hosting on a gaming PC usually work this out around week three, which is exactly when the world has become worth protecting.
There is a security angle too. Hotfix 14.1.1, released on 6 September, closed a hole that let malicious players manipulate bank account data on servers. Eco's entire endgame is economic, so that is not a cosmetic bug. A self-hosted server is only as patched as you remember to keep it.
So which should you pick?
Self-host if you are testing mechanics, running a short world for four friends on a small map, or you already keep a machine on around the clock and enjoy that side of it. It costs nothing but attention, and Eco's server really is straightforward to stand up. Our Eco dedicated server setup guide walks through the whole thing.
Rent if the world is meant to last. A civilization server with a working economy, elections and a 30 day meteor is a months long commitment from everyone in it, and it deserves a machine that does not go down because someone needed their PC back. That is also the point where automatic backups stop being optional.
Neither answer is wrong. The mistake is picking the free route for a world you intend to keep, then losing it in week five.
Before you start
Size the map before the first player joins, because changing it later means a new world. Keep the server on 14.1.1 or newer. Back up before every update, especially the ones that migrate worlds.
If you would rather skip the port forwarding and the uptime babysitting, our Eco server hosting runs on dedicated Ryzen 9 hardware with automatic backups and one click updates. If not, go build something. The planet is patient. The meteor is not.
