What the Game Runs On
A plain tour of the machines behind the world, and what replaces them in January.
As of today, the servers that hold the world and the servers that hold your account are both running on infrastructure we own and control. Here's what that actually means.
The pieces
| Piece | Where it lives | What it does |
|---|---|---|
| The game | In your browser, served from our site | Everything you see and play. Your Daggerfall files stay on your device. |
| The world relay | Cloudflare, one room at a time | Every player in a town or dungeon shares a room; the relay keeps them in step. |
| Accounts | Cloudflare, with a database and save storage | Logins, your identity in the world, cloud saves. |
| Voice | Not switched on yet | Deliberately off for launch. |
Why this isn't the final shape
The real backend is a Go server on our own hardware, with PostgreSQL and a purpose-built simulation kernel. It has a calendar: the first real stack in early November, two players sharing a world by the twentieth, and a load test with six and a half thousand simulated players in mid-January. Until then, the setup above is the bridge. Same game in your browser, a different set of machines on the far end.
What that means for you
Nothing you need to do. Accounts made now carry forward. When the hardware switches over you'll see a short maintenance window and a post here explaining what changed.
Next time: opening the Online door for the first players, and what they ran into.