CYBRARY Practice. Defend. Build. Compete.
The three questions every buyer asks, answered while you watch
Does an attempt survive a dropped connection? Does a full class stay on the same world? And what do you actually learn about a person from an hour in the range? Every number below was calculated in your browser just now by running the real thing — reload the page and it runs again.
Nobody loses their work
An attempt cut short at every possible moment, and recovered every time
We take a full attempt and sever it after step one, then step two, and so on to the end. Each time we rebuild the world from scratch and replay what the learner had done, then compare it with where they were when the line dropped.
40
Steps in the attempt
41
Interruption points tested
41
Recovered exactly
None
Work lost
Honest limit: this proves the recovery path is sound for the recorded attempt. It does not promise a learner's own network will come back.
A class of forty, one world
Everyone lands on the same state, even when delivery misbehaves
Each seat receives the same set of actions under a different kind of network trouble — backwards, jumbled, duplicated, or arriving all at once after a late join — and every seat has to finish on an identical world.
40
Seats simulated
320
Actions exchanged
40
Seats in agreement
Yes
Everyone converged
- Everything arrives in order8/8 agree
- Delivery arrives backwards8/8 agree
- Delivery arrives jumbled8/8 agree
- Every message is delivered twice8/8 agree
- A seat joins halfway and catches up8/8 agree
Honest limit: this is our own harness against our own shared-world rules. No vendor, ourselves included, has published a like-for-like benchmark against another platform.
What an hour in the range tells you
The decision trail, read back as coaching
Because Forge draws every console itself, it knows what the analyst opened, what they came back to, how long they sat before committing, and whether the action they took was supported by anything they had read. A recorded remote desktop cannot answer any of those.
5 min
Time on task
4
Pieces of evidence opened
59s
Pause before committing
0
Actions with no evidence
Clean run: every action you took was backed by something you had already read.
Why we said it: 2 correct action(s), none unsupported
What we never collect
- Keystrokes and typing cadence
- Clipboard contents
- Screen pixels, screenshots and video
- Anything on the learner's machine outside the exercise tab
- Free text the learner wrote, beyond whether a hypothesis was recorded
- Camera, microphone and location