# ReMOAT: A WebRTC Team Embeds a WebRTC Call Button | CallCeptor > ReMOAT streams browser DevTools peer to peer over WebRTC. Six questions a WebRTC team should ask before embedding someone else's call widget, answered for CallCeptor. Source: https://callceptor.com/customers/remoat/ customer-story / remoat.dev ## A WebRTC company put someone else's WebRTC on its website ReMOAT lets a developer open a live, peer-to-peer DevTools session into a user's browser over WebRTC. A team that builds on the same stack knows which questions to ask before putting a third-party call widget on its own site. Here they are, with CallCeptor's answers. Published 2 October 2026 · Written by the CallCeptor team “We wanted a call button that worked in the browser, sounded clear and didn’t need a phone line behind it. CallCeptor did that from day one. Our visitors can reach us in one click, and we get the context of the page they called from.”Team ReMOAT ### Two different calls ReMOAT's paid plans already include voice calling between a developer and a user, inside a debugging session. That is a call during support, between people who already know each other. The Call button on remoat.dev does a different job: a visitor who hasn't signed up yet, talking to the team before they do. That needs routing, business hours and a callback when nobody is free, which is the part CallCeptor does. ### Six questions a WebRTC team should ask - Q1 #### What does it add to page load? One script of about 7 KB, roughly 3 KB gzipped, loaded with async. It draws the button and nothing else. The calling code, PeerJS included, lives in an iframe that loads only when a visitor clicks Call. A visitor who never clicks never downloads it. - Q2 #### Can our CSS break it, or can it break ours? The button is drawn inside a shadow root, so the host page's styles don't reach it and its styles don't leak out. The call itself runs in an iframe on CallCeptor's origin. Microphone permission is asked for by that frame, not by your page. - Q3 #### What's the media path? Browser to browser over WebRTC, using PeerJS for signalling. Audio is encrypted with DTLS-SRTP, as WebRTC requires. STUN finds a direct route between the visitor and the agent. For networks that block that, a TURN relay can be configured on the server. - Q4 #### How is the audio tuned? Opus is moved to the top of the SDP with in-band forward error correction, so short packet loss is concealed rather than heard. The microphone is opened with echo cancellation, noise suppression and automatic gain control switched on. - Q5 #### What's stored, and what isn't? Per call: the visitor's name and number if they gave them, an anonymous browser id, the page and user agent, ring and talk time, the agent's notes and the visitor's rating. For diagnosing bad calls: a capped event log and the WebRTC stats each side reports (round trip, jitter, packet loss, codec, ICE route). Customers' own dashboards don't show these; CallCeptor staff use them to debug. Audio is not recorded. There is no recording feature today. - Q6 #### Can someone copy our embed onto their site? The button only appears on origins accepted for the site key. Pasting the snippet onto another domain draws nothing. ### The contact page, as desks remoat.dev/contact promises a reply in two to four business hours and sorts enquiries into five topics. In the call panel the same topics become desks the visitor picks before calling, so a question about TURN relays reaches the person who can answer it. - Enterprise on-prem signalling and TURN - SDK integration (React, Next.js, Vue, Safari) - Security and compliance questionnaire - Billing and subscription - General technical question How desks and routing work: [routing website calls by page](https://callceptor.com/guides/route-website-calls-by-page/). ReMOAT productLive remote browser debugging transportWebRTC data channels, peer to peer installnpm SDK or Chrome extension companyReMOAT Technologies Pvt Ltd, India site[remoat.dev](https://remoat.dev/) ### About this story Facts about ReMOAT come from its public site, linked below. The six answers describe CallCeptor's code as of this page's date; when the code changes, this page changes with it. No usage numbers yet. They'll be added with ReMOAT's agreement once there are enough calls. Sources - [remoat.dev: product and plans](https://remoat.dev/) - [remoat.dev/about: company](https://remoat.dev/about) - [remoat.dev/contact: enquiry topics and response times](https://remoat.dev/contact) Something here wrong or out of date? [Tell us](mailto:support@callceptor.com?subject=Correction%3A%20ReMOAT%20story).