Our Apps

Our Apps · Game Suite

Learn the stack by playing it

Real commands, real failure modes, and a reset button: six games that turn the tools you run every day into muscle memory. No dry manuals, no damage to production.

Explore the games See how it works

Developer previewLevels are being built in the open — new missions land regularly.

Attract-mode console screen listing the six game missions with a press-start prompt

The suite

Six games, six real skills

Each game covers one area the job keeps asking for, and each mission is a working system that needs you to fix something.

Console-style mockup of Pipeline Patrol: build, test, ship, and observe stages with a failing test stage
01 / DevOpsLevel 1 · Starter

Pipeline Patrol

Read a failing pipeline, find the stage that broke, and ship the fix.

Build stages · logs · deploy gates

Console-style mockup of Exception Dungeon: a Python traceback puzzle with a clue panel
02 / PythonLevel 2 · Explorer

Exception Dungeon

Read a traceback, patch the bug, and get the script green again.

Tracebacks · types · input validation

Console-style mockup of Token Tycoon: a prompt box with context, temperature, and top-p meters
03 / LLM inferencingLevel 2 · Explorer

Token Tycoon

Tune temperature, top-p, and context until the model answers well.

Temperature · top-p · context windows

Console-style mockup of Protocol Quest: tool servers wired to a model with a tool-call log
04 / MCPsLevel 3 · Operator

Protocol Quest

Register tool servers and watch a model call them over MCP.

Servers · tools · call results

Console-style mockup of Harness Workshop: a local model cartridge beside VRAM budget and throughput meters
05 / Local harnessesLevel 3 · Operator

Harness Workshop

Load a quantised model locally and keep it inside your VRAM budget.

Quantisation · VRAM · tokens per second

Console-style mockup of Squad Select: planner, builder, and reviewer agents with energy bars
06 / CoworkersLevel 4 · Architect

Squad Select

Brief a crew of AI coworkers and split the work without collisions.

Briefs · handoffs · peer review

How it works

Play it, break it, fix it

Reading documentation teaches you the words. Poking at a live system teaches you the reflexes — what to check first, what to leave alone, and what breaks when you turn one knob.

Step 01No setup

Pick a mission

Start where you are: a penguin-simple pipeline, a thorny traceback, or a prompt that needs tuning.

Step 02Sandboxed

Break things safely

Every puzzle runs on a throwaway system. Run real commands, flip the wrong switch on purpose, watch what happens.

Step 03Scored

Ship the habit

Short missions, scoreboards, and replays turn one-off fixes into reflexes you use on the job.

Why games

Because the job is learned by doing

Production is a terrible classroom: the feedback is slow and the stakes are high. Games give you the same problems with a reset button.

Operator-first

Built for admins

Everything you practise maps onto a tool you already run: CI pipelines, Python, inference servers, MCP tool servers, and local harnesses.

Bite-sized

Missions, not manuals

Each level fits in a coffee break and teaches one concept properly, with a scoreboard that shows what actually stuck.

Failure is free

Safe to get it wrong

Mistakes cost a mission, not an outage. Replay any level until the fix feels obvious.

Ready, player one?

Start with one mission today

Pick any game above, finish one level, and see how much of the concept lands when you have to use it.

Explore the games Terms of Service Privacy Policy

Our Discord applications link to the terms and privacy pages above, so you always know what you are agreeing to.