Code Lab: a real browser development environment for every student
Students open a project, edit files and run code in the browser, then submit it for grading. Hidden tests check whether their code works, and faculty track attempts and scores by batch.
Work in Python, Java, Node.js, C/C++, Go, SQL and web stacks.
2,500+ projects across tracks
A ready catalogue of practical projects across programming, data, web, databases, DevOps, testing and security tracks, from beginner labs to multi-file builds.
- Assign catalogue labs to any cohort
- Duplicate and adapt a lab for your syllabus
- Starter files, tests and solutions kept separate
Hidden tests check whether the code works
Each lab runs in an isolated sandbox. Hidden tests check the submitted code for correctness, and faculty see attempts, scores and progress per cohort.
- Isolated, hardened sandbox per session
- Hidden-test grading and attempt history
- Contests and challenges with leaderboards
Everything included
Browser IDE
Editor, file tree, search, run, test cases, output and a real terminal.
Custom labs
Faculty create labs from a stack template; automated validation checks them before publishing.
Contests
Timed contests for a batch with snapshots and rankings.
Cohort assignments
Group labs into programmes and assign them to cohorts with deadlines.
XP and streaks
A first lab pass earns 10 XP; a contest solve earns 20 XP. The daily cap is 3 labs. XP counts towards the institution leaderboard and daily streak.
How gamification worksCommon questions
Do students need to install anything?
No. Everything runs in the browser, including the terminal, on any laptop with a modern browser.
Which languages are supported?
Python (including data libraries), Java, Node.js (including full-stack), C/C++ and Go, plus SQL and web projects in the practical tracks.
Can faculty write their own labs?
Yes. Start from a stack template, add starter files and hidden tests, and the platform validates the lab before you publish it.
Walk through a lab submission
See a student open a project, run code and submit it for correctness checks, then review the results as faculty.