You send.
Run pike send file. Get three words.
Open source · direct connection
Send files.
Skip the cloud.
Private, post-quantum file transfer directly between your devices. No account. No size limit. Not one byte through Pike.
✓ No signup✓ Any file size✓ Browser to browser
…Direct connection · no server
We couldn't read or carry your file even if we wanted to.
HOW IT WORKSIntroduced by Pike.
Introduced by Pike.
Carried by nobody.
The directory behaves like a disposable phone book, never a courier. It forgets the introduction as soon as your devices meet.
They receive.
They type the three words. That's it.
Direct.
The file goes straight through. No server. No cloud. No middleman.
SERVER×
The file path never includes us.
If a direct connection cannot be made, Pike stops. It never silently falls back to a server that carries your file.
SECURITY / PERFORMANCEHard to intercept.
Hard to intercept.
Easy to verify.
Multiple layers work together so privacy is an architectural property, not a promise.
01POST-QUANTUM
PQ
Future-safe key exchange
Hybrid X25519 + ML-KEM-768 protects connections today and against future quantum computers.
02HUMAN VERIFIED
SAS8 HEX
See who's connected
A short safety code lets both people rule out an active person-in-the-middle.
03RATELESS CODING
Built for bad Wi-Fi
Recover the file from whichever coded pieces arrive, without waiting on missing packets.
04ZERO-CODE
LAN
No code typed on LAN
mDNS discovery + SAS confirmation. On LAN, just run pike send. Done.
The old way
Your file uploaded to a server.The server reads it. Stores it. Serves it.Pre-quantum encryption. Server holds the keys.croc relays your file through its server. Pike never does.You pay for bandwidth. They pay for servers.
The Pike way
- Your file goes straight to theirs.
- No server sees it. No server holds it.
- Post-quantum. Keys exist only on your devices.
- Direct connection only. No middleman.
- We pay $0. You pay $0. Forever.
PIKE FOR WEBThe product is
The product is
the homepage.
Drop a file and create a direct, encrypted link between two browsers. The post-quantum handshake, AEAD streaming, SAS confirmation, and hash verification all run in the open — from the same Rust code as the CLI, compiled to WASM.
Send
Drop a file here, or click to choose
Receive
stateidle
sas
—progress0%
result—
We couldn't read or carry your file even if we wanted to.
0 bytes through a server
957 MB/s encode
∞ file size
PIKE CLITwo commands.
Two commands.
One direct path.
Use Pike from macOS, Linux, or Windows. Local devices discover each other automatically; internet transfers use a disposable tap code.
cargo install pike-transfer$ pike send movie.mkv Tap code: tunnel-gem-spark Waiting for receiver… $ pike tunnel-gem-spark SAS 6eed027b — same on your screen? [y/N] y ████████████████████████████████ 100% Done. Direct connection. No server touched it.
FAQ
Asked often.
Is my file encrypted?
Yes — X25519 + ML-KEM-768 hybrid key exchange, then every chunk is encrypted with XChaCha20-Poly1305. Keys exist only on your devices.
Do you store my file?
No. The exchange is a phone book: code → address, with a 5-minute TTL. It never sees your file, your keys, or your plaintext.
What if the direct connection can't be made?
Pike stops and tells you honestly. It never silently falls back to a server that carries your file.
Is there a size limit?
No. Files stream chunk by chunk from device to device.