Peer-to-peer · No cloud · Runs in browser
Make calls
without a cloud middleman.
Create a live audio/video/chat meeting and share an invite link. No install, no account, no app store. The call runs browser‑to‑browser when your networks allow, or through an end‑to‑end encrypted relay when they don't — so the server can't read your data.
Peer
You
muted
for Humans
part of the alt-p2p family
◢ no install · no account · no cloud service can read your call
A call that lives at a URL.
Both people just open a URL. The browser does all the real-time work — the server just introduces you, and can't read the call. Use our hosting service, or run your own server.
Just hit a URL
Runs 100% in the browser — nothing to download, no account, no app store. Send an invite link and the other side's form fills itself; the secret rides the URL fragment, which never reaches a server.
It connects you — and can't read it
This server only introduces you. Calls go peer-to-peer when your networks allow it; if a firewall or router blocks the direct path, they fall back to relay through the server — end-to-end encrypted either way, so the server can't read your traffic.
No WebRTC, except the wire
hivedrop uses a WebRTC DataChannel as the carrier only — nothing else from WebRTC. Its own WebCodecs media pipeline (Opus audio, VP8 video) rides the channel, with camera-less and mic-less peers degrading gracefully instead of failing the call.
End to end — even the fallback
Each peer proves its own certificate fingerprint with the shared key, so a coordination server can't slip in as a man in the middle. When a hostile network blocks the direct link, frames are relayed AES-256-GCM encrypted with forward secrecy — encrypted so the server can't read it.
Drag a file into the call
Drop a file into the chat and it transfers over the same peer-to-peer channel — no files uploaded or stored in anyone's cloud. Every block and the whole file are SHA-256 verified end to end, so what lands is exactly what was sent.
Two browsers. One link. No cloud can read it.
Both browsers punch through their networks and talk directly, peer-to-peer over UDP. When a network is too strict for the direct path, the coordination server relays the traffic over TCP instead — end-to-end encrypted, so the server can't read your call.
- You create a meeting and share the invite link with your peer — the shared secret rides the link, never a server.
- The coordination server introduces the two browsers to each other.
- The two browsers attempt a hole punch through their networks and connect directly.
- The browsers set up an encrypted channel — a fresh per-call key (forward secrecy), each side verified against the shared secret, so no one can eavesdrop or impersonate.
- Audio, video, chat and files flow straight between the two browsers, end-to-end encrypted.
- You create a meeting and share the invite link with your peer — the shared secret rides the link, never a server.
- The coordination server introduces the two browsers to each other.
- The two browsers attempt a hole punch, but a firewall blocks the direct path — so they connect through the server.
- The browsers set up an encrypted channel end-to-end — a fresh per-call key (forward secrecy) negotiated through the coordination server, which passes the handshake along but can't derive the key.
- Audio, video, chat and files pass through the server, but only as encrypted data the server can't read.
The coordination server is required, but tiny — one lightweight server process. License it to run on your own box, or let us host it for you. Start with a free trial.
The server can't be in your call.
hivedrop is the in-browser member of the alt-p2p family — the same shared-session and pre-shared-key trust model as its siblings, reborn for the browser. You share a meeting id and a key out of band; everything else is derived from them, and nothing of your call is ever exposed to a service you don't control.
A calling app with no cloud middleman.
hivedrop is in active development. It runs today on Chrome, Edge, Brave and Safari 18+ — validated live on LAN, forced-relay, invite links, mid-call device switching, and camera-less peers.
To self-host: one small server process on a machine you run. To call: a modern browser (Chrome, Edge, Brave, or Safari 18+) — nothing else. Camera and mic are used only in your browser, over a secure (HTTPS) page.