Sessions, risk, the review queue, languages, integrations and the audit trail — without opening six tools.
Interface illustration, not a screen capture. A drawing of the console dashboard — live sessions, the review queue, risk for the day, question bank, languages, reporting, webhooks and the audit log. Figures are one institution's illustrative day, not platform throughput.
How it works
AI flags. A person decides.
Every step to the threshold is automatic. Nothing past it is.
Detection produces evidence, not verdicts. A person records the decision, with a reason — and the candidate can appeal it.
The Platform
Everything an exam needs.
Author once
Versioned items, pooled papers, published before use.
Deliver anywhere
A link in the browser. Nothing to install.
Watch six ways
Typed detections, each with a confidence score.
Decide with proof
Evidence timeline, recorded reason, appeal.
Mark long answers
Free-text and image answers, scored with a rationale.
Push it downstream
Seven signed webhook triggers, retried and replayable.
Monitoring
Six ways we watch.
No layer decides anything on its own. A person always does.
Every code drawn here is one the platform actually emits.
How it runs
Three steps to exam day.
1
Build the paper
Sections, pools, marking rules.
2
Open the window
Invite candidates, set the proctoring level.
3
Close the case
Review the evidence, record the decision.
13 Languages
One paper. Every language.
Candidates pick theirs when the exam opens — and can switch mid-attempt.
HIहिन्दी
MRमराठी
GUગુજરાતી
TAதமிழ்
TEతెలుగు
KNಕನ್ನಡ
MLമലയാളം
BNবাংলা
PAਪੰਜਾਬੀ
ORଓଡ଼ିଆ
ASঅসমীয়া
URاردو
ENEnglish
Integrations
Connects to what you already run.
Results, violations and decisions leave the platform the moment they happen — signed, idempotent and replayable. No middleware to babysit.
Seven signed triggersAssigned · started · submitted · result published · disqualified · review completed · proctoring
A REST APIScoped by the same roles as the console.
Bulk CSV and XLSXCandidates in, results out, at batch size.
FAQ
Asked first.
No. A one-time link opens the exam in the browser they already have.
Never. Detectors produce evidence with confidence scores. A person reads it and records the decision — and the candidate can appeal.
Answers save as the candidate moves through the paper. A drop is logged as a network event, not a violation, and the session resumes on the same question.
Yes — build them from pools. A blueprint draws from a pool to generate a section, so one question bank produces as many distinct papers as you need. Each published paper is then frozen, and everyone assigned to it sits exactly that paper.
Yes — each is its own tenant, with its own users, libraries, branding and limits, on its own subdomain.