Project
CallLink
CallLink is a lightweight, privacy-oriented web application for creating temporary links for real-time calls.
70 commits 1 contributor Updated Sep 2026
Overview
CallLink is a lightweight, self-hostable web application for temporary real-time audio and video calls. One person creates a room, CallLink returns a shareable link, and anyone who opens that link joins the call directly in a modern browser.
Rooms are intentionally ephemeral: they exist only for the duration of a call, expire automatically when idle, and are never written to a database of record. CallLink is a signaling and control plane only — audio and video flow peer-to-peer between browsers over WebRTC (or through your own TURN server when a direct path is impossible) and never through the backend. When the deployment enables external authentication, a room stays private while an authenticated participant can share a separate, expiring public invitation with a guest outside the authenticated network.
The project is privacy-oriented and small by design. It records nothing, stores no media, and keeps no user database. Optional external authentication can sit in front of it, and the whole stack runs behind a reverse proxy you control.
Why CallLink?
- A link is the whole invitation — create a room, share it, talk.
- No account, no install — participants only need a modern browser.
- Ephemeral by design — rooms and links expire; nothing persistent is kept.
- Privacy-first — no recording, no media storage, no unnecessary personal data.
- Peer-to-peer media — WebRTC media is encrypted in transit and flows directly between participants (or through your TURN server when a direct path is impossible).
- Self-hostable and lightweight — a small FastAPI service and a Next.js PWA, shipped as non-root container images.
- Scales when needed — an optional Redis-backed mode shares ephemeral state across instances.
- Open source — Apache-2.0 licensed.
Features
- Ephemeral rooms with sliding server-side expiration and bounded capacity.
- Shareable links that open the call room directly.
- Room-scoped WebSocket signaling relay.
- Multi-participant (2–4) WebRTC audio and video mesh.
- Peer-to-peer text chat over WebRTC DataChannels with replies, a searchable emoji picker, emoji reactions, and automatic history sync — session-scoped and never stored server-side.
- Peer-to-peer screen sharing alongside audio and camera, with browser stop-sharing detection and no media server.
- Chunked peer-to-peer file sharing (photos, documents, PDFs, and arbitrary files) with progress, accept/reject, cancellation, and local download — file content is never uploaded to the server.
- Post-call conversation export as plain text or versioned JSON, generated locally in the browser before the ephemeral conversation is destroyed.
- Participant presence, connection-quality, and speaking/microphone/camera indicators derived from the existing signaling and WebRTC state — no centralized presence service.
- Private rooms behind optional external authentication, and high-entropy, expiring, revocable public invitations for guests.
- Microphone, camera, and speaker controls, device selection, and hot-plug recovery.
- Configurable STUN/TURN connectivity with short-lived TURN credentials.
- Optional external authentication through trusted ForwardAuth headers (disabled by default).
- Optional Redis-backed distributed mode; single-node in-memory by default.
- English and French interface, with light, dark, and system themes.
- Installable progressive web app (PWA).
- Non-root…
Project Links
Technology
- peer-to-peer
- privacy-first
- react
- realtime
- REST API
- TypeScript
- voip
- webrtc
- websocket
Repository information
- Primary language
- TypeScript
- Created
- September 11, 2026
- Last activity
- September 28, 2026
Activity
Daily commits on the default branch, across the whole project history.