Beyond the console

• Just reaching the lab can demand virtual machine and networking know-how before the real activity begins, especially in a local lab environment.
• Once inside, beginners face a stack of separate consoles, with little sense of what each machine is or how the systems fit together.

• Labs have to be built, maintained and updated, on top of the teaching itself.
• Explaining how devices relate, and how their physical connections shape the network, is difficult across separate consoles.
• Students collect screenshots as evidence, and educators wade through them to check that assessment requirements are met.
• A screenshot proves a task was done, not that the student understood why it worked. Quizzes that check understanding usually sit outside the lab, long after the moment it mattered.

• Activities, tools and infrastructure have to keep pace as technology moves on.
• Hosting is only part of the cost, alongside maintenance, technical support and staff time.

Learners walk into a realistic room, pull up a chair at the computer and flick through the manual on the desk. Every device has its place in the scenario, and every connection between systems is there to explore.

Plug in, trace and rewire connections, so abstract ideas become something you can see and touch. Every cable makes a real network link, so physical tasks are part of the lab too.

Every terminal and device runs on real compute and responds just as it would in production. Lightweight containers start quickly and cost far less to run than virtual machines, and students build skills they can take straight into industry.

Short quizzes pop up as learners reach each goal, checking the why at the moment it matters. Goals, timings and quiz results are collated into a report that's ready for assessment and shows which students need extra guidance.