peeza — move big files device-to-device

How it works

Three steps, no upload.

A file never lands on a server waiting to be fetched. It streams the moment the other side connects.

Any size. It's read straight off disk in small chunks, so memory stays flat whether it's 4 MB or 400 GB.

Send a one-time link, or fire it straight to one of your own machines — or a Peeza on the same network.

A direct connection when the network allows one; a blind relay when it doesn't. Either way, encrypted the whole path.

Why peeza

No cloud storageFiles stream machine-to-machine, never parked on a server.

Always end-to-end encryptedAES-256-GCM per share. The relay forwards bytes it can't read.

One-time linksThe decryption key rides in the link, not in our database.

Direct peer-to-peerStraight across when the network allows a path.

Any size, constant memoryStreamed in small encrypted chunks — no staging, no ceiling.

ResumableSurvives closed windows, restarts, reboots. Resumes from the last byte.

Send to your own devicesSigned in on two machines? Send from one to the other.

AirDrop-style transfersFinds Peezas on your local network — no relay, no internet, no login.

Web remote controlWatch and manage machines and transfers from the browser.

Security

Even when a transfer can't go direct and falls back through our server, it forwards ciphertext it has no key for.

A per-share AES-256-GCM key is generated on your machine and rides in the link fragment — #k=… — which browsers never send to a server.
The relay only ever sees encrypted chunks. It does signaling and blind byte-forwarding — never decryption.
Device-to-device sends use per-machine keypairs and sealed-key envelopes, so the relay stays blind even for directed transfers.
AirDrop-style transfers confirm a first connection with a matching 6-digit code, then pin the peer.

Want the full picture? Read how it works →