The recording layer under your proctoring product.
Webcam and screen, captured in the browser for the length of an exam, with nothing for the candidate to install. AddPipe keeps the session recording alive through dropped connections and device changes, stamps it with server-side timestamps and metadata, and delivers it to your reviewers or your review engine as one mp4.
No app, no extension, no AddPipe account for candidates. SOC 2 Type I. EU and US regions.
Session streamed while recording
Recording for assessment platforms and institutions
What a proctoring recorder has to get right.
An exam recording is long, unattended, and only reviewed when something is in dispute. That sets a different bar from a thirty-second testimonial.
01Length
Two hours of webcam and screen, from a student laptop, without failing.
- Streams while recording, so nothing accumulates on the candidate's machine and there's no giant upload at the end.
- Up to 5 GiB per recording on PRO; a maximum length you set with
mrt. - Tested at 200k+ recordings a day per region, so exam-day peaks are ordinary load.
02Continuity
Wi-Fi drops, a headset unpairs, the laptop sleeps. The record has to survive it and say what happened.
- The client reconnects mid-recording and falls back to the other zone if the first refuses.
- If the connection is lost for good, AddPipe processes what was received rather than discarding the session.
- Device changes are handled live and logged; disconnected devices stay listed so the candidate can see why a feed stopped.
03Both sources
The face and the screen, in sync, in one file the reviewer can scrub.
- Screen + webcam overlay composited into a single mp4, with system audio and microphone. Screen recorder details.
- A face-positioning outline so candidates frame themselves before the exam starts.
- Webcam alone where screen capture isn't wanted, including on phones and tablets.
04Evidence quality
If a result is challenged, the recording has to stand up.
- Server-side timestamps and IP, user agent, device and codec metadata stored with the file.
- Your exam and candidate IDs attached via
payloadand returned in the webhook and REST API. - Original file kept alongside the mp4 on request; signed webhooks. See legal and compliance.
05Candidate privacy
Exam recordings are personal data of students, often minors, often across borders.
- Pin to the EU or US; the EU silo keeps everything on EU infrastructure.
- Background blurring for the candidate's room; PII controls for what's collected.
- Lifecycle rules to delete after the appeal window, Do not store to keep nothing on AddPipe.
Where AddPipe sits in the exam.
Check-in
The candidate frames themselves with the outline, picks camera and mic, and records a short identity clip if your process requires one.
Session recording
Webcam, or screen with webcam overlay, streamed to the nearest region for the length of the exam, reconnecting as needed.
Stored
Processed mp4 with snapshot and filmstrip, pushed to your bucket in the region your policy requires, or kept on AddPipe storage.
Reviewed
A webhook hands the file and metadata to your human reviewers or your analysis pipeline, linked to the exam and candidate.
What AddPipe does, and what stays yours.
Proctoring products differ in how they review. AddPipe is deliberately the part that's the same in all of them.
PipeCapture, keep, deliver
- Browser recording of webcam and screen, desktop and mobile
- Reliability through the session: streaming, reconnection, fallback, recovery
- Transcoding to one mp4, with snapshot and filmstrip
- Server-side timestamps, device and network metadata, your IDs
- Storage in your region or your bucket; retention and deletion controls
- Webhooks and REST API to hand everything to your system
YouJudgement and policy
- Identity verification against an ID document or a stored photo
- Live proctors, or automated analysis for gaze, faces and audio
- Flagging, scoring and the appeal process
- Lockdown of the exam environment
- Consent, notice and retention policy for candidates
Pipe doesn't detect cheating. It makes sure the recording your reviewers or your model needs exists, is complete, and is attributable.
Features proctoring teams use.
Your UI, not ours
Hide the native controls and drive the recorder from your exam interface through the JS control API; the events API reports every state change, including connection loss.
Whitelisted hosts
Restrict the recorder to your exam domains so your embed code can't be reused elsewhere.
Environments per client or exam
Separate settings, region, storage and webhooks per institution or assessment programme.
LMS integrations
Ready-made for LearnDash and Tutor LMS; the REST API and webhooks for anything else.
Live device list
Cameras and mics that appear, vanish or change mid-exam are handled and logged, with disconnected devices kept visible.
Logs for the appeal
getUserMedia, storage and webhook logs per recording, retained up to 31 days on PRO, longer on Enterprise.
Questions assessment teams ask.
Does the candidate have to install anything?
No. Recording runs in the browser on your exam page, on desktop and mobile. Screen capture is desktop only, since mobile browsers don't expose it.
Can AddPipe detect cheating?
No. AddPipe records the session and delivers it with its metadata. Detection, whether human review or automated analysis, is done by your product on the recording. This division is deliberate: it keeps the recording layer neutral and reusable across different review methods.
What happens if the candidate's connection drops during the exam?
The client reconnects and continues. If the connection can't be restored, AddPipe processes what was received. Both cases are visible in the logs, so a gap in the recording has an explanation attached.
How long can a session be?
You set the cap. Recordings up to 5 GiB on PRO; because media streams during the session, length mostly affects processing time, not the candidate's wait at the end.
Where are recordings stored, and for how long?
In the EU or US on AddPipe storage, or pushed to your own bucket. Retention is yours: lifecycle rules for automatic deletion, REST or dashboard deletion on demand, and a Do-not-store option that keeps nothing on AddPipe.
Can it integrate with our LMS or assessment platform?
Yes, through the embed code, the JS APIs, webhooks and the REST API. LearnDash and Tutor LMS have ready-made integrations.
Is there a security report we can review?
Yes, the SOC 2 Type I report. Request it here.
What if I need help integrating?
Contact us and an engineer will reply. For work beyond AddPipe, our custom development partners can help.
Something else? Email us.
Record a two-hour session. Pull the plug halfway.
That's the test that matters. Run it on the trial: embed the recorder, start a long take, drop the network, and read the logs. 14 days, no card required.