Technical Overview
How PeerBox Works
Direct browser-to-browser encrypted communication with zero servers, zero intermediate
relays, and zero tracking.
Engineered for Privacy & High-Throughput Streaming
Direct browser data channels bypass cloud servers for maximum speed and privacy.
🚀
Multi-Gigabyte OPFS Streaming
Large transfers stream directly into your browser's Origin Private File System
(navigator.storage.getDirectory()), bypassing JavaScript heap memory
limits to support 10GB+ file exchanges without crashing.
🎙️
Ephemeral Voice Notes
Record high-fidelity audio notes with dynamic RMS volume waveforms. Audio codecs
(Opus/WebM or AAC/MP4) are dynamically negotiated cross-browser for instant playback.
📸
Instant Screen Grabs
Capture a crisp single frame from any display or window with offscreen canvas
rendering. Media tracks immediately stop upon capture to guarantee zero ongoing
streaming overhead.
⚡
Zero-TURN Direct P2P
Direct WebRTC connections across Local LAN and public STUN NAT hole-punching. Zero
relay servers means zero third-party latency and zero recurring hosting costs.
Under the Hood Architecture
A decentralized signaling mesh orchestrates direct peer connections in three transparent
steps.
1
Decentralized Nostr Signaling
Browsers discover each other over public Nostr relays (or BitTorrent tracker
fallbacks). Signaling payloads are encrypted; relays only see opaque ciphertext.
2
URL Hash Key Isolation
Room Keys live exclusively in the URL hash fragment (#key=...). Per RFC
3986, hash fragments are strictly client-side and are mathematically never sent to web
servers.
3
Direct WebRTC DataChannels
Once NAT hole-punching succeeds via STUN, direct UDP sockets form between browsers.
All chat messages, audio payloads, and binary file chunks stream directly between
peers.
Direct P2P vs Centralized Cloud Relays
Why serverless browser streaming is inherently more private and sustainable.
| Dimension |
Traditional Cloud Relays |
PeerBox (Serverless P2P) |
| Server File Storage |
Stored on remote cloud disks |
0 Bytes (Pure memory / OPFS) |
| Account / Sign-up |
Requires email, phone, or OAuth |
None (Ephemeral Persona) |
| Transfer Speed |
Throttled cloud bandwidth tiers |
Full LAN / Direct Internet speed |
| Encryption Visibility |
Server operator holds keys / logs |
Client-side Web Crypto AES-GCM |
| Hosting Costs |
High recurring server & relay bills |
$0 (Static GitHub Pages) |