# Neurologyca DevLab: Deferred (server-side) · Preview > The pages of this path, in reading order. The index of every page: https://devlab.neurologyca.com/docs/llms.txt # Deferred (server-side) **Preview** > Preview: server-side processing is Neurologyca's processing service, the only option today; running it yourself comes later. The manifest may change. Use it only with people who have given their informed consent; the Data Processing Addendum (DPA) your organization accepts with the DevLab Terms covers it. The SDK records the video and a step manifest and uploads them; our processing service handles them shortly after. It is not hours later: it just doesn't run on the device. [See the example in the playground](/playground#deferred). ## The loop at a glance Browser (createRecordingClient → uploadRecording) → Your receiver (createUploadReceiver.onComplete) → Your backend (submit to the service) → Processing service (Preview) → Back to your backend (token URL while it runs · webhook / getJob) → interpreting → succeeded (read /results + interpretation) Processing is Preview. Answer the webhook 2xx fast and do the work after; stop polling at succeeded or failed. 1. **Page** — `createRecordingClient`, the same step loop as on-device; `session.stop()` gives the recording. 2. **Page** — `uploadRecording(recording, { url })` uploads it in chunks and deletes the local copy only after your receiver confirms. 3. **Your backend** — your receiver's `onComplete` signs a URL for the video and submits the job to the processing service. 4. **Your backend** — the service replays the capture against Engine (transcribing the recording and passing to Engine only the text of the steps the job asks for) and tells your webhook; poll `getJob` if it does not arrive. Answer the webhook `2xx` fast and do the work after, and **stop polling once the job is `succeeded` or `failed`**. ## The mode at a glance | Topic | Deferred (server-side) · Preview | | --- | --- | | Today | You can record, upload and process with Neurologyca's processing service: nothing to deploy. | | Where it runs | On our processing service, shortly after the upload. It is not hours later: it just does not run on the device. | | When the results arrive | Minutes after the upload, adding three stretches: the upload (about 7 min for 3 min of video at 1.75 Mbps, a calculation), the queue (one job at a time) and the processing, somewhat longer than the video itself. | | What leaves the device | Video and audio (with the camera, the microphone is always on) to your receiver, and from there to the processing service, which, with transcription on, transcribes the whole audio of the recording and passes to Engine only the text of the steps the job asks for (`transcribeSteps`). The raw audio identifies a person more than numbers do, and the manifest that travels with the video holds the full `userAgent` of the browser. | | What limits you | Upload bandwidth. At 4 Mbps, 3 min of video are about 93 MB (about 310 MB per 10 min). The upload resumes after a cut. The quality depends on the recording's bitrate and the light, not on the device's power: the processing runs on the server. | | Browsers and phones | Records MP4/H.264: desktop Chrome and Edge, Chrome on Android and Safari on iOS. An iPhone records MP4 too: its file can end about 1.1 s before the stop, which is why the SDK keeps recording 2 s more. On a phone or a tablet it records in portrait: it waits until the device is upright. | | Measurement | Yes, since 0.27.0: `triggerAnalysis: false` travels in the manifest and the processor does not call `/analyze`. | | Typical cases | A ten-minute interview on a modest phone; a field session on a weak device, uploaded later. | | Moving between them | Add the receiver to your backend (`createUploadReceiver`); record from the camera, a `