Turn on encryption and your upload is scrambled client-side with AES-256-GCM before it leaves your browser.
The key is generated server-side once, emailed to you, and never stored after that — lose the email and the files are gone too. There's no recovery flow, because building one would mean keeping a copy of the thing we're claiming not to keep.
Share links with real rules
Files you store sit behind share links with their own password, download cap, and expiry, set per link, each independently revocable. Two links to the same file can carry completely different rules
Notes, live and shared
Real-time cursors and search across your notes by default.
Lock a specific note and both of those drop out, since neither works
without the server reading what's inside. That's a per-note choice, not
account-wide.
Or skip the server entirely
A six-digit code sets up a WebRTC data channel directly between two
browsers over DTLS. No upload, no size cap, nothing stored.
Stack
Next.js, Laravel API, Postgres, Reverb for the live-cursor sync, Backblaze
B2 for storage, on Kubernetes on a small VPS.
sharenod.com — free to use.
Top comments (0)