Why the call is the preview and the files are the product

Two jobs, one wire

A call has to be fast, so it gives up quality the moment the network struggles: lower resolution, fewer frames, squeezed audio. A recording has to be complete, and doesn't mind arriving a minute late. Record the call, and the recording inherits every compromise the call made.

Record where the person is

Tapry records each person in their own browser, at the studio's full quality, in four-second pieces. Every piece is written to the browser's storage on that computer before it is sent anywhere. The live call runs alongside, on 360p copies of the camera and microphone, so nothing the call does can touch what is being recorded.

“A dropped connection blurs the call but never the recording.”

Upload during the session

Pieces upload in the background while you talk, each one straight to storage through a short-lived signed link. The browser only deletes a piece once the server has confirmed it arrived. If the Wi-Fi drops, recording carries on and the pieces wait on the guest's computer; if the tab closes, they're still there when the guest opens the link again, and the upload picks up where it stopped. Uploading the same piece twice is harmless.

Meanwhile the host sees, for each person, how much has arrived and whether their upload is falling behind, so nobody has to guess whether it is safe to say goodbye.

What you get

Once you press Stop and everyone's upload is in, a worker on your server lines every track up to the moment you pressed Record, evens out the volume toward -16 LUFS without compression, and makes one WAV and one MP4 per person, a combined video and, when transcripts are on, a transcript with each speaker named. The call was only ever the preview; the files are the product.