Dev Updates

Why We Built the Servers First

Before a demo or playtest, the game needs a reliable place to run. Here’s what we built this month and why.

Posted November 15, 2026

Before we can share a demo or run a playtest, the game needs a reliable place to run. That’s what most of this month went into.

What we did

VESSELBORN runs on our own servers, in our own hands. This month we cleaned them out, gave game development its own space, and tightened security on every machine.

We also set things up so one problem can’t knock us offline. If a server goes down, another one takes over within seconds. If our whole location loses power or internet, a small backup server in another state keeps the websites up. Our work gets backed up every night to three different places, and we tested all of it by switching things off on purpose.

Why now

It’s a lot easier to get this right now than to fix it in the middle of a playtest. Doing it early means that when the demo and playtest come, our time goes into the game.

What this means for the game

New builds go up fast. The team can upload a new version of the game and have it running on a test server in a few minutes, right from a browser. Faster testing means a better game sooner.

Multiplayer tests on our schedule. We can run a test session whenever a build is ready and watch how the server handles it.

Nothing gets lost. Builds, art, music and design work are backed up every night, so one bad day can’t cost us months.

Technical details, for the curious

The hardware. Two rack servers do the main work, joined by a direct 10-gigabit link. A third, smaller server runs our team logins and keeps one of the backup copies. A small server in another state keeps a copy of the public sites and takes over if our location goes offline.

Failover. The two rack servers watch each other. Every couple of seconds they check that the sites are actually serving pages, not just that the machine is on. If the main server fails those checks, the other takes over in seconds. If our whole location goes offline, visitors are sent to the out-of-state server automatically in about a minute, and sent back home on their own once we’re back.

Backups. Every night, everything we can’t replace is encrypted and copied to three separate machines, one of them out of state. After the first copy, only changes are sent, and we keep a year of history. The copy kept out of state is encrypted, and the key never lives on that machine. We’ve tested restoring from the backups, not just making them.

Security. Every server blocks all incoming traffic by default and only opens what it needs. The websites can only be reached through a protection layer in front of them, never directly. Admin access uses keys instead of passwords and only works from inside our network. Firewall changes test themselves and undo automatically if they would lock us out.

Testing builds. The team uploads builds and runs test servers through a private web panel behind a single login. The panel can only do a short list of game server tasks, and every action is logged, so nobody needs direct access to the servers to run a playtest.

Software. Everything runs on Linux, using open source tools.

What’s next

The next update is on the way. Subscribe below to get it first, along with news about the closed playtest.

Christopher “Viceroy Tank” Cuby
Founder and Creative Director

All updates