SysAdmin Crisis

SysAdmin Crisis puts you on the night shift as the only systems administrator on duty. The clock runs from 00 to 08, logs stream past, metrics drift, and things start going down. You read what the machine is telling you, work out what is actually wrong, and fix it by typing a command.

The loop is diagnosis, not selection

Most simulation games about technical work turn the work into a menu: a list of abilities, one of which is correct. This one does not. An incident arrives as a signature — a shape in the logs, a curve in a metric, a service that stopped answering in a particular way — and reading that signature is the actual gameplay.

Three things happen, in order. You read the signature. You diagnose it — confirm with top, netstat, df or db_stat whether this is disk pressure and not a memory leak, or a lock on the database and not a slow server. Then you apply the fix by typing a command.

Diagnosing it is the hard part and the part the game is about. The commands are not a puzzle to reverse-engineer; they are what you already decided to do, expressed.

Real commands

The terminal takes commands, not menu picks. The syntax is gamified Unix — close enough that the habit of diagnosing before acting carries over — and the game cannot fake difficulty by hiding which of five buttons is live this time.

You do not need to arrive knowing any of it. The shift introduces its vocabulary as it goes and never tests you on something it did not show you first.

One shift, eight hours, time that keeps moving

The clock is game time, not your time, but it does not pause while you think. Incidents queue and interact — a fix that takes a service down for thirty seconds matters if something else depends on it — and diagnosing an incident quickly earns a speed bonus, but nothing here is testing your reflexes. This is a game about being right under pressure, not about beating a stopwatch.

A single shift is one sitting, about ten minutes. It ends at 08, unless an SLA breach or a total outage ends it early; what changes is how much of the estate is still standing. The campaign strings ten shifts together, and Endless mode keeps the pressure going once the campaign is done.

Same seed, same night

Nothing in SysAdmin Crisis is randomised behind your back. Which incident arrives, and when, comes from a seed: replay a shift and you meet the same incidents in the same order, on any device. A given signature has a given cause, so an incident you misdiagnosed is one you misread, not one that rolled against you — and the second attempt is worth something.

Where it runs

It opens in a browser: no installer, no launcher, no account. iOS and Android builds run the same engine and are waiting on store release; until then it plays in your phone’s browser too. The web build is statically exported with no server behind it — which, for a game about servers, is worth saying plainly: there is no backend to go down, no connection to drop and no account for anyone to close.

Nothing is collected: no accounts, no telemetry, no analytics, no crash reports. Your progress and settings stay on your device. The studio page explains why all three games share this shape; the privacy page states the claim in checkable terms.