[ Early access · secure exam proctoring for certification & credentialing platforms ]

What your browser can't see,
Watchr does.

A lightweight local agent inspects the machine itself — processes, displays, virtual machines, remote-desktop tools — while the browser locks down fullscreen and tab focus. Together they catch what a browser-only proctoring tool never sees, and hand your LMS a verdict it can act on before the exam even starts.

Request early access // onboarding a limited cohort of design partners
[ The gap ]

A browser can't see what's running underneath it.

Screen recorders, virtual machines, and remote-access tools are invisible to a proctoring tool that only watches the tab. Watchr's local agent inspects the machine itself, so the gate can't be beaten by closing one window.

[ Remote desktop ]

TeamViewer, AnyDesk, RDP, VNC.

Invisible to a proctoring tool that only watches the tab — and one of the most direct ways a candidate hands the exam to someone else.

[ Second monitors ]

A newly connected display doesn't wait for check-in.

An added monitor or HDMI splitter shows up in the agent's device list the moment it's plugged in — mid-exam, not just at the start.

[ Virtual machines ]

VMware, VirtualBox, Parallels.

A sandboxed copy of the machine can't be made to look clean to a check running outside it.

[ How Watchr works ]

Three checkpoints, one continuous record.

Watchr runs as a layer over the exam you already administer — it doesn't replace your testing platform, it watches over it.

01

Gate

Before the exam starts, your LMS polls Watchr for a verdict. The agent and browser scan the machine together, and the exam only opens once the environment comes back clean.

02

Monitor

Once the exam is running, the agent re-checks the machine every 1–1.5 seconds for a screen recorder, a newly connected display, a remote-desktop tool, or a prohibited application.

03

Enforce & report

A violation blurs the exam on the candidate's screen in about a second, independent of the network — then a signed webhook tells your LMS what happened, so it can pause, flag, or record on its side.

[ Two patterns, one integration ]

Pull for the decision. Push for the events.

The gate is a blocking decision, so your LMS polls it to a terminal verdict — a dropped response just retries on the next poll. Live monitoring isn't blocking, so Watchr pushes each violation to your webhook the moment it happens.

Five states, three terminalpending → scanning → ready / blocked / expired. Blocked is resolvable — a clean re-scan moves the session back to ready.
No shared secrets in the browserYour LMS holds the API key. The candidate's browser only ever sees a per-session launch token.
A gate that can't hang foreverA configurable timeout resolves an unresponsive scan to expired, so your LMS is never left polling indefinitely.
Four endpointsCreate a session, poll its status, load the scanner, and receive one webhook callback. Nothing else to stand up.
Full API reference & OpenAPI download → 
POST /v1/exam/create-session
  → { sessionId, launchUrl }

GET  /v1/exam/status/{id}
  → pending · scanning · ready · blocked · expired

GET  /v1/exam/launch/{id}
  → scanner page the candidate loads

POST <callbackUrl>
  → gate result + live violations
  → X-Watchr-Signature: sha256=<hmac>
[ The platform ]

Everything your integrity review process needs, in one record.

System-level detection

The agent sees what the browser can't — running processes, virtual machines, remote-desktop tools, and connected displays.

Pre-exam environment gate

Your LMS polls a single endpoint for a terminal verdict — ready, blocked, or expired — and the exam simply doesn't open until the environment is clean.

Continuous live monitoring

The agent re-checks the machine every 1–1.5 seconds for the length of the exam, not just once at login.

Local enforcement, ~1.2 seconds

The exam blurs on the candidate's screen almost immediately, regardless of network conditions — enforcement never waits on a round trip.

Recoverable blocks, permanent record

A cleared violation returns the candidate to the exam. The detection history that triggered the block stays with the proctor either way.

Integrates with your LMS

A REST API and signed webhook over the exam delivery system you already run — no candidate re-registration required.

[ Built for certification bodies ]

Whoever issues the credential, you carry the reputational risk when it's faked.

Watchr is being built alongside a small group of certification and licensing bodies who administer high-stakes exams and need to defend every result they issue.

Professional licensing boardsExams that gate entry into a regulated profession, where a challenged result can carry legal weight.
Certification & credentialing bodiesIndustry credentials sat by thousands of candidates a year, often fully remote.
Corporate certification programsInternal or partner-facing certifications tied to compliance, vendor status, or pay grade.
Academic credentialing officesPlacement and equivalency exams where identity fraud undermines the credential itself.

We're deliberately starting small. Early-access partners work directly with our team to tune Watchr to their exam format, item bank, and adjudication process — not the other way around.

[ Security & data handling ]

Candidate data is sensitive by nature. We're building around that from day one.

Fail closedAbsence of agent data is never treated as a clean environment — if the agent hasn't reported, the gate blocks rather than passing.
Signed webhooksEvery push is HMAC-signed, so your LMS can verify it genuinely originated from Watchr before acting on it.
Gate timeoutA session that never resolves becomes expired, so your LMS never polls indefinitely on an agent that failed to connect.
No stale cachingSecurity-critical assets are served no-store, so a deployed fix takes effect on the candidate's next reload.
[ Now onboarding design partners ]

Join the early access list.

Tell us about your exam program and we'll reach out to set up a working session. No long-term contract to start.

Thanks — your email client should be open now. If nothing happened, write to us directly below.

Prefer to skip the form? Email morgan@watchrai.com.

[ Questions ]

Before you write in

Do we need to replace our exam platform or LMS?

No. Watchr integrates through a REST API and a signed webhook — your LMS still owns registration and delivery, Watchr only reports on the environment.

What happens when a violation is detected?

The exam blurs on the candidate's screen in about a second, independent of the network, and a signed webhook tells your LMS what triggered it — so it can pause, flag, or record on its side.

Does Watchr use a webcam or verify identity biometrically?

Not today. Watchr focuses on environment integrity — the agent and browser watch the machine, not the candidate. For high-stakes exams we recommend pairing Watchr with camera-based proctoring: a second monitor is caught, a second device is not.

What does early access actually involve?

A working session to map your exam flow, a pilot cohort of real sessions against our staging environment, and direct input into what we build next — four endpoints, not a platform migration.

[ Ready when you are ]

Ready to protect what your certification stands for?

Tell us about your exam program and we'll reach out to set up a working session.

Request early access