No accounts
Discover and pair immediately. No email collection, no forced login.
Local-first · app-layer E2EE
Near-field transfer trust you can see
Move files between nearby or same-LAN devices — no account, no server by default, end-to-end encrypted.
Untrusted peers cannot send files. Pairing requires mutual SAS confirmation. No relay by default.
- Default mode
- Local
- Default port
- 39551
- Pairing TTL
- 120s
Trusted transfer in three steps
No accounts, no cloud contact list. Trust lives between two devices and is created by mutual confirmation.
- 01
Discover
Auto-discover candidates on the same LAN, or connect manually by scanning a code.
- 02
Pair
Scan a signed pairing payload, then both sides confirm the same short SAS digits.
- 03
Transfer
Untrusted peers cannot send files. Every byte stays app-layer end-to-end encrypted.
Three hard constraints, not marketing words
Local by default, pairing must be visible, crypto must be verifiable — written into architecture decisions, not a landing page.
Visible pairing
Signed QR payloads plus short SAS digits. Trust only after both sides confirm.
Verifiable crypto
AES-GCM on TCP; TLS cannot replace SAS. Engine and protocol are open for review.
Crypto you can verify, not slogans
The engine and protocol are open for review. Every claim below maps to code.
AES-256-GCM
Authenticated encryption on every frame, AES-NI / ARMv8 accelerated. TLS cannot replace SAS (ADR-001).
Ephemeral X25519
HKDF-SHA256 derives session keys. Long-term keys only sign, never enter the KDF — forward secrecy holds.
Ed25519 device identity
Long-term keys sign the handshake transcript. Device ids derive from public keys and revoke per device.
Local-first path
No server in the default path. Relay is never the default; every Connected feature is opt-in.
One experience across devices
Phone, tablet, and desktop share the same tokens and transfer state machine.
Hand the file to the device next to you, not to the cloud
Download the client, or spend two minutes on the security model first.