Your mate has the good world save. Your mate is away for the weekend. Your entire group is now staring at the Discord chat like a party of villagers waiting for a door to open.
That is the practical problem serverless multiplayer tries to solve. Not every co-op session needs a rented machine humming away 24/7 just so someone can plant parsnips, move conveyor belts, or get repeatedly flattened by a boss. For plenty of games, the expensive bit is not running the world. It is making sure the right person has the right save, nobody overwrites it, and a bad mod or crash does not turn 80 hours into digital compost.
What serverless multiplayer actually means
The phrase gets used loosely, so let’s remove the fog machine. Traditional multiplayer usually means a dedicated server: a computer hosts the game world continuously, players connect to it, and the server keeps the authoritative save. That can be a home PC, a rented host, or an official service.
Serverless multiplayer, in the co-op sense, means the group does not keep a permanent game server running. Instead, players take turns hosting locally, with the shared world moving safely between them. The game still needs a host while people are playing. There is no sorcery here, and no tiny goblin maintaining your Valheim map at 3am. The difference is that you are not paying monthly for an always-on box just to make ownership less annoying.
For games built around host-and-play sessions, this can be a much better fit. You launch the game, host from your PC, friends join, everybody logs off, and the world is handed to the next trusted player when it is their turn. The key word is safely. Passing a save through Discord, Google Drive, USB sticks, or a folder called `FINAL_final_USE_THIS_ONE` is not a system. It is a hostage situation with extra steps.
When serverless multiplayer beats a dedicated server
A dedicated server earns its keep when people play at wildly different hours, need the world online constantly, or want a public community with dozens of players. If your Minecraft realm is effectively a small town, leave it running. Nobody wants to schedule access to the town square.
But many co-op groups do not play like that. They play on Tuesday nights, perhaps a bit on Sunday, then disappear for two weeks because work, school, holidays, and the unstoppable gravitational pull of a new release happened. Paying a recurring server bill for that pattern can feel like renting a cinema just in case three friends fancy watching a film.
Serverless co-op makes sense when your group has a few regular players, trusts each other with the world, and only needs one host at a time. It is particularly useful for games where a local save already contains the whole world: Stardew Valley farms, Factorio factories, Satisfactory builds, Palworld worlds, modded survival saves, and emulator save files.
The money story is refreshingly simple. A free plan that is actually free is useful. Paying once for more storage and keeping it forever is better than another subscription nibbling at your bank account. No rented server to forget cancelling. No mysterious price rise because a hosting company discovered the word “community”. No “powered by AI” sticker slapped onto a sync button for reasons known only to marketing departments.
The real challenge: the save is the server
With a dedicated server, the world lives in one place. With serverless multiplayer, the save file becomes the thing that must be protected and controlled.
That creates three ways a great co-op world can die embarrassingly. First, two people launch different copies of the same save and make conflicting changes. Second, someone copies an older version over a newer one because the filenames are a cursed archaeological dig. Third, a game crash, mod update, or power cut damages the active save and leaves the group debating whether the last six hours were ever real.
A proper serverless setup needs more than cloud storage. It needs version history, clear ownership, and a way to stop simultaneous edits. Cloud folders are excellent at synchronising files. They are much less excellent at understanding that two people independently building factories in the same world is a conflict, not a collaboration feature.
Version history is your rollback button
Every meaningful save change should create a recoverable point in time. That means you can roll back the mod update that ate your NPCs, the accidental chest clear, or the session where someone “tidied up” and demolished the wrong half of the base.
This matters even more with modded games. A modpack is not a stable ecosystem. It is a Jenga tower made from dependencies, load orders, hotfixes, and one mod author deciding that version 2.4.1 needs a total inventory rewrite. Keeping older versions of the save means a bad launch is a problem, not an obituary.
One world, one active editor
The most valuable rule in serverless co-op is painfully unglamorous: only one person should hold the active world at a time.
A lock-based handoff enforces that rule without asking your group to remember it. One player checks out the save, hosts the session, and later releases it for the next person. Everyone can see who has it and when it last changed. Expiring locks are useful too, because every group contains at least one person who vanishes mid-campaign and leaves the save trapped on a laptop until the heat death of the universe.
This is where Checkpoint64 fits the job neatly. It watches supported save folders, checks for changes every 30 seconds, uploads only what changed, keeps prior versions, and uses server-enforced locks for co-op handoffs. In normal human language: the world follows the group, not whichever friend happened to host it first.
A practical serverless multiplayer routine
You do not need a ritual circle of backup drives to make this work. You need a boring, repeatable routine. Boring is good. Boring saves worlds.
Before a session, the intended host takes the current shared save and confirms they hold the lock. Everyone joins as normal through the game’s own multiplayer tools. After the session, the host saves and exits cleanly, waits for the new version to upload, then releases the lock. The next host starts from that latest version rather than from a local mystery copy.
Add one extra habit for modded games: agree on the modpack version before launching. Save sharing cannot rescue a world opened with the wrong mods, missing dependencies, or a different game build. It can restore the damage afterwards, which is lovely, but avoiding the damage remains cheaper on the blood pressure.
A shared logbook also helps more than it sounds. Leave a note when you update mods, beat a major boss, rebuild a base, or finish a risky migration. When someone asks, “Which version was before the bee incident?”, you will have an answer that is more useful than scrolling through timestamps and regret.
Where serverless multiplayer falls short
This approach is not a universal replacement for dedicated hosting. If players need access while the usual host is asleep, at work, or offline for a week, a server is still the clean answer. The same goes for large worlds with many concurrent players, persistent economy servers, public access, or games that require a dedicated process for their multiplayer features.
Your upload speed also matters. A giant world with frequent, chunky save files may take time to move between players, especially on slower broadband. Incremental uploads help, but physics remains annoyingly committed to being physics.
There is also a social trade-off. Serverless co-op works best with a defined crew. If your group cannot agree who hosts next, cannot stick to one modpack, or considers “I think this is the latest file” acceptable documentation, a dedicated server may be worth the cost purely as a peace treaty.
The better question is not “server or no server?”
The better question is: how often does your world genuinely need to be online, and what happens when the person holding it is not?
For a small group that plays together, serverless multiplayer can cut the rental bill without returning to the bad old days of save files passed around like contraband. Keep every version. Hand the world over deliberately. Make rollbacks quick enough that one disastrous session becomes a story, not the end of the campaign.
Your co-op world is not disposable. Treat it less like a temporary download and more like a cartridge shelf: labelled, protected, and always ready for the next person to pick up.