Peridot is in pilot with its first courses. Linux and SOC analyst labs are live.Pilot a course →
For universities

Hands-on labs for every practical course, faculty by faculty.

Peridot fits the way a university is already run: faculties, departments, levels and sessions, down to the course code. Lecturers keep their syllabus; students get a lab for every chapter.

lab.peridot · student workspace
Linux lab on an Ubuntu computer
What gets in the way

The practical part is the hard part.

01

Lab rooms are full and old

A practical class needs working machines for every student, every week. Most departments can’t keep that up.

02

Large classes, few TAs

With hundreds of students per course, marking practical work by hand takes weeks.

03

Accreditation asks for evidence

Reviewers want to see what students can do, not only what they scored on paper.

How Peridot fits

Built around how universities work.

University → faculty → department → level and session → course. Unit admins run a faculty or department; lecturers and TAs are added per course.

HOW YOUR ORGANISATION IS SET UPexample
Example structure for a universityUniversityFaculty of ScienceFaculty of Mgt. SciencesComputer ScienceAccounting100 level · 2026/27200 level · 2026/27CSC 111ACC 201

Mirrors your structure

Faculties, departments, levels (100 to 500) and sessions (2026/27). Courses keep their codes, like CSC 111 or ACC 201.

Works on student laptops

Nothing to install; it works on campus Wi-Fi or at home.

Marks with evidence

Every mark keeps what the check found, ready for moderation and external examiners.

Reports to your systems

Results go to your portal or LMS by API, or as a spreadsheet for the exams office.

Roles

Everyone sees what they need, and no more.

Five roles cover every organisation. Names stay the same everywhere, so a lecturer at a university and a trainer at a company use the same screens.

RoleWho it usually is here
Org adminRegistry or ICT. Sets up faculties and departments, connects systems.
Unit adminDean’s office or HOD. Adds lecturers, sees every course in the unit.
LecturerOwns a course. Reviews labs, watches progress, moderates.
TAHelps a group. Sees who is stuck, answers questions.
StudentDoes the labs and tests, asks the tutor.
Results

Results go where you already work.

By API, webhook or spreadsheet. Peridot never asks you to move your records.

Results in your systems
  1. 01

    Work is checked

    A step, a lab or a whole chapter test.

  2. 02

    Your systems hear at once

    A webhook the same minute, with the score and evidence.

  3. 03

    Gradebook and HR stay current

    Your LMS, gradebook or learning system, unchanged.

  4. 04

    Read any time

    The results API, or a spreadsheet for the exams office.

Rolling it out

Start small. Grow when it works.

  1. WEEK 0

    One course

    Pick a course with a practical side and a lecturer who wants it.

  2. TERM 1

    Pilot

    Labs built with the lecturer, used by one class, results reported.

  3. TERM 2

    The department

    More courses in the same department, with a unit admin.

  4. YEAR 2

    The faculty

    Faculty-wide, connected to your portal.

Questions

From universities

Can we use our own course material?

Yes. Send the syllabus and whatever you teach from. The engine drafts labs from it, and your lecturer reviews them before students see them.

How do students sign in?

Today, by an invitation link or a roster upload. Single sign-on with your identity provider is coming.

Does it work with large classes?

Yes. Every student gets their own computer in the cloud, ready in seconds, whether the class is 40 or 4,000.

Pilot

Send us one course. Get labs back.

Pilot Peridot with one course for one term. We build the labs with your staff, and you see every result.