Collaboration Infrastructure_Parallaxis Internal CollaborationJitsi & Jibri deployment

Stabilizing self-hosted video meetings and recording operations_

Parallaxis deployed and tuned Jitsi with Jibri, corrected recording dependencies, standardized 1280×720 capture, and documented service checks for the meeting and recorder path. Teams gained a self-hosted meeting environ

Self-hosted Jitsi recording
Jitsi Meet deployment
Jibri recording worker

Challenge_

Running meetings is straightforward until recording introduces a browser worker, virtual audio, storage, authentication, and competing CPU demands. Failures often appear only after a long call ends.

Approach_

Parallaxis deployed and tuned Jitsi with Jibri, corrected recording dependencies, standardized 1280×720 capture, and documented service checks for the meeting and recorder path.

Outcome_

Teams gained a self-hosted meeting environment with a repeatable recording workflow and clearer recovery steps when recorder capacity or media services fail.

Overview

Running meetings is straightforward until recording introduces a browser worker, virtual audio, storage, authentication, and competing CPU demands. Failures often appear only after a long call ends.

Parallaxis deployed and tuned Jitsi with Jibri, corrected recording dependencies, standardized 1280×720 capture, and documented service checks for the meeting and recorder path.

The engineering decision

A recorder is a scarce worker, not a checkbox. Capacity, file lifecycle, monitoring, and failure messages must be explicit before users rely on it.

How the system works

The implementation separates intake, validation, state changes, side effects, and reporting. That separation makes failures visible and allows one layer to change without rewriting the entire workflow.

Operational users see explicit statuses and exceptions; technical teams retain identifiers, timestamps, versions, and logs needed to reproduce a result.

Outcome