← Back to all projects
📡

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.

10 GiB in 56.8s3 platformsAES-256-GCM90 tests

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

01Send a file from browser to browser using a short pairing code.
02Use the desktop app on Windows, macOS or Linux.
03Script transfers from the command line.
04Resume after a dropped connection — every chunk is verified with SHA-256.
05Move huge files fast: 10 GiB in 56.8 seconds over encrypted TCP.

How it’s built

A simplified view of the architecture — follow the dots as a request moves down the layers.

Devices
Web appReact 19 + Vite
DesktopElectron
CLI
Pairing
Signaling serverNode.js WebSocket · rate-limited
CPace PAKEshort code → strong key
Transport
WebRTC P2Pup to 4 parallel channels
Encrypted TCPAES-256-GCM
TURN relayfallback
Integrity
64 KiB framesflow control
SHA-256 checksresume after disconnect

A request, step by step

  1. Sender and receiver connect to the signaling server and pair with a short code.
  2. They derive a shared key with the CPace PAKE handshake and HKDF.
  3. Data flows directly peer to peer over up to 4 WebRTC channels — or encrypted TCP for the CLI and desktop.
  4. If no direct path exists, traffic relays through TURN — still encrypted end to end.
  5. Every 64 KiB frame is flow-controlled and verified with SHA-256; interrupted transfers resume.

Tech stack

Signaling & transport
Node.js⚡WebSocketsWebRTCTURN relay
Security
CPace PAKEHKDF🔒AES-256SHA-256
Apps
ReactViteElectronCLI
Platform
DockerGitHub Actions

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

❓ Fast without a server in the middle.

✅ Parallel WebRTC channels with flow control, and encrypted TCP for CLI / desktop: 10 GiB in 56.8 seconds.

❓ Pairing securely with a short code.

✅ CPace PAKE turns a short code into a strong shared key, so the code can’t be brute-forced offline.

❓ Abuse of a public signaling server.

✅ Rate limits and brute-force throttling on signaling and TURN; 4 rounds of security testing with every finding fixed.