Students learn security by doing it — hands-on, isolated lab environments that run entirely in the browser. No lab hardware to buy, no images to maintain, nothing for your IT team to install.
Now in pilot with our first institution.
Everything an institution needs to teach hands-on cybersecurity — labs, access, assessment, and hosting — in one service, run for you. Start teaching from a library of 100+ pre-built labs and tutorials — and commission more.
Structured rooms — Linux Fundamentals, Python for Security, Web Security foundations, Networking — each mixing short readings and Q&A with capture-the-flag labs that build in sequence.
Every student works in their own isolated environment, with flags generated uniquely for them. There is nothing to copy from a classmate — by design, not by policy.
Students open a full attack-box desktop right in the browser — nothing to install — or connect over VPN from their own machine and use their own tools. Their choice, per session.
Open practice any time. For exams, assessed mode locks the session down — attack box only, no clipboard or file transfer — and records it, so results stand up to scrutiny.
Progress, points, and completion for every student and room, at a glance. See who is stuck, who has finished, and what to teach next — without chasing spreadsheets.
We run, patch, and maintain the platform. Your institution gets its own branded instance on your own domain, and your students' data stays isolated on it.
Each room is a guided sequence: read a little, answer, then prove it in a live lab. Rooms stand alone, or chain into a full learning path.
The flagship learning path: staged modules that take a beginner from first login toward a complete, methodical security assessment, lab by lab. Module 1 is live now; further modules are in development.
Navigation, permissions, processes, services, and log hunting — the command-line fluency every security role assumes.
Scripting for analysts: reading files and logs, sockets, parsing, and automating a small security audit end to end.
How web applications break — and how to check yours properly — practised against deliberately vulnerable lab targets.
OSI and TCP/IP made tangible: DNS, addressing, and packet capture, investigated live rather than memorised from slides.
Images, containers, Dockerfiles, and Compose — the tooling modern labs and modern infrastructure both run on.
No infrastructure project, no lab build-out. Three steps between signing and your first student lab.
Your own platform, with your institution's branding and your domain. Labs, rooms, and instructor accounts configured and tested before anyone logs in.
Accounts are created in bulk from your class list. Students sign in with two-factor authentication — no shared logins, no passwords on sticky notes.
From day one, lessons run against real environments. Instructors assign rooms, watch progress live, and switch to assessed mode when it's exam time.
Typical onboarding: about two weeks from agreement to first student lab.
The platform arrives wearing your brand — and the content can be your curriculum, not just ours.
Your instance carries your logo, your colours, and your domain. Students sign in to what looks and feels like your own school's platform — because it is. Branding comes as standard with every deployment, never as an upgrade.
Commission rooms and labs written to your syllabus and learning outcomes. Our team designs, builds, and solve-tests each one before your students touch it — scoping starts with a conversation about your curriculum.
We train your teaching team to create labs on our templates and build pipeline, with our QA process behind them — so your content library keeps growing without depending on us for every lab.
Built for teaching budgets and teaching realities — not adapted from an enterprise product.
Our labs are written by working security practitioners and use the tools and techniques used on live engagements today. Content is reviewed on a regular cycle so it tracks the field as it changes, and no lab reaches a student until it has been solved end-to-end in testing. Students practise the current craft — not museum exhibits.
Simple per-student, per-year pricing covering the platform, labs, hosting, and support. No stack of per-seat licences quietly adding up.
The large hosted lab platforms price for corporate training budgets. We price for schools — because schools are who we built this for.
Each institution's students, progress, and recordings live on its own isolated instance. Student data is never sold, mined, or used for advertising. Ever.
Cyber-Labs is designed and run by working cybersecurity practitioners and educators — not a generic LMS vendor bolting on a security module.
Cyber-Labs.Dev is built by cybersecurity practitioners who also teach. The platform didn't start as a product idea — it grew out of a live teaching programme, where we needed students practising on real systems, safely, without a room full of lab hardware or a per-student subscription we couldn't justify.
So we built it: per-student lab environments that start in seconds and disappear when the lesson ends, flags no two students share, and an assessed mode we would trust with real exam results. It is currently in pilot with its first institution, and a Canadian company is being formed to operate it as we take on the next cohort of schools.
We are deliberately small and deliberately focused: hands-on security labs for education, done properly.
We're onboarding a small number of early institutions as founding pilots — up to around 30 students, at founding pricing, with direct access to the team building the platform. Your feedback shapes what gets built next.
Tell us about your programme — how many students, what you're teaching now, and what you'd want labs to do. We'll reply with how a pilot would look for your institution.
[email protected]