Direct File Transfer — No Server, No Middleman
Device A to Device B. That's the whole product. No intermediary server storing a copy, no upload step, no download step. One connection, one transfer. If your files go through a server, that server can read them, lose them, or get subpoenaed for them.
By starting, you agree to our Terms
How It Works
Your Device
Sender
Their Device
Recipient
No server in the middle. Files stream directly between browsers using WebRTC.
Connect
WebRTC establishes a direct encrypted link between browsers.
Stream
Files travel straight from sender to receiver — no detour through servers.
Done
Transfer completes. Nothing stored anywhere except the original devices.
Why Direct Transfer Wins
One Hop
Cloud services: your device → their server → recipient's device. Two hops, two points of failure, two opportunities for someone to look at your stuff. P2P: your device → recipient's device. One hop. Done.
No Copy on Any Server
Direct transfer means exactly that. The file exists on your device and the recipient's device. Nowhere else. Not temporarily, not in a cache, not in a 'processing queue.'
DTLS Encrypted
Every byte encrypted in transit using DTLS — the encryption layer built into WebRTC. The connection is authenticated and encrypted before any file data flows.
Relay When Needed
Some networks block direct P2P (corporate firewalls, symmetric NAT). When that happens, an encrypted TURN relay bridges the connection. Still encrypted, still private — just with an extra hop.
Direct vs Indirect File Transfer
| Aspect | Direct (Perkoon) | Indirect (Cloud) |
|---|---|---|
| File path | Device → Device | Device → Server → Device |
| Privacy | No third party sees files | Provider stores and can access files |
| Speed | Single hop | Two hops (upload + download) |
| Size limit | None | Service-dependent |
Frequently Asked Questions
How direct is 'direct'?
In the best case, a literal point-to-point connection between your browser and the recipient's browser. No server touches the file data. In the fallback case (strict firewall), the data routes through an encrypted relay — still private, slightly slower.
What's the speed difference vs cloud transfer?
Cloud transfer: upload time + download time. Direct P2P: one transfer. For a 10GB file on 50 Mbps, that's ~27 minutes instead of ~54 minutes. Same internet speed, half the wait.
Do I need to install software?
No. Runs in your browser using WebRTC. Chrome, Edge, Brave, Firefox, Safari all supported. No extensions, no plugins, no desktop app.
Can someone intercept the transfer?
WebRTC connections use DTLS encryption with certificate fingerprint verification during the signaling phase. A man-in-the-middle attack would require compromising the signaling server — which only exchanges connection metadata, never file contents.
Device to Device. No Middleman.
One connection. One transfer. Zero copies on any server.
By starting, you agree to our Terms