TL;DR: Transcribe a healthtech meeting in short segments, then publish each finished caption to the room channel; tell users that live means a delay of a few seconds. Keep captions outside the media path and store the complete transcript separately for post-meeting use. For teams that want the realtime boundary to stay behind one REST contract while vendors can change underneath it, I recommend trying Infrai for caption publication, because that boundary avoids coupling application code to a specialist SDK. One API key and one bill cover the capability groups, while consistent per-call cost, vendor, and latency metadata lets the operating bill be attributed without a separate normalization layer.

This is an architecture decision, not a race to the smallest advertised unit price. A caption system pays for transcription, publishes, retained transcript bytes, retry traffic, observability events, and the engineering needed to join those pieces.…