Department pilot
One department, one course, one semester.
- Up to 150 students
- Installation on your hardware
- Full lab catalog and guided courses
- Faculty onboarding session
- End-of-term usage review
Lab infrastructure for universities
Every student in the section gets their own machine.
Dharun's Labs runs Linux desktops, security ranges, DevOps toolchains and databases for a whole class, in the browser, from servers your university controls. Nothing to install on lab PCs. No shared logins. No student breaking another student's work.
- Self-hosted on your hardware
- Works in any modern browser
- Accounts issued by your administrators only
Accelerated for the demo
0/72Seats ready
0Starting now
0Private networks
Select any seat to inspect that student's machine.
- 40lab environments, one click each
- 7guided course tracks, 21 graded labs
- 6managed databases and queues
- 1private network per student
- 0installs on lab PCs or laptops
Who it's for
One platform, four people who have to say yes.
A lab platform gets adopted when the department, the faculty, IT and the students all get something they need from it. Pick a role to see what changes for them.
Today
With Dharun's Labs
Lab catalog
40 environments your syllabus already names.
Each lab is a full working tool in a container the student owns, capped at 2 vCPU and 4 GB. Your administrators decide which batches can see which labs.
Guided courses
Graded inside the student's machine, not from a screenshot.
Each course runs in a timed, disposable container. "Check my progress" runs the verification inside it, so a pass means the work is actually done. Progress and badges stay; the machine is wiped at the end.
Timed challenges
Something is broken and the clock is running. No hints, no partial feedback, personal best only.
- Deploy Blockedbeginner · 15 min
- The 3 AM Pageintermediate · 20 min
- Docker Won't Startadvanced · 20 min
Files, Permissions & Ownership
Linux Fundamentals
44:12
Task 1 of 6 · try it
Survey the damage and create a releases directory
The deploy script for the service in /srv/app fails because it has nowhere to put new releases. Look around, then create /srv/app/releases.
Type a command and press Enter. Try ls /srv/app.
Hints come one rung at a time. The explanation of why the step matters unlocks only after the check passes.
Assessment
Attack ranges and CTF events for security electives.
Ranges are multi-machine networks with no route to the internet. The internal segment can only be reached through the compromised DMZ host, so students have to pivot for real.
CTF events
Static or per-student flags, dynamic scoring, first-blood bonuses, hints that cost points, and teams. You choose how much of the scoreboard students see.
- After-action report for every event and range
- Events authored in the admin console
- Separate from graded courses
For your IT office
Built to get through a security review.
You are giving hundreds of students root on machines inside your network. These are the controls that make that a reasonable thing to do.
Everything runs on infrastructure you control. Student accounts, work and progress are stored in your database, on your servers.
RefControlStatus
Sizing
How much hardware does a cohort need?
A first estimate for your IT team. Set your largest concurrent class and the kind of labs it runs. We confirm the final sizing with you during scoping.
Estimated capacity
0vCPU
0GB memory
0GB disk
Based on typical average load per seat, not the per-lab cap of 2 vCPU and 4 GB. Disk covers persistent student home directories and lab images.
Rollout
From first call to a running course in one semester.
The pilot is sized to one course so your faculty can judge it on real teaching, and your IT team can judge it on real load.
- Week 1
Scoping
Courses, cohort sizes and the hardware you have. You get a sizing and a pilot plan.
- Week 2
Installation
Installed on your server with your IT team. Lab images are built on site.
- Week 2
Accounts & groups
Class lists imported in bulk. Groups decide which batch sees which labs.
- Weeks 3–16
Pilot course
One course, one semester, with onboarding for the faculty who teach it.
- End of term
Review
Usage, completion and challenge data, then a decision on campus rollout.
Engagement
Start with one course. Grow to the campus.
Pricing is per enrolled student per semester and quoted after scoping, because hardware, cohort size and support needs differ between institutions.
Campus licence
Every department, every course that needs a lab.
- Unlimited courses and cohorts
- Group access per batch and programme
- CTF events and attack ranges
- SSH access and optional AI assistant
- Priority support during exam weeks
Multi-campus
Several campuses or a university consortium.
- Separate installs or a shared deployment
- Shared curriculum across campuses
- Custom labs and courses built with you
- Named technical contact
- Annual curriculum planning
Questions
What procurement and IT usually ask.
Where does it run?
On servers your university controls. A department pilot needs one Linux machine with Docker. Larger rollouts add machines as usage grows. We install it together with your IT team.
Do students need to install anything?
No. Every lab opens in a browser tab, on lab PCs or personal laptops. Students who prefer a local terminal can connect with their own ssh, scp or VS Code Remote through one gateway port, if your IT team turns it on.
Does it need internet access?
Lab images are built during installation. After that, labs run on your campus network. Attack ranges and the Docker and Kubernetes courses have no internet route by design, so they behave the same on a restricted network.
How are student accounts created?
Your administrators create them in a separate admin console, one at a time or in bulk from a class list. Students sign in with their university ID and a password. There is no public signup, and the student-facing site has no admin functions at all.
What happens to student work at the end of a semester?
Accounts are deactivated, never deleted. Labs, files and progress are kept and come back intact if the account is reactivated for the next course.
Can we limit which labs a batch can open?
Yes. Groups decide which labs, courses and services each cohort can use. Locked items can be hidden or shown greyed out, and they cannot be started either way.
Can faculty add their own labs?
Faculty can assemble custom lab stacks from a curated set of components. New lab images and guided courses are built with you as part of a campus or multi-campus engagement.
Is there AI in it?
There is an optional assistant, off by default. It answers questions and suggests actions, but only the student's click runs anything, with the same permissions as the rest of the platform. Spending is capped per student and per installation, and timed challenges get no help.
Campus pilot
Run one course on Dharun's Labs next semester.
Tell us about the course and the cohort. We come back with a sizing estimate and a pilot plan your department and IT team can review.
- A 45-minute scoping call with your faculty and IT
- Hardware sizing for your actual cohort
- A pilot plan with dates and success measures