Get 20% off your first order using the coupon code
A world that keeps simulating whether or not anyone is logged in, so crops grow, pollution spreads, and the meteor clock keeps counting down on schedule.
from $5.00/mo · unlimited slots
Enterprise hardware and every feature you need, at a fraction of the price. Not feeling it? We offer a no-questions-asked 7-day refund window.
Need more than 50 GB of NVMe? Just ask.
Keep up to ten backups at once.
Split your server into more than one.
Switch to any supported game, any time.
Modpacks, worlds, mods and plugins.
Every version, mod, and modpack.
We'll tell you when and why it crashed.
No AI or bots here. Only humans.
6 GB at $15.00 fits a settlement of eight to ten citizens, while a medium world with twenty to thirty specialists runs better on 12 GB at $30.00 and its 5 cores.
Every plan: Unlimited Slots · Unmetered Allocations/Ports · Unmetered Databases · Enterprise Hardware · Unmetered NVMe Storage
Need help choosing? Talk to a human or check the docs.
Eco's ecosystem and economy simulation scales with world size and citizen count, so larger maps want the 12 GB and 16 GB tiers and the 5 cores that come with them.
Setup runs automatically after checkout, so terrain generation starts before you have finished writing the server rules.
Instant setup · Automated build · No queue
Plant growth, pollution spread, and market calculations run on Ryzen 9 CPUs with DDR5 ECC memory and NVMe storage.
Ryzen 9 9950X class · DDR5 ECC · 5 cores at 12 GB
Difficulty, world generation, networking, and user files all open in the panel file manager and reload on restart.
Browser editor · Mods folder · Task scheduler
Player slots are unlimited, so you size the server by world and population rather than by a seat count.
Unlimited slots · Whitelist support · Subusers
DDoS protection is included on every server, backed by a 99.9% monthly uptime target in the published SLA.
DDoS included · 99.9% target · No add-on
Put the world close to your citizens with regions in Miami, Dallas, Salt Lake City, Toronto, Brussels, and more.
9 locations · NA and EU · Set at checkout
Eco generates its world once and then simulates it, so decisions made at creation time stick. A smaller map keeps travel short and plant simulation cheap, which suits a group of eight friends. A larger one gives thirty citizens room to specialize and argue about zoning. The meteor deadline sets the clock everyone is working against. All of it lives in configuration files you edit in the panel before the first login.
Eco spreads its settings across several files: one for networking and the server description, one for difficulty and skill rates, one for world generation, and one for users and admins. Mods are assemblies you place in the mods folder, and they have to match the game version your players run. Upload through the file manager, restart from the console, and watch the output for load errors before opening the doors.
Progress in Eco depends on other people, so a server lives or dies on its community. Name your admins in the users file, whitelist if you want a closed run, and use panel subusers so a co-host can restart or moderate without your account credentials. The task scheduler handles a nightly restart, and ten rolling backups mean a griefed town hall is recoverable rather than final.
Compare all 9 game server locations for node hardware and the regions each one covers.
Common questions about running a Eco server with us.
Requirements follow world size and population rather than a slot count. Six gigabytes at $15.00 suits a small world with a handful of settlers, 12 GB at $30.00 with 5 cores fits a medium map and twenty to thirty citizens, and 16 GB at $40.00 gives a large public world room through the late tech tiers.
Not for an existing world. Generation settings apply when the map is created, so a different size means a new world. Archive the old one through the file manager first; ten rolling backups and unmetered NVMe storage let you keep a finished server as a snapshot while a fresh map runs, and you can restore it later if the group asks.
Server-side mods that change recipes, skills, or world behavior only need to sit in the server's mods folder. Anything touching the interface or adding assets players can see has to be installed locally at the same version. Mods are also tied to a specific game release, so check compatibility before you apply an Eco update to the server.
Admin and whitelist entries live in the users configuration file, which you edit in the panel file manager and reload with a restart. For server operations rather than in-game powers, create a panel subuser instead so a co-host can restart, read the live console, or restore a backup without ever touching your billing account.
Yes, and that is much of the point. Plants grow, pollution spreads, animals migrate, and the meteor countdown keeps advancing for as long as the server is up, which is the main argument against running it from a desktop. The task scheduler can perform nightly restarts so long-lived worlds stay tidy between sessions.
