Skip to content
Open Source

Build peer-to-peer apps 
without headaches

Simple and extensible API, 
optimized for performance, 
for creating WebRTC applications

Peerix

Why Peerix?

Peerix in 1 minute

Frequently Asked Questions

What is Peerix?
A lightweight JavaScript/TypeScript library that simplifies WebRTC by handling signaling, NAT traversal, and connection state so you can build peer‑to‑peer apps faster.
Do I need a signaling server?
Yes — peers need signaling to discover each other; Peerix is transport‑agnostic and supports drivers for different signaling backends. You can use built‑in drivers or implement your own custom driver.
Is Peerix an SFU or MCU?
No — Peerix is not an SFU (Selective Forwarding Unit) or MCU (Multipoint Control Unit). It focuses on enabling direct peer-to-peer communication between clients, without server-side media processing or routing.
How does Peerix handle NAT and firewalls?
Peerix uses standard WebRTC techniques, such as ICE (Interactive Connectivity Establishment), STUN (Session Traversal Utilities for NAT), and TURN (Traversal Using Relays around NAT) servers, to handle NAT traversal and firewall restrictions, ensuring reliable peer-to-peer connections. You can specify public STUN servers or set up your own TURN server for better connectivity in restrictive network environments.
Can I self‑host or use a cloud offering?
Both — documentation covers self‑hosting your signaling/TURN infrastructure or using cloud hosting options.
Which browsers are supported?
Peerix targets all major browsers; the library and tests aim to ensure broad browser compatibility.
Is Peerix open source?
Peerix is an open‑source project with dual GPLv3 and commercial licenses, allowing you to choose the license that best fits your project’s needs.