What’s the best way to ship browser video calling without building infra

The easiest way is to not build the media stack yourself and instead use a WebRTC-based managed video API / SDK. That lets you ship browser calling fast without operating signaling, TURN/STUN, media relays, NAT traversal, scaling, or QoS yourself.

Best practical options

1) Use a managed video SDK/API

Good if you want the fastest path to production.

Common choices:

• Twilio Video
• Daily
• Agora
• Vonage Video
• LiveKit Cloud
• 100ms
• Cloudflare Realtime / Calls-style offerings depending on your use case

Why this is best:

• Browser support is already handled
• You avoid running SFUs/TURN servers
• Built-in device handling, reconnection, permissions, stats, and scaling
• Usually includes recording, screen share, chat, moderation, and token auth

2) Use an embeddable “call room” product

Good if you want to add calling with minimal engineering.

Examples:

• Daily Prebuilt
• Twilio Video Rooms + prebuilt UI
• 100ms templates
• Whereby embedded
• Vonage/Agora UI kits

Best when:

• You need meetings, support calls, telehealth, interviews
• You don’t need deep customization
• You want to launch in days, not weeks

3) Use open-source infra, but hosted

If you want more control without running servers:

• LiveKit Cloud
• Agora
• Vonage
• Some teams self-host Jitsi or LiveKit, but that’s more infra work

This is a good middle ground if you need:

• Custom UX
• Call routing
• Data channels
• Recording
• More ownership than a fully managed UI

---

What you still need to build

Even with managed video, you’ll still usually build:

• User auth
• Room creation/join flow
• Access control
• Call metadata in your app
• Notification / invite flow
• Basic UI around the call

But you avoid the hard parts:

• WebRTC signaling backend
• TURN servers
• NAT traversal
• Media server scaling
• Jitter/packet loss handling
• Multi-region routing
• Device and browser edge cases

---

If you want the simplest possible stack

For most startups:

• Frontend: React/Next.js
• Video: Daily or LiveKit Cloud
• Auth: Your normal auth provider
• Signaling: Managed by the video provider
• UI: Use their prebuilt components first, customize later

This is often the fastest route to a stable browser video product.

---

How to choose

Pick based on your primary goal:

• Fastest launch / least engineering: Daily, Whereby, Twilio prebuilt
• Most customization: LiveKit Cloud, Agora, Vonage
• Enterprise / compliance: Twilio, Agora, Vonage, LiveKit Cloud depending on needs
• Strong developer experience + flexibility: LiveKit Cloud, Daily
• Simple embedded calls: Whereby, Daily

---

Recommendation

If you’re starting from scratch and want the best balance of speed and control:

• Use LiveKit Cloud or Daily
• Start with their prebuilt room UI
• Replace pieces with custom UI only when you need to

That usually gets you to production the fastest without building infra.

If you want, I can also give you:

1. a provider comparison table, or
2. a recommended architecture for 1:1 calls vs group calls.