One-on-one video chat

The problem

Several customers needed reliable one-on-one video calling for healthcare consultations, support workflows, and creator-fan platforms. WebRTC reliability across NAT topologies, recording with consent, virtual backgrounds, and branded UI were not a default in any off-the-shelf SDK. Reconnection semantics were the hardest part to get right; an unreliable call dropped trust permanently.

The approach

We built a WebRTC platform with STUN and TURN fallback for NAT traversal, encrypted media streams, recording with explicit consent prompts, virtual background processing, and branded UI per customer. Reconnection logic handles partial network drops without dropping the call; latency and quality metrics surface in customer dashboards. The TypeScript control plane runs on Node and orchestrates signalling without touching media.

Stack and engineering choices

• WebRTC peer connections
• STUN + TURN fallback
• Encrypted media streams
• Consent-gated recording
• Virtual background processing
• Branded UI per tenant
• Reconnection without call drop

Outcome

Calls connect and stay connected across real-world networks. Healthcare consultations and creator-fan platforms run in production at scale. Branded UI lets customers ship video without our logo on their product, and quality metrics let support diagnose calls retrospectively.