How we built an encrypted notepad and how it compares
We wanted something like ProtectedText but with a stack we could maintain and a UX we could improve. Here’s where we landed.
We’re not the first encrypted notepad on the web. Tools like ProtectedText, Standard Notes, and others have been around for years. We built Inkrypt because we wanted a zero-knowledge note that’s simple (no account), uses modern crypto (AES-256-GCM, strong KDF), and runs on a stack we control.
What we kept simple
- No signup. You pick a URL and a password. That’s the whole identity model.
- One password per note. No “account password” vs “note password”—just one secret per note.
- Share by link + password. No invites or roles—whoever has both can open and edit.
Where we invested
We use PBKDF2 with 310k iterations and AES-256-GCM with a random IV per save. We store only ciphertext and metadata. The editor supports rich text, images (encrypted in the same note), and multiple tabs. So: comparable security to the best in class, with a UX that fits “quick secure note” without turning into a full productivity suite.