Project Zomboid hosting
built for long saves.

Included: Standard support, L3/L4 DDoS protection, full access to your files and configuration (SFTP included), no slot limit on game servers, and every panel feature: console, schedules, collaborators, and connecting your domain with reverse proxy and SSL.
Options: dedicated IP and backups.
Separate: a database is a server of its own, deployed alongside yours.
Coming soon: Fracture Assistant, an AI built into the panel to help you manage your server.

Build 42 wants around 6 GB before a single player connects, then roughly half a gigabyte per player on top. A heavy mod list can nearly double that. Riverside suits a small to medium modded group, Muldraugh is the baseline we recommend for an established community, and Louisville exists for large servers running overhaul mods.

Yes. The branch is a dropdown in your panel: Build 42.20 stable, Build 41.78.20 legacy, or 42.19 if you are finishing an old pre-stable world. One thing to know before you switch: saves do not carry across builds and most B41 mods will not run on B42, so change the branch on a fresh server rather than an established one.

You put the Workshop IDs in WorkshopItems and the mod IDs in Mods in your server INI, and the game downloads them on start. There is no click-to-install mod browser here. You edit the file directly, in the file manager or over SFTP, which is also why load order and the Map line stay yours to control.

No, and we would rather tell you than sell you cores. Project Zomboid runs its simulation on essentially one thread, so extra cores do not buy player capacity. What actually moves the needle is zombie population, how much of the map has been explored, and your sandbox settings. That is why these plans scale on memory.

Yes. Incremental snapshots, kept off your server disk so a backup can never fill the server and take it down. Hold between 1 and 100 restore points, browse any snapshot, and pull back a single file or the entire world. We recommend turning the game's own backups off, BackupsOnStart=false and BackupsPeriod=0, and letting ours do the job.

Yes. Task automation schedules restarts, console commands and snapshots, and chains them in the order you want. Most Project Zomboid communities run a daily restart to recover the memory that drifts as more of the map gets explored.

Yes. Every restart it pulls the current files for your branch from Steam, so you are never sitting a patch behind. If you are on legacy41 it stays on 41.78.20. It will not quietly drag you onto Build 42.

Yes. RCON is enabled on first deploy with its own port and a generated password, so external admin tools connect straight away. The in-panel console does the same job without leaving the browser, and every action taken lands in your activity log.

Yes. Upload your Zomboid save folder, server INI and sandbox settings over SFTP, set the branch to match the build your save came from, and start. If you want a hand moving a long-running modded world across, open a ticket and we will go through it with you.

You pay on the 1st for the month you just finished using, via Stripe, incl. VAT. Nothing upfront, and you only pay for the days the server actually ran. If you upgrade or downgrade mid-cycle it is prorated automatically on that month's invoice.