Perkoon vs RocketShare

File transfer was a solved problem. Then everyone decided to make it worse — size caps, forced signups, expiring links, surprise paywalls. The usual.
Perkoon unsolved it.
Free P2P transfers beam files directly between browsers. No server in the middle. No size limit. No account. Both parties online, files move. Simple physics.
Cloud storage exists for when the other human is offline, encrypted and waiting for them whenever they show up. This one costs money. Servers aren't powered by good vibes.
Here's where it gets interesting: Perkoon is the first file transfer service built with native agent accessibility. Machine-readable state, stable DOM selectors, automation API. Your AI workflows can send and receive files without pretending to be a human clicking buttons. The future showed up early.
CLI included: npx perkoon send/receive. Works browser-to-CLI, CLI-to-CLI. Because terminals deserve nice things too.

RocketShare is built on a zero-knowledge model: files are encrypted client-side, and encryption keys never reach our servers. Share links keep the key in the URL fragment, so the backend only stores encrypted blobs + metadata + expiry. This gives users enterprise-grade privacy with a simple, self-serve sharing experience.