Encrypted P2P Video Calling (WebRTC Mesh)

Direct peer-to-peer communication ensures audio, video, and screen shares do not route through or get saved on Pondchat media servers.

The WebRTC Mesh Architecture

Pondchat connects up to six peers in a mesh. Each browser negotiates DTLS-SRTP with every other peer. There is no SFU and no server-side media recording. Cloudflare TURN is used only when a direct path fails.

What Is Encrypted Where

Media: DTLS-SRTP between peers (or peer↔TURN).
Text chat: Client-side AES-GCM with a key derived from the room URL; server holds ciphertext only while the pond is occupied, then wipes it.
Signaling: Ephemeral WebSocket / HTTP relay of SDP and ICE — not a transcript store.

Limits by Design

Mesh topology favors low latency for small groups (2–6). Large webinars need an SFU; Pondchat deliberately does not become one.

Create a pond · No-signup video chat · Signaling docs