WebRTC call integration without building WebRTC

Raw WebRTC is a protocol, not a product

WebRTC gives browsers the ability to send audio to each other — and nothing else. To ship calling you still need a signaling layer (SIP or custom WebSocket), TURN and STUN servers for the ~20% of users behind strict NATs, DTLS certificate handling, echo cancellation tuning, reconnection logic, and a UI on both ends. CPaaS APIs like Twilio hand you the same work with per-minute billing on top. Most teams just want the call to happen.

The whole calling stack, delivered as a script tag

WebCallHub runs the signaling (SIP over WebSocket), the media server (Asterisk), and globally reachable TURN/STUN for you. Your integration is pasting one snippet before </body> — the widget renders, visitors click, and audio flows browser → server → your team's browser, encrypted end-to-end with DTLS-SRTP.

One-line embed

A single <script> tag works on plain HTML, WordPress, Shopify, Webflow, Wix, React, Next.js, Vue — anywhere you can paste HTML. A WordPress plugin and an npm React component are also available.

NAT traversal handled

TURN relay with automatic fallback means calls connect from corporate networks, mobile carriers, and strict firewalls — the part that kills most DIY WebRTC projects.

REST + WebSocket API

Business plan includes the API: provision agents, fetch call logs and transcripts, subscribe to call events via webhooks, or white-label the whole flow.

No per-minute PSTN fees

Calls are pure WebRTC — no phone numbers, no telecom termination charges. Plans are flat monthly prices with a free-forever tier.

What teams integrate it for

• SaaS products that want in-app voice support without building a calling stack
• Marketplaces connecting buyers and sellers by voice without exposing phone numbers
• Agencies adding click-to-call to client sites in minutes instead of sprints
• Support teams replacing a Twilio integration and its per-minute bill
• Internal tools where a 'call the on-duty engineer' button beats a phone tree

Frequently asked questions

How do I integrate WebRTC calling into my website?

With WebCallHub you paste one script tag before </body>. The widget appears on your site, visitors click it, and the call rings your team's browser dashboard at webcallhub.com/app/support. No signaling servers, TURN infrastructure, or WebRTC code required — setup takes about 5 minutes.

Do I need my own TURN/STUN servers?

No. WebCallHub operates the TURN and STUN infrastructure and falls back to relayed media automatically when a visitor is behind a strict NAT or corporate firewall. That is included on every plan, including Free.

How is this different from Twilio or a CPaaS API?

A CPaaS gives you programmable building blocks and bills per minute; you still write and maintain the integration. WebCallHub is the finished product — widget, agent dashboard, routing, recording, transcription — at a flat monthly price. Browser-to-browser calls have no per-minute cost at all.

Is there an API?

Yes. The Business plan ($149/month) includes a REST + WebSocket API and webhooks: create agents, query calls and transcripts, receive call events, and white-label the widget.

Is the audio encrypted?

Yes. All call audio is encrypted in transit with DTLS-SRTP, the WebRTC standard. Optional recordings are encrypted at rest.

Which browsers and devices are supported?

Chrome, Safari, Firefox, and Edge on desktop, Android, and iOS. Visitors need no app, plugin, or account — WebRTC is built into every modern browser.

Ship calling this afternoon, not this quarter

Paste the snippet, open the dashboard, take your first call. Free forever with 200 minutes/month — no card required.