My product Live
Hopline
Encrypted peer-to-peer file transfer
Hopline sends files directly between devices — browser, desktop and command line — encrypted end to end, with no upload server holding your data.
Built for: Anyone moving big or private files — and developers who want to script transfers from the terminal.
↓ Scroll to explore the problem, architecture and stack
The problem
Most file-sharing tools upload your file to someone’s cloud first. That is slower, size-limited, and someone else keeps a copy.
Why it matters
Direct peer-to-peer transfer is faster, has no storage limit and keeps files private. Hopline makes it work across browsers, desktops and terminals, with resume and integrity checks built in.
What you can do with it
How it’s built
A simplified view of the architecture — follow the dots as a request moves down the layers.
A request, step by step
- Sender and receiver connect to the signaling server and pair with a short code.
- They derive a shared key with the CPace PAKE handshake and HKDF.
- Data flows directly peer to peer over up to 4 WebRTC channels — or encrypted TCP for the CLI and desktop.
- If no direct path exists, traffic relays through TURN — still encrypted end to end.
- Every 64 KiB frame is flow-controlled and verified with SHA-256; interrupted transfers resume.
Tech stack
What I built
- A Node.js WebSocket signaling server and a WebRTC protocol sending 64 KiB frames over up to 4 parallel connections, with flow control, SHA-256 verification and resume after a disconnect.
- Encrypted TCP transfer for the CLI and desktop app (CPace PAKE key exchange, HKDF, AES-256-GCM): 10 GiB sent in 56.8 seconds with SHA-256 verification.
- An Electron desktop app and a React 19 + Vite web app.
- A hardened signaling server and TURN relay with rate limits and brute-force throttling.
- 90 automated tests, 4 rounds of security testing with every finding fixed, and a release pipeline that builds installers for 3 operating systems.
Hard problems & how I solved them
✅ Parallel WebRTC channels with flow control, and encrypted TCP for CLI / desktop: 10 GiB in 56.8 seconds.
✅ CPace PAKE turns a short code into a strong shared key, so the code can’t be brute-forced offline.
✅ Rate limits and brute-force throttling on signaling and TURN; 4 rounds of security testing with every finding fixed.