Parva Machina
// 03 — SYSADMIN CRISIS

SysAdmin Crisis

Terminal simulation

One shift, one terminal, servers going down.

SysAdmin Crisis is a terminal simulation that runs in the browser: a single night shift from 22:00 to 06:00, played by reading the symptoms in the logs, diagnosing the incident and typing a real command to fix it. The campaign strings ten shifts together and branches on the mail you answer, toward one of seven endings; nothing is randomised behind your back — the same seed and the same choices produce the same incidents in the same order on every replay.

real commands22:00 – 06:00web · iOS/Android soon
Play in the browser
nightshift — 03:1203:11:42 [lb-01] 4200 req/s — latency 2.1s03:11:45 [web-02] cpu saturation (94%)03:11:51 [web-03] DOWN$ tail -n 200 access.log
Genre
Terminal simulation
Platforms
Web (browser) — iOS and Android coming soon
Price
Free — no ads, no in-app purchases
Languages
English, Turkish, Spanish, Simplified Chinese, Brazilian Portuguese, German, French

Last updated: November 22, 2026

SysAdmin Crisis puts you on the night shift as the only systems administrator on duty. The clock runs from 22 to 06, 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 symptom — a shape in the logs, a curve in a metric, a service that stopped answering in a particular way — and the logs show the symptom, not the cause. Reading it is where the gameplay starts.

Three things happen, in order. You read the symptom. You diagnose it — move to the right host with ssh and 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. It is a small Unix shell — real flags, pipes, redirection, ssh between hosts — with short aliases for the common fixes, so 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 first night is a guided tutorial that teaches the method, and man and hint are one command away.

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 resolving an incident inside its SLA scores more than resolving it late, 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 06, 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; Endless, open from the first launch, drops the night count and keeps raising the pace until you fall.

Between nights, mail arrives. How you answer it — and how well you hold the fleet — changes which incidents the next nights bring, which tools open up and how the campaign ends: there are seven endings, and a player who never answers a single mail still reaches one.

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 with the same seed and the same choices and you meet the same incidents in the same order, on any device. Red herrings are part of the design, but nothing rolls against you: an incident you misdiagnosed is one you misread — 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.

It plays in seven languages — English, Turkish, Spanish, Simplified Chinese, Brazilian Portuguese, German and French. Command names and program output stay in English in every language, as on a real terminal.

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.

Common questions

Is SysAdmin Crisis free?
Yes. No price, no ads, no in-app purchases and nothing locked behind a payment.
Are the commands real?
Yes, within a simulation. You work in a small Unix shell — ssh into a host, read /var/log with tail and grep, pipe the result through sort and uniq, then act with real commands such as iptables or systemctl, or with the short aliases (block_ip, restart) that do the same thing. Nothing touches a real machine.
Do I need to be a sysadmin to play it?
No. The first night is a guided tutorial that teaches the method — find the host, read the log, filter it, name the cause — and man and hint are one command away.
How long is a shift?
One night, 22:00 to 06:00 in game time, about ten minutes at the table. The campaign runs ten nights back to back; Endless mode, open from the start, has no morning to reach — it runs until the fleet falls, and the score carries across shifts.
Does it work offline?
Yes. After the first load it runs fully offline, in airplane mode too. Online, the only traffic is the page checking its own origin for an update — never an analytics call, an account check or a third party. Which is a little funny for a game about infrastructure, and entirely the point.

More from the studio

01

SilkWard

Turn-based puzzle

A caravan leader tracing a lost sibling along the Silk Road. Every level is a single-screen isometric diorama: you take one step, the enemies take one deterministic step.

About the game
FOG
02

Regnarium

Short 4X strategy

For the player who wants a 4X but does not have six hours: explore, expand, exploit and exterminate on a 480-hex map. Combat is diceless — the preview you see before attacking is the actual calculation.

About the game