Proctored mock exams
Chrome-free runner, server-authoritative timer, keyboard locked, tab-switch counted. Auto-submit on expiry, instant scoring, per-question review.
Phase 1 is live — foundation shippedThe legal-education
The legal-education
operating system
for Indian law colleges.
Glimmora Rise gives faculty a question bank, a proctored exam runner, cohort assignments, and an audit-grade trail of every action. Students see only what's theirs. You see everything.
Free for early-access colleges. No card required.
In conversation with law colleges across India
- NLS Bengaluru
- NALSAR Hyderabad
- NLU Delhi
- NUJS Kolkata
- Symbiosis Pune
- Jindal
10
Indian-law subjects in scope
4
Roles with end-to-end flows
100%
State changes audited
What ships today
Foundational. Not flashy.
The boring bits law schools actually need before AI features make sense. Hardened, audited, and tenant-isolated.
Faculty-authored questions
Versioned question bank across constitutional, IPC/BNS, contract, companies, IT Act, and IP. Marks, difficulty, explanations — all first-class fields.
Cohorts that actually scale
Group students by year and section, assign exams per cohort. Students only see what's theirs. Faculty only see what they own.
RBAC at the layer that matters
Platform / college admin / faculty / student. Every endpoint role-gated, every query tenant-scoped by college_id at the dependency layer.
Immutable audit trail
Every state change writes an audit row — login, invite, publish, attempt-submit, password-reset. Filterable viewer with action, entity, role, date.
JWT with refresh rotation
Access tokens short-lived. Refresh tokens rotate on every use with family-level reuse detection. One stolen refresh, family revoked.
How it works
From contract signed to first mock exam in a single afternoon.
No procurement saga. No migration plan. Sign in, invite, publish.
- 01
Onboard your college
Your platform contact creates the tenant and a college admin. We hand over a temp password once — they're in within minutes.
- 02
Invite faculty & students
College admin invites faculty by email; faculty build the question bank and exam drafts. Students self-register with the college code.
- 03
Run mock exams · review · iterate
Faculty assigns exams to cohorts. Students attempt under proctor mode. Everyone sees scores instantly. Audit log captures the rest.
One platform · four roles
Each role sees only what they need to do their job.
Same codebase, four lived experiences — separated cleanly by RBAC.
Practice the way the bar will test you.
Proctored mock exams across Indian legal subjects, instant scoring, and per-question explanations so you actually learn from every attempt.
- Constitutional, IPC/BNS, Contract, Companies Act, IT Act, IP
- Server-authoritative timer · keyboard locked · tab-switch flags
- Per-question review with the correct option and the reasoning
- Personal scorecard history with subject-wise progress
FAQ
Questions, answered.
If yours isn't here, write to us at hello@glimmora.ai.
Indian law colleges, their faculty, and their students. The platform multi-tenants by college, so each institution gets its own users, exams, audit trail, and cohort structure.
We run a chrome-free exam shell with a server-authoritative timer, keyboard shortcuts disabled, and tab-switch counting. The faculty's pass percentage is enforced server-side at submit time. Webcam/screenshot proctoring is on the Phase-2 roadmap.
Four: platform admin (us), college admin (onboard faculty/students, view audit), faculty (author questions and exams, assign cohorts), and student (take exams, review results). Every state-changing action is audited.
Not yet. The current release ships the foundation — auth, RBAC, question banks, mock exams, cohorts, and the audit trail. AI features (legal-research tutor, drafting lab, judgment summariser) are on the Phase-1 roadmap with OpenRouter access.
Yes. Students sign up with their college's invite code. Faculty and college admins are invited by a higher-privilege role with a one-time temporary password.
Yes. Every query is scoped by college_id at the dependency-injection layer. Platform admins can cross tenants for support; nobody else can.