Does REAP work on Windows or Linux?

macOS and iOS at launch. Windows is on the Q1 2027 roadmap. Linux follows based on demand.

REAP — Peer-to-peer file transfer with cryptographic proof-of-delivery

01 · The problem

Everything you use today was built for everyone else.

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.

WeTransfer7-day links

File expires in a week. Recipient must download in time. No receipt. No proof it arrived whole.

Dropboxcloud storage

Your 60TB shoot lives on someone else's server. Paying rent, forever. Cloud dependency isn't delivery.

Email25 MB limit

Attachment silently stripped. Clients "didn't get it." No confirmation. No hash. No trail.

FTP1985-era

Requires a server. Credentials leak. No verification. Your IT department's nightmare.

02 · How it works

Three steps. No server in the middle.

— Step 01

Latch your files.

Drop files into REAP. We compute a BLAKE3 hash for every byte before anything leaves your machine. That hash is your fingerprint.

→

— Step 02

Direct peer connection.

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.

→

— Step 03

Receipt issued.

Recipient re-hashes every byte. If it matches, both peers countersign with Ed25519. You now have cryptographic proof, signed by both parties.

03 · The proof

The artifact no one else gives you.

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.

REAP — proof-of-delivery.

— Receipt ID

RCPT-bf3a7d2e9c81f4a3b8e2

— Delivered

2026-04-15 · 14:32:07 UTC · 0.241s after upload

— File

wedding_ceremony.mov · 8,103,242,141 bytes · ProRes 4K

— Content hash

BLAKE3: 9f2a1b8c4e7d3f5a6b9c2d1e8f4a7b3c5d6e9f1a2b3c4d5e6f7a8b9c0d1e2f3a

— Sender signed

✓ REAP-P9xK2mN Kenji Tanaka · Ed25519: d4f8a2b1...c9e3f7d2

— Receiver signed

✓ REAP-P3vL8Zq Anya Vasquez · Ed25519: a1b2c3d4...e5f6a7b8

— Route

Direct peer · QUIC/WebRTC · no relay · no cloud copy

— Integrity

VERIFIED · all bytes matched · signatures valid

// RCPT-bf3a7d2e9c81f4a3b8e2 · verifiable forever
{
  "version": "1.0",
  "receipt_id": "RCPT-bf3a7d2e9c81f4a3b8e2",
  "delivered_at": "2026-04-15T14:32:07Z",
  "transfer_duration_ms": 241,
  "file": {
    "name": "wedding_ceremony.mov",
    "bytes": 8103242141,
    "media_type": "video/quicktime",
    "content_hash": {
      "algo": "BLAKE3",
      "value": "9f2a1b8c4e7d3f5a..."
    }
  },
  "sender": {
    "peer_id": "REAP-P9xK2mN",
    "display_name": "Kenji Tanaka",
    "signature": "d4f8a2b1...c9e3f7d2"
  },
  "receiver": {
    "peer_id": "REAP-P3vL8Zq",
    "display_name": "Anya Vasquez",
    "signature": "a1b2c3d4...e5f6a7b8"
  },
  "route": {
    "protocol": "QUIC+WebRTC",
    "direct": true,
    "relay_used": false,
    "cloud_copy": false
  },
  "integrity": {
    "bytes_matched": true,
    "sender_sig_valid": true,
    "receiver_sig_valid": true,
    "status": "VERIFIED"
  }
}

$ reap verify RCPT-bf3a7d2e9c81f4a3b8e2

— step 01 · parsed

Receipt structure valid

v1.0 · signed JSON · 2.4 KB

✓ ok

— step 02 · hash

BLAKE3 hash recomputed on file

matches manifest · 8.1 GB scanned · 142ms

✓ match

— step 03 · signature

Sender Ed25519 signature valid

REAP-P9xK2mN · Kenji Tanaka

✓ valid

— step 04 · countersign

Receiver Ed25519 signature valid

REAP-P3vL8Zq · Anya Vasquez

✓ valid

— step 05 · chain

No tampering detected in transfer log

route confirmed direct · no relay

✓ clean

— RESULT · VERIFIED · holds in court.

04 · Security

What we don't store is the point.

What REAP does.

End-to-end encrypted transport

Every byte is encrypted at source, decrypted only at destination. No middle box can read it.

Deterministic hashing

BLAKE3 fingerprints every file before send and after receive. Hashes must match or the transfer is rejected.

Countersigned receipts

Ed25519 signatures from both peers embedded in every Proof-of-Delivery Receipt.

Local-first storage

Files live on your drives. REAP indexes them. You own the bytes and the catalog.

What REAP doesn't.

No cloud copy, ever

Your files don't pass through our servers. We can't read them. Can't decrypt them. Can't subpoena them.

No tracking pixels or analytics on content

We measure uptime and protocol metrics. We don't know what you transfer.

No forever-contracts or lock-in

Cancel any time. Export your catalog. Your files stay exactly where they are.

No "share link" that bypasses peers

Every transfer is a negotiated, signed session. Not a public URL.

HIPAA by construction

SOC 2 in progress

GDPR aligned

Zero-trust architecture

05 · Who it's for

Three professions. One promise.

— The videographer

She shot your wedding. Her business is the 60TB that lives on one Thunderbolt drive.

When the clients say "we never got the files," she has a receipt. When the drive fails, the integrity hashes prove the copy is the original. When she's audited, she shows a chain.

— The litigator

Chain of custody for evidence files isn't a nice-to-have. It's the whole case.

Opposing counsel challenges the authenticity of the discovery video. He produces the REAP receipt — signed, hashed, timestamped. The challenge dies.

— The surgeon

A DICOM scan crossing hospital networks before a four-hour resection. Margin for corruption: zero.

REAP verifies every byte, peer-to-peer, end-to-end. HIPAA-compliant by construction. No third-party server touches the data. Ever.

06 · Features

What's inside.

Zero-knowledge transport

Peer-to-peer means peer-to-peer. No cloud copy. We can't read your files.

— E2E encrypted

Court-ready receipts

Every transfer ends with a signed, hashed, timestamped artifact. Verifiable forever.

— Ed25519 · BLAKE3

Built for 60TB, not 60MB

Thunderbolt-native ingest. Resumes across network drops. Professional scale.

— Made for pros

Ghost mode for offline files

Your entire archive stays searchable — even when the drive is unplugged. Reconnect and restore.

— Always indexed

QR-pair any device

No account creation. Scan a code, you're connected. Seconds, not signups.

— Passwordless

Matrix command palette

Search any file across any session, any drive, any peer. ⌘K and go.

— Keyboard-first

07 · Pricing

One fair price. No rent on your files.

— Individual

$12/mo · billed annually

For the working pro who bills clients by the delivery.

✓Unlimited peer-to-peer transfers

✓Court-ready receipts · JSON + PDF

✓Up to 10 active peers

✓Single device · macOS + iOS

Join waitlist

— Studio

$29/mo · per seat

For small teams with shared archives and compliance needs.

✓Everything in Individual

✓Shared sessions · team rooms

✓Unlimited peers and devices

✓Multi-device sync · Thunderbolt-aware

✓Audit log export · CSV, JSON

✓Priority support

Join waitlist

— Enterprise

Custom

For hospitals, firms, and studios with institutional compliance needs.

✓Everything in Studio

✓SSO · SCIM · domain controls

✓On-prem relay · air-gap option

✓Custom retention policies

✓BAA for HIPAA workflows

✓Dedicated success engineer

Contact sales

— First 1,000 waitlist seats: 50% off for the first year. Lock it in by joining.

08 · Questions

Answered plainly.

Why not just use WeTransfer or Dropbox? +

They're built for everyone. REAP is built for people whose livelihoods depend on cryptographic proof. If you've never needed a receipt signed by both parties after a file transfer, you probably don't need REAP yet. If you have — or your profession requires one — you already know.

Is the peer-to-peer connection really direct? +

Yes. REAP uses QUIC over WebRTC to negotiate a direct tunnel between your machine and the recipient's. In rare cases where NAT traversal fails, we fall back to a TURN relay — but the files are still end-to-end encrypted, we still can't read them, and the relay is logged transparently in the receipt so you always know the exact route.

Can the receipt be forged? +

No. Every receipt is signed with Ed25519 keys held on the sender and receiver devices — we never see the private keys. The content hash is BLAKE3, a modern cryptographic hash that's effectively impossible to collide. If a single byte of the file is altered, the hash changes and the signature fails verification. Forgery would require breaking Ed25519 and BLAKE3 simultaneously.

What happens to my files if REAP shuts down? +

Nothing. Your files live on your drives — we never touched them. Receipts are plain signed JSON, verifiable forever by any tool that implements the standard. We'll open-source the receipt format and verification logic so the proofs outlast the company.

Does REAP work on Windows / Linux? +

macOS and iOS at launch. Windows is on the Q1 2027 roadmap. Linux after that, driven by demand. If you're an enterprise customer and Linux is a blocker, let us know — we prioritize based on real need.

Can I self-host REAP? +

The Enterprise tier includes an on-prem relay option for air-gapped environments. The core peer-to-peer protocol is already local-first — you don't need any of our infrastructure to transfer files between two of your own devices. We are genuinely not in the middle.

Is this HIPAA-compliant? +

The architecture is HIPAA-aligned by construction — no cloud copy, no third-party access, end-to-end encrypted, auditable receipts. We sign Business Associate Agreements for Enterprise customers and provide the controls most institutions require. Talk to us before deploying in a regulated environment so we can confirm your specific workflow.

Know it arrived.
Don't hope it did.

Everything you use today was built for everyone else.

Three steps. No server in the middle.

Latch your files.

Direct peer connection.

Receipt issued.

The artifact no one else gives you.

What we don't store is the point.

What REAP does.

What REAP doesn't.

Three professions. One promise.

What's inside.

One fair price. No rent on your files.

Answered plainly.

Get in early.

Know it arrived. Don't hope it did.

Everything you use today was built for everyone else.

Three steps. No server in the middle.

Latch your files.

Direct peer connection.

Receipt issued.

The artifact no one else gives you.

What we don't store is the point.

What REAP does.

What REAP doesn't.

Three professions. One promise.

What's inside.

One fair price. No rent on your files.

Answered plainly.

Get in early.

Know it arrived.
Don't hope it did.