Project Zomboid on Flux
On the Decentralized Cloud

No. We don't sell player slots and we never cap your server. You set Max Players to whatever your community needs. The player count shown on each plan is a guide to what its CPU and RAM handle comfortably — with Project Zomboid, a heavy mod list moves that ceiling far more than the player number does.

Flux is a decentralized cloud infrastructure running on thousands of independent nodes across 50+ countries worldwide, providing redundancy and eliminating single points of failure.

Your Project Zomboid server can be deployed and running in under 30 seconds with our automated deployment system. Mods and custom maps download automatically on the first couple of restarts.

Yes — full Steam Workshop support is built in. In the dashboard's Mod Manager you paste a Workshop link or ID and we automatically resolve the Mod ID and Workshop ID for you, then write both the WorkshopItems and Mods lists. No manual config file editing required. Mods install automatically on the server's next restarts.

Use the built-in dashboard to manage players, edit sandbox and server settings, add or remove Workshop mods, and run admin commands through the RCON console — all from your browser.

Yes. Every server ships with RCON (the classic Source RCON protocol) enabled. From the RCON tab you can list, kick and ban players, broadcast messages, save the world, reload options and check for mod updates in real time. Just set an RCON password during deployment.

We use transparent pay-as-you-go pricing. Plans start at competitive rates with no hidden fees or long-term contracts.

Yes, all servers include enterprise-grade DDoS protection to keep your server online during attacks.

A vanilla Project Zomboid server runs comfortably on about 4 GB of RAM and 2 CPU cores for a small group. Heavily modded servers or larger player counts benefit from 6-8 GB of RAM. About 15 GB of storage covers the game files, mods and world saves. All of our managed plans are pre-sized to these requirements so you never have to guess.

As many as your server can carry — we don't sell slots and we don't cap anything. Plans are sized around 8, 16 and 32 players as a guide to what their RAM and CPU handle comfortably, but you set Max Players yourself. How many mods you run moves that ceiling far more than the player number does, so heavily-modded communities want a higher tier.

Once your dedicated server is online, share its IP address and port (default 36261) with your friends. They open Project Zomboid, choose Join, enter the address and password if you set one, and drop straight into your persistent Knox County. Our servers auto-open the required ports, so no home-router port forwarding is needed.

Yes. A Project Zomboid dedicated server persists 24/7 on the Flux network. Your safehouses, loot, characters and world state are saved and kept running even when every player is offline, so Knox County is exactly as you left it the next time anyone logs in.

Absolutely. Use the Mod Manager to add or remove Workshop mods and the Server Settings tab to change sandbox and server options. Project Zomboid rewrites its config on shutdown, so the dashboard stops the server, applies your changes and restarts it automatically.

That error is Project Zomboid's Lua checksum check: the server refuses any client whose game or mod files differ from its own. Almost always it means Steam updated the player to a newer build than the server is running, so the fix is to align them — open the Game Version tab in your dashboard and update the server to the latest patch, or turn on "always run the latest version" so it follows new releases automatically. If the versions already match, have the player unsubscribe and re-subscribe to the server's Workshop mods, then verify their game files through Steam. As a last resort, turn off Lua File Check (the DoLuaChecksum setting) in the Server Settings tab — this is also the only fix for the rare false positive that Linux servers can hit. Use it only after the first two steps: the check exists to keep everyone's files in sync, and disabling it lets mismatched or modified client files through, which causes desyncs and crashes instead of a clean kick.