Five questions to ask before moving computing labs into the browser

Browser-based teaching labs solve real problems: physical labs that take a term to re-image, students who can't install tools on their own machines, and practical courses that end at the door of the computer room. Having led the development of a platform in this space at Education Host, I'd still say the technology is the easy half. These are the questions that decide whether the move works.

1. How will students sign in?

If lab access doesn't use your institutional identity provider, you are about to create hundreds of orphan accounts a year. Single sign-on — Microsoft Entra ID in most UK institutions — should be a requirement, not a roadmap item. It ties access to enrolment, which is what makes the next question answerable.

2. What happens at the end of the module?

Every environment you create must have a defined end of life. Who archives student work? When do accounts suspend? Can a resit student get access back? Lifecycle is where lab platforms quietly fail: the demo shows creation, but the operational cost lives in the teardown. Ask the vendor to walk through the end of the academic year, not the start.

3. Can lecturers build and reuse their own environments?

If every new lab configuration needs a support ticket, adoption stalls at the first enthusiastic lecturer. The test is whether a lecturer can design an environment once — a Linux server pair, a Windows domain, an isolated network for security exercises — and redeploy it to next year's cohort without rebuilding it.

4. What does a cohort actually cost?

Cloud labs move cost from capital to consumption, which is only an improvement if you can see and shape it. Ask how cost maps to a module: per student, per running hour, per template. Ask what happens to idle environments overnight. A good platform makes the cost of a teaching decision visible before the invoice does.

5. Does it fit how the course is actually taught?

A browser lab that assumes every session is a tidy 50-minute exercise will fight the reality of coursework, group projects and assessments. Check the awkward cases: a student finishing an assignment at midnight, an external examiner needing access, a group sharing one environment. The platform should bend to the course, not the reverse.

The pattern behind the questions

All five questions are about operations, not features. That's deliberate. Teaching infrastructure succeeds when it survives the whole academic year — enrolment, teaching, assessment, teardown — not when it demos well in July. Whatever platform you choose, buy the year, not the demo.