The exam hall is the worst place to depend on the internet
Every institution that has ever run a computer-based test has a story about the network going down mid-exam. A dropped connection during a live CBT session isn't a minor inconvenience — it's a disputed result, a re-sit, and a room full of students who no longer trust the process. When we designed the Examination Management System (EMS), we treated this as a hard constraint, not an edge case to handle gracefully.
EMS runs entirely on an institution's own local network. Question banks, examiner assignments, the CBT engine itself, and AI-assisted grading all execute against a server sitting inside the building, not a data center hundreds of kilometers away. There is no moment during an actual exam where a student's screen depends on an external connection staying alive.
Licensing without a permanent phone line
The one place EMS does eventually need to reach the outside world is licensing — confirming that an installation is legitimately paid for. We solved this the same way software has solved it for decades before "always-on" was assumed: a signed license token, issued once per purchase or renewal cycle, verified entirely offline by the deployment itself using a public key it already holds. The institution only needs connectivity at the point of purchase or renewal — never during actual use.
What this trades away, and what it buys back
Running offline means no live dashboard-in-the-cloud you can casually check from your phone at a conference. We accepted that tradeoff deliberately. What it buys back is something we think matters more for this specific use case: an examination process that behaves identically whether the building's internet is excellent or nonexistent that day — because it was never a variable to begin with.
