Beacon Command
Run a deep-space station: dock the ships, route the signals, survive the surprises. Then flip one switch — and discover you’ve been doing real systems engineering the whole time.
Opens in a new tab — runs in your browser, nothing to install, no account. Progress saves on your device.
About Beacon Command
A game first
Ships queue for docking, relays go quiet, storms knock out half the station. You balance traffic, activate reserves, and decide what survives when there isn’t enough to go around. No technical background needed — if you can reason about a busy harbor, you can run Meridian Station.
Two views, one truth
Every mission runs the same simulation twice-labeled. In Adventure View it’s docking bays and holding patterns; switch to Ops View mid-game and the exact same situation becomes load balancers, queues, and SLOs. Nothing resets — only the language changes.
Real concepts, earned
Capacity headroom, load balancing, dependency latency, retry storms, canary deployments, failover, graceful degradation, rate limiting — each learned by living through it, not reading about it. Eighteen concepts, five hands-on sandbox labs, and a library that fills in as you play.
Adventure View
“Too many vessels are being directed to Docking Bay Alpha while Bay Beta sits nearly empty.”
The station tells you what’s wrong in plain language. You fix it with your hands on the controls.
Ops View
“The load balancer is sending too much traffic to Instance A while Instance B is underutilized.”
Same moment, same simulation — in the words an on-call engineer would use. That mapping is the whole point.
Long Watch
When the missions run out, the station keeps running. Long Watch is an endless roguelite on the same simulation: procedurally generated waves that escalate until they beat you, and a station you rebuild between every one of them. It is the mode you play once the concepts have stopped being new — and it is available from the very start.
Choose a doctrine
Open as Freight Line, Bulwark, or Signal Corps. Each hands you a different station, discounts a different kind of upgrade, and is scored on a different thing — volume moved, integrity held, or response time.
Requisition between waves
Survive a wave, draft your next advantage: more modules, caches, buffers, rate limiters, batch processors, second-stage pipelines. Three of a kind unlocks a keystone, and every keystone you install makes the next one dearer.
Something is reading your station
An adaptive adversary studies whatever you just built and goes after its weakest point — the single module you never doubled, the dependency everything routes through. Always telegraphed, never random, and past a certain depth the damage stops being temporary.
Spend the error budget
Integrity is the run’s health bar and it is literally the error budget: every request you lose burns it, clean waves earn some back, and at zero the watch is over. Every run is seeded, so the recap you copy is one somebody else can replay exactly.
Five minutes to your first incident
A built-in tutorial walks you through your first watch. Whether you’re an engineer who wants to show someone what you actually do all day, or you’ve never heard of an SLO — the station doesn’t care. It just needs a coordinator.
▶ Take the Watch (opens in a new tab)