Peer-to-peer file transfer with cryptographic proof-of-delivery. Built for the media pros, lawyers, and surgeons whose livelihoods depend on knowing — not hoping — the file arrived intact.
A wedding videographer. A defense attorney. A neuro-oncologist. Three livelihoods. One shared problem: no way to prove the file they sent arrived exactly as sent.
Drop files into REAP. We compute a BLAKE3 hash for every byte before anything leaves your machine. That hash is your fingerprint.
We negotiate a QUIC + WebRTC tunnel direct to your recipient. No cloud copy. No third-party server. A to B — and only A to B.
Recipient re-hashes every byte. If it matches, both peers countersign with Ed25519. You now have cryptographic proof, signed by both parties.
Every transfer ends with a Proof-of-Delivery Receipt — a signed, hashed, timestamped artifact you can hold up in court, an audit, or in any disagreement with a client.
A single JSON file plus a human-readable rendering. Portable. Tamper-evident. Verifiable by anyone with REAP or a simple command-line tool. Three views of the same proof.
Across the internet the two machines speak QUIC to each other directly — TLS 1.3 from one device to the other. Our server is a phone book, never a post office: it learns two addresses, says go, and carries nothing. There is no relay path in the code.
Who you are talking to is your device's Ed25519 key, bound to the connection itself, so nothing can stand in the middle and pretend. On your own network, bytes never leave your network.
quinn · rustls · Ed25519 channel binding · no relayEvery transfer ends with a receipt: the file's BLAKE3 hash, its size and name, the moment it landed, and the sending device's public key — signed with that device's Ed25519 identity.
Anyone can check it, forever, with nothing but the receipt and the file. The verifier runs in your browser — the file never uploads.
Files are hashed as they stream, not after — a 4 GB video starts moving without being read twice. The queue keeps its own ledger, so a drive unplugged mid-copy resumes the moment it is back.
Over the network a dropped connection resumes at the byte it stopped, and the receiver proves the bytes it already holds with a hash of exactly those bytes before a single new one is sent.
streaming BLAKE3 · byte-offset resume · prefix hash · mount auto-resumeEach drive gets its own search index the first time REAP meets it. Unplug the drive and the index stays: you can still find the file, see when it was last there, and see its thumbnail — thumbnails are keyed by the file's own hash, not by the path.
Plug it back in and REAP notices the mount, picks up anything that was waiting, and carries on.
Tantivy per drive · content-keyed thumbnails · /Volumes watcherDevices on the same network find each other on their own. Tap Pair and each side keeps the other's key — that is the whole ceremony. No account, no password, nothing to reset.
For devices that cannot see each other yet, a one-time invite code does the same job; the QR form of that code is landing in 0.25.
Bonjour + peer-to-peer Wi-Fi discovery · mutual trust · Ed25519 identity⌘K from anywhere. Type a filename, part of one, or a plain sentence — pngs on this drive, my last three transfers — and the Matrix answers from every drive it has met, every session it has kept, every peer it knows.
Enter opens the folder. ⌘L reveals in Finder. ⌘O opens the file. A word buried inside a name is found in about a millisecond.
Tantivy 0.24 · reap_name tokenizer · natural-language asksWe're rolling out slowly. First 1,000 seats go to professionals who need this most — and earn a 50% discount on the first year. Leave your email. We'll send a personal invite when it's your turn.