Your exam data never leaves your server: edzproctor is live

LMSProctoringAvailable now

Why we built it

Every institution that runs online exams eventually hits the same wall. The proctoring market is built almost entirely on SaaS: you send candidate webcam feeds to a third-party service, you pay per exam or per candidate, and you accept that your students' faces are processed on someone else's infrastructure in someone else's jurisdiction.

For a university running tens of thousands of quiz attempts a semester, the per-exam model alone makes proctoring a budget line that scales the wrong way. For anyone operating under India's DPDP Act — or GDPR — the data-residency question is harder still, because the honest answer to “where does the candidate video go?” was usually “abroad, and we can't tell you exactly where.”

There was also an integration problem hiding behind the pricing one. Bolting an external proctoring service onto Moodle means LTI configuration, a separate admin console, a separate report to reconcile and a separate vendor relationship to renew. It is a project, not a setting.

edzproctor removes all three problems at once by refusing the SaaS shape entirely. It is a Moodle quiz access rule — the same category of thing as a password or a time limit. It installs into your Moodle, it runs in your learners' browsers, and it writes to your Moodledata.

What it does

• Real-time violation detection, in the browser. Face absent, multiple faces, tab switching, exiting fullscreen, copy/paste, low light and camera-blocked — all detected client-side as the attempt happens, with webcam snapshots on an interval plus a burst capture at the moment of each violation.
• A Trust Score per attempt. Each violation type carries a weight; the score starts at 100 and comes down. Colour bands make triage instant — green at 80+, amber 60–79, red below 60. A reviewer opens the red ones first instead of scrubbing every attempt.
• A Live Monitor wall. A real-time dashboard of everyone currently taking the exam, sorted suspicious-first, with connection-loss detection. This is the piece that makes a large exam supervisable by one person.
• Reports a teacher will actually use. An attempt list with trust scores and violation counts, exportable to CSV, plus a per-attempt view with a violation timeline, the captured image gallery and the trust-score breakdown.
• Privacy built in, not bolted on. Explicit consent records, a default 90-day retention window with a daily auto-delete task, right-to-erasure support and full Moodle Privacy API integration.
• Optional on-premises identity verification. Face match against a base image — a photo, ID card or passport — running on your own server. No candidate biometric data leaves your network.

How to turn it on

1. Install the plugin. quizaccess_edproctoring goes in as a standard Moodle quiz access rule, then complete the database upgrade as usual.
2. Set your site-wide defaults once. Snapshot interval (30 seconds by default), retention period (90 days by default), the trust-score weights for each violation type, and whether a critical violation should auto-submit the attempt.
3. Enable it on a quiz. Open the quiz, edit its settings, and switch on edzproctor under Extra restrictions on attempts. That is the whole integration — no LTI, no external console, no keys to exchange.
4. Choose the enforcement level for that quiz. Fullscreen enforcement, mobile and tablet blocking, and whether learners see warning toasts before a violation counts.
5. Optional — switch on identity verification. Run the on-premises face-match service and collect base images during pre-flight. Candidates who do not match raise a mismatch flag rather than being blocked outright.
6. Watch it live, review it after. The Live Monitor wall during the exam window; the attempt reports and Trust Scores afterwards.

Learners get a consent screen and a pre-flight check — camera permission, one face in frame, adequate brightness — before the attempt begins, so nobody discovers a broken webcam thirty seconds into a final.

Where it fits

A university running high-stakes semester exams. The driver is usually cost shape rather than integrity alone: per-candidate SaaS pricing across a full cohort turns proctoring into a variable cost that grows with enrolment, while an on-premises rule does not.

A corporate compliance team certifying a regulated workforce. Here the driver is evidence. When an auditor asks how you know the person who passed the assessment was the person enrolled, a consent record, a violation timeline and a retained image gallery are a better answer than a vendor dashboard you no longer have access to.

What's next

On-premises identity verification is already available as an optional layer. Screen recording and a lockdown-browser executable remain deliberately out of scope.