P2P WebRTC and Own Server Options
Last updated: 11 November 2026. Source for accurate/current info: webrtchost.com/hosting-plans/, videowhisper-webrtc on GitHub.
Source page: https://webrtchost.com/hosting-plans/
P2P WebRTC services focus on low-latency peer connections using the VideoWhisper WebRTC signaling server plus STUN/TURN. This path is useful for private calls, high-interactivity sessions, developer tests, and custom deployments.
Free Developer Account Context
The free developer account is designed for limited testing by 1-3 developers with constrained quality settings. The public plan page lists:
| Feature | Free Developers Account |
|---|---|
| Streams around 532kbps | 5 |
| 1-way viewers | 3 |
| 2-way private calls | 1 |
| Max resolution | 640x360p |
| Max framerate | 15 fps |
| Max video bitrate | 750 kbps |
| Max audio bitrate | 32 kbps |
| Total account bitrate | 2.7 Mbps |
| Max connections | 10 |
Own Server Deployment
The Free VideoWhisper WebRTC core is GPL-2.0-or-later and supports browser broadcasting, private calls, RandomChat and opt-in small-room conferencing. Source version 2026.11.11 includes authentication, server-enforced room roles/limits, usage statistics, tests and example-only configuration. It does not include nginx, restream or schedule implementations.
Use a maintained Linux environment with Node 22+, an HTTPS/WSS hostname and valid TLS files. Configure coturn separately when relay is required, along with firewall and media ports. Private website callbacks should verify per-user/PIN access; keep account and API secrets server-side. Native ICE diagnostics are optional and do not replace real-browser TURN testing. Size CPU, network and relay capacity from the intended workload and measurements, not a universal participant count.
The Video Conference demo provides up to four mesh participants, camera/microphone, screen sharing, chat, host controls and shared invitation links. Actual quality/capacity also depends on account/callback limits and bandwidth; the Developers table is not an unconditional conference-capacity promise. Conference source · Broadcast/call/RandomChat app.
Self-hosting does not require purchasing a VideoWhisper account. Managed installation, streaming/TURN and turnkey options are available through WebRTCHost and Site2Stream. Check current plan terms and request setup guidance for your network/access model.
Read the server publishing and rollback checklist. Preserve configuration, database history and installed private modules; source publication alone does not authorize or perform a production update.
Limitations
P2P WebRTC is excellent for private calls and low-latency interactivity, but it is not optimized for 1-to-many scaling. For large broadcast audiences, a relay streaming server is usually recommended so the broadcaster sends one stream to the server and the server distributes it to viewers.
Separate Managed Media Services
RTMP/HLS/DASH management, IP-camera restreaming and scheduled playout may be supplied by separate managed services or installed optional modules. They are not included in the Free WebRTC source. Confirm the selected service/plan, codecs, storage and deployment requirements before promising those workflows. Larger meetings need a separately evaluated SFU/media architecture; the Free signaling core is not an SFU.
Excerpt
Self-host the GPL Free VideoWhisper WebRTC core for broadcasting, calls, RandomChat and small conferences, or choose optional managed WebRTC/TURN hosting.
