Designing ServerBound
How cybersecurity concepts became walkable neighborhoods — the design philosophy behind turning networks into a narrative RPG.
ServerBound started with a question: what if a network was a place you could walk through?
Not a visualization. Not a dashboard. A place — with neighborhoods, locals, economies, and dangers. A place where the abstract concepts of cybersecurity become tangible, spatial, explorable.
This is the design diary of how that idea became a game.
The Problem Space
Cybersecurity education has a problem. The concepts are invisible. You can’t see a packet. You can’t touch a firewall. You can’t walk through an encryption handshake. Everything happens in terminal windows and log files, and the gap between understanding the theory and developing intuition is enormous.
Games solve this. Games make abstract systems concrete. SimCity taught urban planning. Kerbal Space Program taught orbital mechanics. Factorio taught logistics and optimization. None of these games set out to be educational — they set out to be about systems, and education emerged from play.
ServerBound takes the same approach to networks and cybersecurity.
The World Wide Wonder
The core metaphor: the internet is a city. Every network is a neighborhood. Every server is a building. Every packet is a person walking through the streets.
This isn’t just flavor text — the metaphor is load-bearing. It maps directly to real networking concepts:
| Network Concept | ServerBound Equivalent |
|---|---|
| Network segment | Neighborhood |
| Server | Building |
| Packet | NPC / citizen |
| Firewall | Gate / checkpoint |
| Port | Door |
| Encryption | Language / dialect |
| DNS | Street signs / directory |
| Router | Intersection / transit hub |
| Vulnerability | Structural flaw in a building |
The player is an investigator — not a hacker, not a defender, but someone who needs to understand how the network-city works in order to solve cases. You learn cybersecurity the way a detective learns a city: by walking the streets, talking to locals, and noticing what doesn’t fit.
Four Neighborhoods
The World Wide Wonder has four neighborhoods, each representing a different aspect of network infrastructure:
The Bazaar — The commercial layer. E-commerce, payment processing, APIs. Everything is transaction and exchange. The visual language is gold and amber, busy market energy, merchants calling out to passersby (API endpoints advertising their services). This is where you learn about data in transit, payment protocols, and man-in-the-middle attacks.
The Commons — The public infrastructure. DNS, CDNs, public forums, open-source repositories. A civic space, teal and green, parks and libraries. This is where you learn about DNS poisoning, CDN cache attacks, and the trust assumptions of public infrastructure.
The Archive — The data layer. Databases, storage systems, backup services. Quiet, violet-toned, vast. Libraries that go deeper than they should. This is where you learn about SQL injection, data exfiltration, and the difference between encryption at rest and in transit.
The Underbelly — The shadow network. Dark web analogues, encrypted channels, black markets. Ash and grey, neon accents. The player goes here when the investigation demands it, not for tourism. This is where you learn about Tor, onion routing, and the ethical complexity of anonymity.
The Theory Board
ServerBound’s central mechanic is the Theory Board — a cork-board where the player pins evidence, draws connections, and forms theories about what’s happening in the network.
This is directly inspired by detective games (Return of the Obra Dinn, Her Story, Disco Elysium’s thought cabinet) but mapped to cybersecurity reasoning. The player collects:
- Packet captures (conversations overheard in the street)
- Log files (building visitor records)
- Configuration files (architectural blueprints)
- Vulnerability reports (building inspection notices)
They pin these to the Theory Board and draw connections. When they correctly identify a causal chain — “this misconfigured port allowed this packet to reach this server, which exposed this data” — the theory resolves and the investigation advances.
The Theory Board teaches causal reasoning about systems, which is the core skill of cybersecurity. Not memorizing CVE numbers, but understanding how components interact and where interactions create risk.
The Disco Elysium Influence
ServerBound uses a portrait conversation system inspired by Disco Elysium. When you interact with a server (building) or a service (local), they speak to you as characters. A firewall is a stern guard. A load balancer is a harried traffic cop directing citizens. A database is an archivist who remembers everything but shares selectively.
This anthropomorphization isn’t cute — it’s functional. By giving network entities personalities that reflect their actual behavior, players develop intuitions about how these systems work. The firewall-guard who only lets through specific types of people is teaching allowlisting. The load balancer who sends citizens to different offices based on their request type is teaching routing algorithms.
Data Packets as Currency
In the World Wide Wonder, data packets are currency. Information is literally the medium of exchange. This mirrors the real internet, where the fundamental unit of value is data — your attention, your preferences, your behavior.
The player can observe how data-packets flow through the city: which buildings collect them, which neighborhoods generate them, where they accumulate. This makes visible the economic structure of the internet — the attention economy, the data brokerage industry, the surveillance apparatus — through spatial observation rather than lecture.
What’s Next
ServerBound is currently in pre-production, targeting Steam Next Fest in October 2026. The Bazaar neighborhood is the first playable area, with the Theory Board mechanic as the core loop.
The game’s development is being documented here in the garden. Follow the connections to see related thinking on packets, network infrastructure, and the intersection of games and systems thinking.
This essay is part of an ongoing series on game design process. It will grow and change as development continues.