Beta
Start your first lab →
BlogManifestoContactStart your first lab →
labcraft.dev

Learn infrastructure by repairing real systems.

LabCraft gives engineers real Linux environments, broken states to diagnose, and validation against outcomes instead of keystrokes. The course content is executable and tested like code, so labs keep working as the tools change.

labcraft.dev/courses/nix/first-contact/01-install-nix

How a LabCraft chapter works

Run. Stumble. Carry.

Most courses hand you the happy path and call it teaching. We don't dodge the wrong turns: when a mistake teaches more than a clean run, the chapter gives you a real system, a recoverable failure, and the evidence needed to understand what happened.

Run

A live shell, yours to break.

Every command runs on real machines provisioned just for you. A lesson spins up as many as it needs, from one box to several wired into a network, and they're yours to configure, break, and rebuild.

Stumble

The mistake is the trigger.

Where a wrong turn teaches more than a smooth one, the chapter builds it in: the obvious command that quietly does the wrong thing, the config that works until it doesn't. The machine is yours alone and nothing real depends on it, so you take the risk you never would in production.

Carry

What you learned the hard way.

Fix a flake that won't evaluate once, and the next cryptic error reads differently. Each chapter assumes the judgment the last one earned you, and pushes further down the stack.

What makes it work

Three proof points behind every chapter.

01

A connected systems graph.

Courses are not isolated tutorials. Prerequisites are explicit, adjacent skills surface where they matter, and each mastered layer supports the next one down the stack.

02

Outcome validation, not keystrokes.

Labs inspect the actual state of the environment. Use the shown command, script it, or find your own route; the check is whether the system reached the intended state.

03

Content tested as code.

Lab steps are executable and tested in CI against current tools. When upstream changes break a lab, it is flagged for review before learners hit stale instructions.

Read the blog

Notes from the lab.

Start your first lab.

LabCraft is open as a public beta. GitHub, Google, or a magic link to your inbox — pick your way in.

By continuing, you confirm that you are at least 18, agree to our Terms, and acknowledge our Privacy Policy.

LabCraft · Beta · 2026PrivacyTerms
labcraft.dev