Games Like Cloud Arch Simulator

Build systems that don't fall over.

Your blog just went viral. In four minutes, traffic spikes 50×. Your architecture is one server wired straight to a database — and it is about to collapse in front of everyone. Cloud Arch Simulator is a reverse tower-defense puzzle for people who actually build software. You inherit a broken cloud architecture, figure out why it dies under load, and redesign it before a timed traffic surge — and a chaos event — decide whether you were right. Then you learn to size the next one before you build it. No fictional tech. No hand-waving. Real patterns, real tradeoffs, real consequences.

The loop

First size it. Then build it.

Real architecture starts before the diagram — with a napkin. Estimation contracts hand you a product in plain words ("eight million users, six sessions a day, fifteen images a feed") and make you derive the numbers everything else hangs on: peak requests per second, read/write ratio, storage growth. Lowball the estimate and you under-provision — then the real traffic arrives and buries you. It's the half of the job that happens before the first server: the back-of-the-envelope that separates engineers who can start a design from those who stare at a blank page.

Real architecture, real tradeoffs

Every component behaves like its real-world counterpart:

Your canvas is infrastructure-as-code, both ways: edit the diagram and the YAML updates live — edit the YAML and the diagram follows.

Watch it hold — or burn

This isn't a spreadsheet. A CRT-oscilloscope readout traces your latency in real time, data-pipe cables pulse with live traffic, overloaded nodes spark and redline, and a three-stage alert system (Yellow → Red → Collapse) screams as your SLA breaks. A correctness readout flags the requests that came back wrong even when nothing technically "failed" — the stale read that passed every health check. Your budget drains by the second while you're down. Every design decision is legible at a glance.

A career of 25 contracts

Climb from Junior Dev to Tech Lead to Principal Architect across 25 scenarios drawn from the incidents that actually happen:

Mastery is optional. Passing isn't gated.

Hints are always available — tiered from a nudge to a full recipe — and every level can be finished by anyone who can read a card and watch a run fail. But S-ranks are earned hint-free, and at Principal rank the game stops being predictable: the chaos schedule shifts every attempt, the failure targets whatever hurts your design most, and redeploys start costing real money. Plan, don't grind.

Who it's for

Software engineers, SREs, students, and anyone who wants to feel how distributed systems break — and hold. You'll size a system from a one-line brief, then build it to survive the worst night of its life. If you liked untangling a system diagram at 2 a.m., this is the game version, minus the pager.