No server in the middle when Drop can manage it, and nothing readable in the
middle even when there is one. drop send and drop recv connect two
computers directly over QUIC by default, falling back to a small encrypted
relay for browsers and uncooperative NATs.
Important
Drop is pre-release software. The protocol and deployment defaults may change, and the public instance should not be treated as a durable storage or high-assurance secure-transfer service.
curl -fsSL https://github.com/op-q/drop/releases/latest/download/install.sh | sh$ drop send ./project
Sending ./project (128 files, archived as project.tar)
Looking for a peer-to-peer path...
Run this on the other computer:
drop recv 7F2A91-crossover-clockwork-ridge
Path peer-to-peer (no Drop server)
Waiting for the receiver to connect...$ drop recv 7F2A91-crossover-clockwork-ridge
Path peer-to-peer (no Drop server)
Receiving 100.0% 412.7 MiB / 412.7 MiB 86.4 MiB/s ETA --
Extracted 128 files into .That's the default, auto — direct when the two computers can reach each
other, the relay when they can't. Every transfer is encrypted end to end
either way. Run drop --help for the full flag list, including
--transport, --compress, and --force.
- Security model — encryption, trust boundaries, hostile input
- Architecture — crates, transport, transfer flow
- Protocol — the wire format
- Deployment — requirements, configuration, Docker, Kubernetes/GKE
- Commands — running from source, local dev workflows
- Contributing
- Full documentation index
Drop is available under the MIT License.