
A healthcare voice AI agent’s intake call usually leaves its transcript, recording, consent, and clinical data in separate services, each with its own format and IDs. We built a telehealth intake agent on LiveKit that writes all of it into one signed, portable vCon, a conversation record

Building a telehealth platform starts with a video call, scheduling, and a patient portal, and those follow established engineering patterns. The harder engineering comes from healthcare regulation. Each rule that governs a remote visit becomes a requirement the software has to meet. The platform has to know

We built a self-hosted video calling system for a healthcare platform client, replacing the usual “meeting link” pattern with a real phone-call flow: clinician dials, patient’s phone rings, patient answers. Highlights: Read the full WebRTC.ventures Story of Success: Self-Hosted Jitsi for Telehealth: Ringing, Answer, and Recovery Instead

STUNner is a Kubernetes-native TURN server, TURN being the relay protocol that gives WebRTC clients a public endpoint to send media through. It builds on the Gateway API to terminate TURN at a single load balancer endpoint and relay media to the pod behind it, so media-server