Peaklyy Examination
Secureexams,honestscores.
Objective papers, coding rounds, and a proctoring record that an administrator can actually audit. The candidate sees the question. The server keeps the key.
18:42
Owned by the server expiration, not the laptop clock.
Score stays sealed
Keys never ship with the question.
Peaklyy integrity deskFormats
Pick the paper. Keep the rules.
Every published exam uses the same attempt lifecycle: one live session, autosave, then an authoritative result.
Objective papers
Single choice, multiple select, true or false, and short answers compared after punctuation and case are normalized.
Coding rounds
Language and SQL tasks run through the configured code runner. Hidden tests stay on the server until submission.
Integrity review
Tab switches, blur, fullscreen exits, clipboard blocks, and extra sessions land on a chronological timeline.
Cohort analytics
Pass rates, score bands, question diagnostics, and a ranking that breaks ties by time, then submission order.
The room
Built so a busy sitting still feels calm.
The palette marks answered, review, and current questions. Local state is backed up immediately, then synced. A dropped network queues the retry instead of dropping the answer.
0+
Concurrent sittings in the benchmark
0%
Scoring performed on the server
0
Answer keys sent to the browser
Method
Three steps.
Then a result.
- 01
Open an account
Students register themselves. Administrator access is issued from the seeded account, never from the public form.
- 02
Read the brief
Duration, marks, penalties, fullscreen, and the privacy notice are confirmed before the attempt clock starts.
- 03
Sit, then score
Answers autosave. When the window closes, the server evaluates the paper and locks the attempt.
One session at a time
A second tab or device is treated as another session. The attempt token has to match the one the server issued.
Escalation is configurable
Warnings come first. The exam’s flag and termination thresholds decide when a sitting moves to review or ends.
Questions
No surprises in the rules.
The attempt carries a server expiration timestamp. A changed laptop clock does not extend the paper, and a late submit is rejected.
Student question payloads leave out answer keys and explanations. Scoring runs only after submission, on the server.
Leaving the tab, blurring the window, exiting fullscreen, blocked inspection shortcuts, clipboard use, and a second live session are recorded. The exam’s own thresholds decide when an attempt is flagged or terminated.
An administrator publishes each round and can require a qualifying earlier paper. A candidate who has not qualified sees the round locked, unless an admin grants access.
The coding round uses the Judge0 or Piston endpoint configured in the environment. If neither is set, the runner reports that code execution is unavailable.