Back to Top

Project Zomboid hosting
built for long saves.

Build 42 or Build 41, switchable from the panel. Steam Workshop mods, full file access, and snapshots that live off your server disk.

B42 + B41
Both branches, switchable
~4 min
Deploy to playable
DDoS
Protection included
PLANS

Pick your plan. Deploy in minutes.

Sized on memory, because memory is what Project Zomboid actually runs out of.

Region
Detecting region...
Rosewood

  • RAM
  • CPU
  • Storage
  • Players
Coming soon
Muldraugh

  • RAM
  • CPU
  • Storage
  • Players
Coming soon
Louisville

  • RAM
  • CPU
  • Storage
  • Players
Coming soon

Custom

Need more? Configure your own specs.

Billed end-of-month via Stripe. Cancel anytime, prorated.

BUILDS

Build 42 and Build 41, your call.

Pick your branch in the panel. Saves do not carry across builds and most B41 mods will not run on B42, so switch on a fresh server rather than an established one.

Default
Build 42.20
The current stable branch, multiplayer included. New servers start here.
legacy41
Build 41.78.20
For communities staying on the old build. Your save and your mod list keep working exactly as they do today.
42.19
Last pre-stable
The final pre-stable B42 build, so an existing 42.19 world can be played out instead of abandoned.
Every restart
Updates itself
Your server pulls the current files for its branch from Steam each time it restarts. No manual patching, and no drift onto a build you did not pick.
MODS AND WORLD

Your mod list, your files, your world.

The things a Project Zomboid server needs to survive months of play, handled where they belong.

Steam Workshop mods
Add your IDs to WorkshopItems and Mods in the server INI and they download on start. You edit that file yourself, in the file manager or over SFTP, so load order and map order stay under your control.
Snapshots off the server disk
Project Zomboid writes its own backups next to your save and only deletes the old one after the new one finishes, which is how servers fill their disk and crash. Ours are incremental snapshots kept outside the server, with retention limits.
Restarts on a schedule
Memory drifts as your players open up more of Knox County. Schedule a daily restart, chain a snapshot in front of it, and set PauseEmpty so an empty server stops burning CPU overnight.
Full file access
SFTP into your save, sandbox settings, server INI and mod folders whenever you want to go deeper. Nothing locked behind a panel.
HARDWARE

What you are running on

Project Zomboid leans on one core and a lot of memory. The resources on your plan are guaranteed, even at peak.

FAQ

The essentials.

How much RAM do I actually need?

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. Rosewood suits a small modded group, Riverside is the baseline we recommend for a real community, and Louisville exists for large servers running overhaul mods.

Can I run Build 41 instead of Build 42?

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.

How do Steam Workshop mods work?

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.

Will more CPU cores let me host more players?

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.

Are my world and saves backed up?

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.

Can I schedule automatic restarts?

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.

Does the server update itself?

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.

Do you support RCON?

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.

Can I migrate my existing server?

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.

How does billing work?

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.

Your stack

Everything your community needs.

Add the pieces around your server. One panel, one invoice, one team.

Why LBC

The host we couldn't find, so we built it.

LBC came out of years of fighting hosts that overpromised and under-delivered: fake "unlimited" specs, hidden hardware, slot caps, lock-in, support that never answered. So we built the opposite.

Real hardware, honest specs

We own and run our machines. The specs on the plan are the resources you get, guaranteed and always available, even at peak. No fantasy "unlimited" numbers.

No caps, no lock-in

Priced by real resources, never by player slot. No forced commitment. Scale up, scale down, or leave whenever you want. If you stay, it is because you want to.

Built and run by humans

A small French team builds the platform and runs the hardware in-house. No resellers, no white-label, no faceless call center between you and the people who know the stack.

Fragile Panel

Don't let the name fool you

Fragile, in name only. Console, files, backups, scheduling, and collaborators, all in one interface. Whether it's one server or twenty, everything is where you expect it.

SFTP access included Subdomain included Dedicated IP option available
Learn more →
panel.lbc.hosting
File Manager
Backups
Tasks
Team
Payment

Simple & Fair

Zero Commitment

No contract, no minimum duration, no hidden fees. Upgrade, downgrade, or cancel, effective immediately. No waiting for the next billing cycle.

Predictable Billing

Guaranteed resources on shared infrastructure. Hourly resource validation, invoiced at end of month. Downtime or issues? Automatically credited back, no ticket needed.

Secure Payments

Visa
Mastercard
PayPal
Apple Pay
Google Pay
Revolut
Exclusive to LBC

Flex Mode

Small monthly fee based on your server config. CPU and RAM billing pauses when your server is off for more than 1 hour. Great for event servers, dev environments, or part-time communities.

0h 6h 12h 18h
Mon
0.45€
Tue
0.45€
Wed
0.10€ -78%
Thu
0.10€ -78%
Fri
0.36€ -20%
Sat
0.45€
Sun
0.30€ -33%
-30% this week

All payments securely processed via Stripe

Support

Real people who know the stack.

When something needs a human, you reach our team directly, the same people who build and operate the platform. No outsourced first line, no copy-paste macros.

Answered by a person

Every ticket is handled by someone on our team who actually knows the infrastructure. No bots, no scripts.

Honest hours

Monday to Friday, 10:00-18:00 Paris time on Standard. Weekend cover comes with Priority support. We would rather be upfront than pretend everyone gets 24/7.

French and English

Native French support, with English just as welcome.

Standard support is included free with every server. Priority support adds faster replies and weekend cover, and on-demand quotes are there for hands-on work.

Ready to deploy?

Games, bots, websites, databases. If you don't see what you need, ask us. We'll find a solution.

Get Started