Session recording separates the frontend (web application) from the backend (session daemon). The session daemon is the backend component responsible for proxying remote sessions between the web interface and target systems. It dynamically loads support for remote desktop protocols and connects to remote desktops based on instructions received from the web application. By separating these components, session recording enables secure, clientless remote access through a browser without any additional plugins.

Component	Description
SaaS Tenant	Users launch sessions from the Britive platform.
Session Recording Service	The orchestration layer and web-based session UI deployed in the client environment. Delegates session traffic to the session daemon. Reads artifacts from shared recording storage for playback.
session daemon	The proxy and data plane. Handles the actual protocol communication (RDP, SSH, VNC, telnet, Kubernetes) and exposes the connection to the web application. Listens for TCP connections on port 4822. Writes recording artifacts to shared storage.
Shared Recording Storage	A shared volume accessible by both the session daemon (for writing recordings) and the Session Recording Service (for playback).
Target Systems	Servers and infrastructure resources accessed via RDP, SSH, VNC, or other supported protocols.